John Peacock wrote:
Though a couple of self-inflicted Denial of Service attacks on my mail servers, I've discovered that qpsmtpd doesn't implement any mailing loop detection internally. Now that I have fixed my misconfiguration (alias domains not completely set up), I thought I'd add this to qpsmtpd so it *can't* happen again.
Any progress on this? I ran into a similar situation a while ago when my server was trying to deliver a message to an address whose MX record resolved to 0.0.0.0.
I've also run into a problem with messages being refused after leaving qpsmtpd because of the "Delivered-To" check (it's amazing what sort of headers spammers put in their messages think it might help), so I'll probably write a plugin for that if no one else has.
And the fun thing today was a couple of spam messages with two subject lines each. The spamassassin plugin munges the first "Subject:", but Thunderbird apparently filters by the last. Not sure whether to change spamassassin to munge both subjects, write a plugin to refuse mail with multiple subject lines, or just set Thunderbird to filter on the "X-Spam-Flag" header instead (and still munge subjects to allow sorting by spamminess) and let other users fend for themselves.
-- Keith C. Ivey <[EMAIL PROTECTED]> Washington, DC
