MCP stopped working on upgrade....

[Philip Butler]

Yes it is there - and I have now copied it over to my /etc/ 
mailscanner/mcp directory and all is well again !!

I have the release files in a separate area - perhaps I should re- 
evaluate this.

Many thanks to Julian and Scott !!

Phil

On Sep 4, 2007, at 3:56 PM, Julian Field wrote:

> But the v320.pre file is in the RPM, so it should be there. Do
>    rpm -ql mailscanner | grep mcp
> and you should see it listed.
>
> Julian Field wrote:
>>
>>
>> Philip Butler wrote:
>>> 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 ??
>> Make sure there is a v320.pre in /etc/MailScanner/mcp or else you  
>> don't be loading the main "Check" plugin which implements the main  
>> scanning functionality. It should say this:
>>
>> [root at alegria mcp]# cat /etc/MailScanner/mcp/v320.pre
>> # Check - Provides main check functionality
>> #
>> loadplugin Mail::SpamAssassin::Plugin::Check
>>
>> [root at alegria mcp]#
>>
>>>
>>> Thanks,
>>>
>>> Phil
>>>
>>>
>>
>> Jules
>>
>
> Jules
>
> -- 
> Julian Field MEng CITP
> www.MailScanner.info
> 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
> For all your IT requirements visit www.transtec.co.uk
>
>
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> For all your IT requirements visit www.transtec.co.uk
>
> -- 
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the website!