MCP stopped working on upgrade....

Scott Silva ssilva at sgvwater.com
Tue Sep 4 20:51:12 IST 2007


Philip Butler spake the following on 9/4/2007 12:16 PM:
> Hi all,
> 
> I have noticed that MCP has stopped working when I upgraded to MS 
> 4.62.9-3 / SpamAssassin 3.2.3 - not sure which one is where I should be 
> looking.
> 
> On searching some of the archives, I came across a message on how to 
> test MCP:
> 
> ------
> spamassassin --config-file=/etc/mailscanner/mcp.spam.assassin.prefs.conf 
> --siteconfigpath=/etc/mailscanner/mcp -p 
> /etc/mailscanner/mcp.spam.assassin.prefs.conf -t -D < /testfile 2>&1 | 
> less -e
> ------
> 
> where /testfile contains the word vi_gra (with an a vs. _).  I get the 
> following output....
> 
> ------
> [3750] dbg: config: read file /etc/mailscanner/mcp/10_example.cf
> [3750] dbg: config: read file /etc/mailscanner/mcp/mcp_rules.cf
> [3750] dbg: config: using "/root/.spamassassin" for user state dir
> [3750] dbg: config: using 
> "/etc/mailscanner/mcp.spam.assassin.prefs.conf" for user prefs file
> [3750] dbg: config: read file /etc/mailscanner/mcp.spam.assassin.prefs.conf
> [3750] info: config: failed to parse line, skipping, in 
> "/etc/mailscanner/mcp.spam.assassin.prefs.conf": use_dcc 0
> [3750] info: config: failed to parse line, skipping, in 
> "/etc/mailscanner/mcp.spam.assassin.prefs.conf": use_pyzor 0
> [3750] info: config: failed to parse line, skipping, in 
> "/etc/mailscanner/mcp.spam.assassin.prefs.conf": use_razor1 0
> [3750] info: config: failed to parse line, skipping, in 
> "/etc/mailscanner/mcp.spam.assassin.prefs.conf": use_razor2 0
> [3750] info: config: failed to parse line, skipping, in 
> "/etc/mailscanner/mcp.spam.assassin.prefs.conf": decode_attachments 1
> [3750] info: config: failed to parse line, skipping, in 
> "/etc/mailscanner/mcp.spam.assassin.prefs.conf": use_dcc 0
> [3750] info: config: failed to parse line, skipping, in 
> "/etc/mailscanner/mcp.spam.assassin.prefs.conf": use_pyzor 0
> [3750] info: config: failed to parse line, skipping, in 
> "/etc/mailscanner/mcp.spam.assassin.prefs.conf": use_razor1 0
> [3750] info: config: failed to parse line, skipping, in 
> "/etc/mailscanner/mcp.spam.assassin.prefs.conf": use_razor2 0
> [3750] info: config: failed to parse line, skipping, in 
> "/etc/mailscanner/mcp.spam.assassin.prefs.conf": decode_attachments 1
> [3750] info: config: failed to parse line, skipping, in 
> "/etc/mailscanner/mcp.spam.assassin.prefs.conf": use_dcc 0
> [3750] info: config: failed to parse line, skipping, in 
> "/etc/mailscanner/mcp.spam.assassin.prefs.conf": use_pyzor 0
> [3750] info: config: failed to parse line, skipping, in 
> "/etc/mailscanner/mcp.spam.assassin.prefs.conf": use_razor1 0
> [3750] info: config: failed to parse line, skipping, in 
> "/etc/mailscanner/mcp.spam.assassin.prefs.conf": use_razor2 0
> [3750] info: config: failed to parse line, skipping, in 
> "/etc/mailscanner/mcp.spam.assassin.prefs.conf": decode_attachments 1
> [3750] dbg: conf: finish parsing
> [3750] dbg: config: score set 1 chosen.
> [3750] dbg: message: main message type: text/plain
> check: no loaded plugin implements 'check_main': cannot scan! at 
> /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm 
> line 164.
> ------
> 
> The last one puzzles me since I am not a perl guru.  Also, the warnings 
> (use_dcc , etc) - what should the syntax for this be ??  I know that's 
> not the problem, but want to clean up the syntax to be proper.
> 
> Anyone know if the "no loaded plugin implements 'check_main'" is the 
> problem with MCP - and if so, what to do to fix it ??
> 
> Thanks,
> 
> Phil
> 
> 
In your /etc/mailscanner/mcp directory you need a v320.pre file and add the 
following content to it;
--cut--
# Check - Provides main check functionality
#
loadplugin Mail::SpamAssassin::Plugin::Check

--cut--


-- 

MailScanner is like deodorant...
You hope everybody uses it, and
you notice quickly if they don't!!!!



More information about the MailScanner mailing list