MCP Error Fix

[Julian Field]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This is the default setting, and has been for a while. I'll get around 
to taking a look at this problem some time, but not many people need MCP 
particularly now I have the "SpamAssassin Rule Actions" setting which 
can do most of what MCP can, but a *whole* lot faster.

Chris Crymes wrote:
> Hello,
>
> I'm a new member, I joined to share a fix I couldn't find in the 
> documentation or in the list archives.
>
> I was trying to get MCP working and had everything setup correctly. I 
> could see the emails being processed in the mail logs but the emails 
> were disappearing after processing.
>
> I finally changed the scan first setting from MCP to SPAM and it 
> started working. I do not know why but it works.
>
> I hope it helps someone.
>
>
> -- 
> Chris Crymes
> ccrymes at gmail.com <mailto:ccrymes at gmail.com> 

Jules

- -- 
Julian Field MEng CITP CEng
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
PGP public key: http://www.jules.fm/julesfm.asc


-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.8.1 (Build 2523)
Comment: Use Thunderbird Enigmail to verify this message
Charset: ISO-8859-1

wj8DBQFH0xX+EfZZRxQVtlQRAvdQAJ9h2fjEOhTgRbDF1HMXbx9XZ8rxGgCeJgxN
v/le1qyQOPfW9nN+wiA/kYE=
=BDPX
-----END PGP SIGNATURE-----

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