When courier encapsulates a message because of missing 8bit heders etc and the message happens to be spam, the result is a message that appears to have originated from the machine running courier and is still spam. Spamcop and similar RBLs are not smart enough to see the obvious, so they end up blacklisting the courier machine. In fact, users of a courier system who report their spam to spamcop end up getting their own MTA blacklisted. There is plenty of misformatted spam floating around, so this is bound to happen pretty often.
The proper solution to this would be smarter RBL scripts, but I doubt anyone should hold his breath for them. As a workaround however, courier could append the original Received: headers of corrupted messages to its own. This would allow the RBL scripts to follow an unbroken Received chain down to the original spam source and would prevent courier from getting innocently blacklisted.
Sam, I'm aware that asking you do this is asking you to fix other people's errors, but we don't live in a just world anyway. Is there any chance you will?
Z
-- The best defence against logic is ignorance.
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
