On 29.08.2011 15:59, SL wrote: > Hello Hello, > I ran into an issue with my mail filtering which I solved by > activating "Broken lineStripping", which converts any CRLF to LF from > the input mail. > > I would like to know why LF is expected as a line terminator, in > particular because I thought that a MTA would feed an RFC 2822 > compliant mail to dspam, therefore using CRLF. I think RFC 2822 (and 2821) are using using CR followed by LF.
> When doing something like "cat myCRLFmail | dspam --deliver=stdout" > (without Broken lineStripping of course), your mail is garbaged with a > mix of CRLF and LF and added colons. Added colons? Where? Usually DSPAM does not touch the message at all except two cases: 1) You have turned on Broken lineStripping 2) You are using DSPAM in daemon mode In daemon mode DSPAM will normalize the mail and replace wrong \n with \r\n. With Broken lineStripping DSPAM will remove broken ^M from lines while reading the message stream line by line. If you have a mixed CRLF and LF in your message then your source was/is already broken and it's not DSPAM fiddeling around with the message at all. I say that because if you would use daemon mode then for sure there would not be a mixed CRLF and LF because the code would fix that into normalized CRLF. > Thanks Stevan ------------------------------------------------------------------------------ EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev _______________________________________________ Dspam-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspam-user
