Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Vernon A. Fort (vfortprovident-solutions.com)
Date: Wed Oct 13 2010 - 10:11:58 CDT
On Wed, 2010-10-13 at 15:27 +0200, Tom Kinghorn wrote:
> On 2010/10/13 03:18 PM, Charles Marcus wrote:
> > On 2010-10-12 4:04 PM, Jeroen Geilman wrote:
> The reason I would like to do this was so that I could add my abuse
> email address as a recipient on any mail which is spam.
> That way, I could scan the actual email with spamassassin using the
> testing mechanism provided.
> I have some strange emails which keep getting passed by
One possibility would be to have amavisd 'add' spam info headers to
messages if the $sa_tag_level_deflt = 2.0 or above. Then:
1. Create two local email accounts (cyrus, etc..)
2. Set always_bcc to a local bcc mail account
3. Perl script to filter these bcc messages
4. The script delivers the messages to user.review (removes others)
Basically, the script will deliver messages to the review account if it
meets a specific condition. Say if the X-spam-score is between 4.0 and
the $sa_tag2_level_deflt cutoff. So you only review the messages in
this gray area.
You may be able to bypass the two account setup by having the always_bcc
set to a alias which pipes the message to the perl script.
Just a thought.....