pydspam corrupts rfc822 attachments
Python API for Sendmail Milters.
Brought to you by:
customdesigned
When the first html attachment is within an enclosed
rfc822 attachment (common when forwarding), pydspam
chooses to put the <!DSPAM...> tag there. That is
fine, but somehow, it also decides to add an extra end
boundary. I think the problem is actually in the email
package (again). Pymilter and friends seems to be the
only project that modifies messages in place. I guess
everyone else copies the message to a new one with changes?
Logged In: YES
user_id=142072
When a message is delivered to multiple local recipients
configured for pydspam, the headers are mangled such that
pine and netscape can no longer decode the MIME attachments.
If such a message is recieved by bms milter (e.g. sent to
jsconnor.com), then it is rejected with a "missing boundary"
error. The message actually seems to have an extra newline
before the headers of a message/rfc822 attachment. But this
*only* happens with two or more local dspam recipients.
I sampled the message as it comes from sendmail. The
version from sendmail was uncorrupted, the version after
modification by pydspam was corrupted. The seems to show
that pydspam is the problem. Running the original through
pydspam twice in a test harness does not reproduce the
problem, however.
Logged In: YES
user_id=142072
Originator: YES
New insight. It doesn't seem directly related to multiple recipients. I think the trigger is adding dspam tags more than once in the same connection. This would, of course, happen with multiple dspam recipients.