-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 09 May 2002 07:41 am, Marc G. Fournier wrote: > Sorry, bad subject, couldn't think of better though ... > > Using postfix as an MTA, you can easily setup a > content_filter so that all email through gets checked ... > not a problem there ... if I tend setup a 'spam@<domain>' > address that those wishing to report spam to razor can use > to submit the spam, that spam message (with the appropriate > spamassassin markups) will go through and get *re-marked > up*, since its still spam ... > > how does spamassassin -r handle that? is there any problem > with that?
Why worry about how spamassassin -r handles it? Can't you just add a line in your local.cf file such as the following: all_spam_to spam@<domain> This way, the message isn't flagged as spam the second time through. The information from the first run will still be intact, but SA should strip that out. However, keep in mind that if this message is being forwarded instead of being redirected, the razor reporting will most likely not work as you wish. This is because the original message (with or without headers) will be the contents of the message sent to spam@<domain>. The MUA will most likely add some text about the message being forwarded that would disrupt the razor reporting. Good luck, Richie Laager Wikstrom Telecom Internet -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE82ze1bfU6uV4fG84RAm7QAJ9f2s1NZYdeQX18MbUEgmCuUEOPZgCgxBcA L5YneNpblNS4Txuhx8KB0B4= =Q8Me -----END PGP SIGNATURE----- _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
