MCP works, doesn't deliver

[Rick Cooper]

 > -----Original Message-----
 > From: mailscanner-bounces at lists.mailscanner.info 
 > [mailto:mailscanner-bounces at lists.mailscanner.info] On 
 > Behalf Of Rick Cooper
 > Sent: Friday, June 22, 2007 9:33 AM
 > To: 'MailScanner discussion'
 > Subject: RE: MCP works, doesn't deliver
 > 
 >  
 > 
 >  > -----Original Message-----
 >  > From: mailscanner-bounces at lists.mailscanner.info 
 >  > [mailto:mailscanner-bounces at lists.mailscanner.info] On 
 >  > Behalf Of Glenn Steen
 >  > Sent: Friday, June 22, 2007 3:51 AM
 >  > To: MailScanner discussion
 >  > Subject: Re: MCP works, doesn't deliver
 >  > 
 >  > And it works locally? How very odd. Did you submit via telnet?
 >  > 
 >  > On 21/06/07, Rick Cooper <rcooper at dwford.com> wrote:
 >  > > I have never used the MCP features of MailScanner before, 
 >  > after all the
 >  > > traffic thought I would try it. My problem is a bit odd in 
 >  > that if I do a
 >  > > test (with the sample rules) it hits fine, and if I sent 
 >  > it locally it
 >  > > delivers the mail tagged correctly. However, if I send it 
 >  > from remote it
 >  > > does exactly the same thing, logs the same way, says it 
 >  > delivered and then
 >  > > the message is just gone. Not in any queue, not in the 
 >  > inbox, just gone.
 >  > >
 > [...]
 > 
 > Get's better. In MailScanner.conf my non spam action is to 
 > deliver and
 > forward to a special account that archives the mail and each 
 > night another
 > process goes through all the messagaes in the spam, and ham 
 > accounts and
 > removes all the headers that we add to an email and then 
 > moves them to a
 > corpus directory and depending on where they come from 
 > learns them as ham or
 > spam. Well these mcp mails are going into the ham mail box 
 > but are not being
 > delivered. Remember there is no such action associated with 
 > mcp, all mcp
 > actions are simply deliver (no rules, no forward just 
 > deliver). So where on
 > earth is MailScanner getting the forward address in the 
 > first place, and why
 > is it only forwarding and not delivering?
 > 

Tried running in debug mode with debug SA yes as well and I get the
following errors:

[28618] dbg: plugin: did not register
Mail::SpamAssassin::Plugin::Check=HASH(0x81cb0f0), already registered
[28618] info: config: failed to parse line, skipping, in
"/opt/MailScanner/etc/mcp/mcp.spam.assassin.prefs.conf": use_dcc 0
[28618] info: config: failed to parse line, skipping, in
"/opt/MailScanner/etc/mcp/mcp.spam.assassin.prefs.conf": use_pyzor 0
[28618] info: config: failed to parse line, skipping, in
"/opt/MailScanner/etc/mcp/mcp.spam.assassin.prefs.conf": use_razor1 0
[28618] info: config: failed to parse line, skipping, in
"/opt/MailScanner/etc/mcp/mcp.spam.assassin.prefs.conf": use_razor2 0
[28618] info: config: failed to parse line, skipping, in
"/opt/MailScanner/etc/mcp/mcp.spam.assassin.prefs.conf": decode_attachments
1

Sa also complains about the missing trusted_networks stuff as well. Is this
normal? The only patch I applied to SA was the new one Julian posted a
couple days ago

Rick


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