nealbscott Posted September 14, 2010 Share Posted September 14, 2010 I am starting to see more and more spam where there is no blank line separating the internet headers from the body. Outlook 2007 does show a subject, and when viewing the internet headers you can see the the entire email... both plain text and html multipart sections. The Spamcop Email system does correctly identify it as spam, and thats good. But I would like to manually report this spam as well, and the parser gives up. so I thought I would add the blank line myself. But I don't seem to be placing it in the right place. Ideas? For example see: http://www.spamcop.net/sc?id=z4487485072zd...c2a3b32602898dz I get NO report IDs so I can't be more specific without actually posting the email here in this post. Link to comment Share on other sites More sharing options...
StevenUnderwood Posted September 14, 2010 Share Posted September 14, 2010 For example see: http://www.spamcop.net/sc?id=z4487485072zd...c2a3b32602898dz I get NO report IDs so I can't be more specific without actually posting the email here in this post. For manual reporting, the blank line needs to be placed between these lines Content-Transfer-Encoding: quoted-printable call free monday luck little gotta amazing kids them twurl.nl through a= Link to comment Share on other sites More sharing options...
nealbscott Posted September 14, 2010 Author Share Posted September 14, 2010 For manual reporting, the blank line needs to be placed between these lines Content-Transfer-Encoding: quoted-printable call free monday luck little gotta amazing kids them twurl.nl through a= Great! I suspected that, but was unsure.. In the example above, I found 'Content-Transfer-Encoding: quoted-printable' in there twice once for plaintext and once for an HTML version so I entered two blank lines. I'm getting closer. Now the spamcop reporting tells me: Finding links in message body Recurse multipart: Parsing HTML part error: couldn't parse head Message body parser requires full, accurate copy of message More information on this error.. no links found It might be the best I can get it. Does anything in below except look fishy? ------=_NextPart_000_0023_25_01CB53A9.185A2227 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859= -1"> <META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT size=3D2 face=3DArial>call free monday luck little gotta amaz= ing kids them twurl.nl through</FONT></DIV> Thanks for your help! Link to comment Share on other sites More sharing options...
Farelf Posted September 14, 2010 Share Posted September 14, 2010 There looks to be several things wrong with those headers 1. Boundary declaration is wrong, needs to be boundary="------=_NextPart_000_0023_25_01CB53A9.185A2227" (2 extra dashes) 2. I would put the missing blank line between these lines X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 and This is a multi-part message in MIME format. 3. Remove indent space (which signifies continuation) from first text line so call free monday luck little gotta amazing kids them twurl.nl through a= starts right at the left column, not 1 space indented The message & parse will then look like that shown at: http://www.spamcop.net/sc?id=z4487920305zc...2e40769256c4d5z As you know, you can't submit that report through SC, it is to assist manual reporting only. Link to comment Share on other sites More sharing options...
nealbscott Posted September 14, 2010 Author Share Posted September 14, 2010 Fantastic!!!! That did the trick, and you made me learn something! Link to comment Share on other sites More sharing options...
Farelf Posted September 14, 2010 Share Posted September 14, 2010 You're welcome. Marking 'resolved'. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.