[ale] problems with MailScanner and spamassassin - Fixed it myself

[Van L. Loggins]

Nevermind I fixed the problem myself. Thanks for the lack of response, obviously I am the only person on the list to ever experience this problem.

In case anyone is interested the solution was to add the domain subnet and domain name of the domain that relays the mail to the other domain's mail server's into their whitelist and then add a line into spam assassin that tells the new bayesian filter to ignore the X-Turbocorp.com-MailScanner-SpamCheck: spam (blacklisted) header that our mailscanner was sending to their mail server inside of the message headers. we had to black list the other domain due to spammers using the fact that we were relaying messages between the two domains and then added the only two valid email addresses that would be coming from the other domain into the whitelist to be allowed thru. this is why the above referenced header was saying spam (blacklisted).





On Mon, 15 Sep 2003 12:29:05 -0400
ale-request at ale.org wrote:

> 
> Message: 11
> Date: Mon, 15 Sep 2003 12:25:09 -0400
> From: "Van L. Loggins" <vloggins at turbocorp.com>
> Subject: [ale] problems with MailScanner and spamassassin
> To: ale at ale.org
> Message-ID: <20030915122509.03a059e3.vloggins at turbocorp.com>
> Content-Type: text/plain; charset=US-ASCII
> 
> 
> I'm having a unusual problem with MailScanner and Spamassassin on one of our systems.
> 
> every single message that is being delived to user's mailboxes on this system has the {Spam?} header attached to it. I have even went into the MailScanner.conf file and turned off the header modifications to spam messages option. Does anyone have any ideas on how to fix this? It's very annoying to say the least.
> 
> 
> -- 

-- 
Van Loggins        vloggins at turbocorp.com
Assistant System Administrator
Linux User #316727
1-770-532-2239 Extension 9404
Turbo Logistics
http://www.turbocorp.com