MCP broke after upgrade

Julian Field MailScanner at
Tue Apr 15 18:39:30 IST 2008

What did you upgrade?

Renee Gehlbach wrote:
> Hello,
> We had MCP working in a previous version, but it is no longer working 
> properly since we upgraded.  Our system is currently running FreeBSD 
> 6.3, with MailScanner port Mailscanner-4.67.6_1, SpamAssassin port 
> p5-Mail-SpamAssassin-3.2.4_3.  We have several cf files with MCP rules 
> in the directory /usr/local/etc/Mailscanner/mcp, where the port places 
> its example MCP rule file.  Up until the upgrade, all of the rules in 
> these files were working properly.  MCP seems to be working, as the 
> X-MailScanner-MCPCheck header appears in all messages.  However, it 
> does not seem to be finding the MCP rules, as even messages which 
> should be triggering rules have the value (score=0, required 2) for 
> this header.  spamassassin --lint shows clean, as does 

> spamassassin -p /usr/local/etc/Mailscanner/mcp --lint -D
If that doesn't say the rules are being read in, then it's not a 
MailScanner problem. You need to get that to read the rules, and admit 
to it, first.


Julian Field MEng CITP CEng
Buy the MailScanner book at

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:

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