[SpamCop-List] SpamCop parser doesn't detect body of spam message
Robert L. Vaessen
rvaessen at spamcop.net
Sun Apr 25 18:48:05 EDT 2004
Could someone tell me why SpamCop's parser is incapable of detecting
spam/message body in the instance below? I sometimes receive spam
where the spammer's HTML message begins on the line immediately
following an X-UIDL: header.
I know that there's 'supposed' to be a space/blank line between the
header and the message body, but it seems to me that a simple rule
could be written to recognize the <html> tag as being part of the body.
In other words, any time an <html> tag appears, SpamCop assumes that
the message body has begun. The <html> tag, and any following data is
Is this possible? Desirable? Is there a 'valid' reason why <html> would
appear in the header?
Currently, when SpamCop chokes on this sort of message: 'No body
provided, check format of submission' I have to go in, add a blank
line/carriage return, and resubmit the spam for reporting.
My mail client (Apple's Mail.app) is smart enough to figure out where
the header ends and body begins. Why can't SpamCop's parser?
Snipet from spam which SpamCop chokes on.
Ref reported spam (after addition of carriage return):
> Content-Transfer-Encoding: 8bit
> X-UIDL: dl-"!)N("!J#R!!ip\uffda
> Buy top painkillers without prescription<p>
More information about the SpamCop-List