On 5/11/2005 3:28 PM, Justin Mason wrote: > BTW I've seen some similar messages -- as far as I can see, when it > happens in my case, it's one of postfix, procmail or my MUA which is > interpreting the message structure wrongly due to the whitespace > wierdness.
That's possible too, if whitespace is wrapped improperly it can be read as a blank line. My setup is arranged so that postfix SMTP recieves the mail, hands it off to spamassassin while the session is still open, and then examines the message that comes back from SA for header flags. If the headers show that the message is spam, then postfix rejects the message, but otherwise accepts the mail and then hands it off to cleanup agent. Looking at the headers that come in and out of spamassasin is what leads me to believe that it's doing the mangling. In particular, we can assume that SA didn't see the blank line in the headers that it read (or else it would have appended the lines at the end of the top block, not the second block), so it seems kind of likely that "writing a new headers block" is what causes the conversion to happen, and results in CR/blanks/whatever getting turned into a blank line. OTOH, I know that postfix does some cleanup before it performs analysis (it adds Message-ID and does other stuff), so it is entirely possible that it is doing a CR/null conversion as part of that. Very annoying whatever it is -- Eric A. Hall http://www.ehsco.com/ Internet Core Protocols http://www.oreilly.com/catalog/coreprot/
