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

[James P. Kinney III]

WooHoo!

Lack of a response on this list is is usually due to several reasons.
1) Don't know a solution
2) Don't have the time to answer, late for work
3) Don't like the way the poster demands an answer
4) Don't want to be involved in the trolling from the poster
5) Too busy in the latest OT rant to read anything actually related to
Linux ;}

In this case, it was 1) problem :)

Usually, when someone figures out a solution to their problem they
express elation at solving the problem on their own and are now eager to
share their new-found knowledge. Thanks for letting the group know a
solution to this. I have not been relaying any mail except leaving my
Intra-net so I have not seen this issue before. But I can foresee a time
when this knowledge will be useful as I may be an intermediate mail
relay point (i.e. backup mx record) for a server I run.

On Tue, 2003-09-16 at 11:13, Van L. Loggins wrote:
> 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.
> > 
> > 
> > -- 
-- 
James P. Kinney III          \Changing the mobile computing world/
CEO & Director of Engineering \          one Linux user         /
Local Net Solutions,LLC        \           at a time.          /
770-493-8244                    \.___________________________./
http://www.localnetsolutions.com

GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
<jkinney at localnetsolutions.com>
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part