( Thu, 27 Jan 2005 17:04:47 -0500 ) Chris Santerre :
> If I misunderstood this, I'm sorry. But can you sip the first server from > scanning the messege with SA? Seems the logical solution.
Not really. Because SA still have tu run on the first server. I leave it, but the users stay :-)
Well I would like SA:
- not to alter the body of the messages it found spam - not to check spam-tagged messages (It stil has to check NON-SPAM tagged)
I found on google that report_header could be the solution of the first point. But how about the second point?
report_header is deprecated.. use report_safe 0 in SA 2.50 and up.
As for the second issue, use a procmail rule to bypass calling SA if the "X-Spam-Flag: Yes" header is present.
SA itself has no mechanism for "aborting" the scan of a message. If SA is given a message, it gets scanned.
Also, if you're having problems where the second server doesn't tag messages the first server does tag, check to see if it's because the DUL lists are no longer hitting. If that's the case, you should manualy declare a "trusted_networks" and "internal_networks" (sa 3.0+) and include the first server.
This way, SA will trust the Received: header generated there, and check if a dialup node direct-delivered mail there. Otherwise, SA will assume the first server is the ISP MTA and it's properly relayed.
