Spamassassin scanning.

[rex007can]

Is it possible to configure Scalix to only scan incoming messages and not outgoing ones?
Because spamassassin adds info in the headers that sometimes causes a bounced message with a 550 error.
This can be fixed by keeping spamassassin from writing the header that causes the error (X-Spam-Status), but then spamass-milter can no longer see a score which causes an error in the logs (Cannot read <> or something like that), AND keeps it from rejecting messages with a ridiculous score without putting it in the user mailbox, which really sucks for users with PDA's.

So, can Scalix only have Incoming messages scanned and NOT Outgoing ones?

thanks.

[kanderson]

Probably the best/easiest way to do this would be to use a seperate machine for inbound scanning. After scanning, it should just pass the message to Scalix. Scalix should not use a smarthost, and therefore it will just send the message out directly.

Thanks
Kev.

[rex007can]

Sorry but I wouldn't consider having to put a new machine in production at both our offices just so we can scan only incoming messages "easy".

This should be fixed.

[Valerion]

You can create 2 seperate sendmail config files (one with the spamassasin milter and one without), then let the outgoing mail gateway (unix.out) use the non-spamassassin file when it invokes sendmail.

I remember seeing a thread about this several months ago (maybe a year), detailing how to do it, but I don't have time to search right now.

[rex007can]

Okay, that seems doable.
I'll try to find the doc.
Thanks.

[jillrae]

If you locate the document for this, can you please post the link? I'm in the process of setting up SPAMASSASSIN also on one "box".

Thanks

jillrae