dspam appears to add a trailing newline to the message body as it passes through dspam's LMTP processing, regardless of the location of the dspam signature.
It may also do this in non-LMTP cases, but i have not had a chance to test any other cases. I first saw this problem mentioned as debian bug 383964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=383964 Let me know if i can be of any help tracking this down further. A simple example follows. Regards, --dkg Here's an LMTP transaction between MTA and dspam: 220 DSPAM LMTP 3.6.8 Ready LHLO squeak 250-squeak.fifthhorseman.net 250-PIPELINING 250-ENHANCEDSTATUSCODES 250 SIZE MAIL FROM: <[EMAIL PROTECTED]> 250 2.1.0 OK RCPT TO:<[EMAIL PROTECTED]> 250 2.1.5 OK DATA 354 Enter mail, end with "." on a line by itself From: sender <[EMAIL PROTECTED]> To: target <[EMAIL PROTECTED]> Subject: bogus message test data. . 250 2.6.0 <[EMAIL PROTECTED]> Message accepted for delivery QUIT 221 2.0.0 OK and the corresponding LMTP transaction between dspam and its LMTP target: 220 fake LMTP ready LHLO squeak-dspam 250-squeak.fifthhorseman.net 250-PIPELINING 250-ENHANCEDSTATUSCODES 250 SIZE MAIL FROM:<[EMAIL PROTECTED]> SIZE=268 250 2.1.0 OK RCPT TO:<[EMAIL PROTECTED]> 250 2.1.5 OK DATA 354 Enter mail, end with "." on a line by itself From: sender <[EMAIL PROTECTED]> To: target <[EMAIL PROTECTED]> Subject: bogus message X-DSPAM-Result: Innocent X-DSPAM-Processed: Fri Sep 1 12:02:09 2006 X-DSPAM-Confidence: 0.9897 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 44f85981204791804284693 test data. . 250 2.6.0 <[EMAIL PROTECTED]> Message accepted for delivery QUIT 221 2.0.0 OK
