Disable MCP notifications for High Spam

Julian Field MailScanner at ecs.soton.ac.uk
Sun Feb 1 21:31:30 GMT 2009

If you can, re-implement your MCP filtering with "SpamAssassin Rule 
Actions". It gives you much more precise control over what happens to 
the mail, and will run a lot faster too.

On 31/1/09 11:56, Dave Jones wrote:
> Does anyone have any ideas how the MCP notifications can be disabled
> for High Scoring Spam?  The High Spam is getting caught and deleted
> but when it also hits the MCP threshold, the user is getting the
> recipient.mcp.report.txt notification.  There are lots of High Spam
> that will hit common profanity checks in MCP.
> I found a thread in the maillist archives on "MCP/SPAM Actions" saying
> that delete is the last action taken so the MCP notify takes
> precedence.   However, I was wondering if there are some recent
> feature additions that will allow me to override this now.
> High Scoring Spam Actions = delete
> MCP Actions = store notify
> High Scoring MCP Actions = store notify


Julian Field MEng CITP CEng
Buy the MailScanner book at www.MailScanner.info/store

MailScanner customisation, or any advanced system administration help?
Contact me at Jules at Jules.FM

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
PGP public key: http://www.jules.fm/julesfm.asc

This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

More information about the MailScanner mailing list