Lloyd Zusman writes:
Sam Varshavchik <[EMAIL PROTECTED]> writes:Lloyd Zusman writes:Sam Varshavchik <[EMAIL PROTECTED]> writes:Lloyd Zusman writes:In some cases, one of the Received-SPF headers that gets generated by Courier ends up being inserted after the initial group of headers, and inside the first part of a multipart message. The following consists of the topmost lines of a spam that I received, which illustrates thisThe spam was a corrupted message. This will not happen with ordinary messages.Thanks. So ... could you or someone explain what exactly is the nature of this corruption? I'd like to be able to somehow detect it programmatically, if possible. [ ... ]More than likely the first blank line in the message wasn't. It contained a space or some other unprintable character. So, Courier kept looking for the blank line that delimits headers from the body, and inserted the SPF header there.Well, there were simply two newlines (character \n, or 010, or 0x0a) and nothing else in the original message between the last header line and the first multipart separator. I have double- and triple-checked this. What else could be triggering this case?
There must be something else. For some reason the parser did not see the blank line, and continued to process the next couple of lines as part of the message header.
pgpSgeIjGfPKV.pgp
Description: PGP signature
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
