Spamassassin scanning.
Posted: Mon Mar 05, 2007 6:22 pm
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.
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.