Jim Paris wrote: > 1) If a message is spam, it should not be modified, but instead be > replaced by a multipart/mixed message where the first part is > a text/plain containing the SpamAssassin report and the second > part is a message/rfc822 containing the original, unmodified > message. This facilitates easy reporting to appropriate abuse@ > administrators, and allows me to easily deal with the message as > if it were normal if, say, I glance through the spam folder and > find a false positive.
Already planned as http://bugzilla.spamassassin.org/show_bug.cgi?id=18 Might take a while to implement though because I'm lazy. Patches happily accepted though. > 2) A message in the exact same format should be sent back to the > original sender. I realize that most of these will bounce, but > that's fine. I want the first text/plain portion to describe why > and how it was rejected (with the SpamAssassin report included); > I'll also use this to give them a password that they can include > in the subject (and to which I would assign a really negative score > in SpamAssassin), to ensure delivery if it was, in fact, sent by > a human. The second part, again, would be the original, unmodified > message/rfc822. Apart from the stuff related to #1 above, this is possible now, but not from within SA -- if you want to auto-reply to mails, then you can do that from procmail or something after SA's done its work. Auto-reply is unlikely to be added to SA since it falls outside the scope of stuff the package is intended to do -- it's not a mail generator, it's a spam filter. > So, my question: What's the best way to do this? Should I modify > Mail::SpamAssassin and add these two things as options (an option to > create new MIME messages rather than modify the existing one, and an > option to send a message back to the sender), or should I just create > my own Perl script that uses Mail::SpamAssassin in its current form? Sending return mail is best done outside SA I think, just check the mail after it's been through SA, and return to sender should be pretty straightforward to write. The report-as-text/plain-MIME-part stuff (bugzilla#18) is best done within SA, with the feature controlled by a config file option similar to report_header -- maybe report_MIME_part or something. If you write this, please consider contributing it back -- I'd love to add it to the distro but don't have a lot of time at the moment to write it myself. C _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
