Quote:
Originally Posted by tgx  From testing, the stuff that ends up in Junk on Zimbra never gets delivered with ASSP. |
But if you want not to see it at all in Zimbra, then you can just lower the kill percent under Global Settings:AS/AV.
Conversely,
Quote:
|
Emails quarantined under Zimbra are handled the same way as ASSP so getting the email back is the same exercise...digging in the filesystem for the email.
|
In that case you could increase the kill percent to disable "kill" altogether. Result: all your junk mail goes into Junk instead of being quarantined. If that has too much of an impact on storage you can then decrease the spam message lifetime under Class of Service:Advanced.
This is not to say that ASSP isn't cool, and given my planned installation I could use it anyway at least as an edge SMTP proxy+RBL blocker, to take some load off of Zimbra. I remember it has Greylisting and maybe some other non-content-based tools as well. If I can then integrate its content filtering with Zimbra in such a way as to give users Zimbra's ease of re-classifying ham/spam, plus putting ASSP-identified spam directly into Junk, that would be great.
One thing I'm remembering, though, ASSP recommended that users set their SMTP server to ASSP rather than (in this case) Zimbra. I believe that was required for auto-whitelisting based on addresses found in outbound mail. Thing is, this would mess up Zimbra's excellent server-based storage of Sent mail. Not to mention, you couldn't do it for web mail. But maybe I could use Servers:MTA:Relay MTA for external delivery to point Zimbra at ASSP.