Difference between revisions of "Using ASSP with Zimbra"

(New page: ASSP is most easily implemented with Zimbra as a separate appliance. A simple and modest box running your favorite flavor of Linux will do the trick. Simply configure ASSP to point at yo...)
 
m
Line 8: Line 8:
 
A second implementation would be only slightly more complex.
 
A second implementation would be only slightly more complex.
 
It would involve changing the receiving SMTP port in Zimbra to a custom
 
It would involve changing the receiving SMTP port in Zimbra to a custom
one of your choosing. Install ASSP ancd configure it to listen on the default port
+
one of your choosing. Install ASSP and configure it to listen on the default port
 
of 25 and specifying in the ASSP configuration to forward to localhost
 
of 25 and specifying in the ASSP configuration to forward to localhost
 
at the custom Zimbra specified port number.  In this way both services could
 
at the custom Zimbra specified port number.  In this way both services could
 
co-exist.  This configuration is probably more susceptible to issues
 
co-exist.  This configuration is probably more susceptible to issues
 
during upgrades, but reduces the amount of hardware to be maintained.
 
during upgrades, but reduces the amount of hardware to be maintained.

Revision as of 20:37, 17 November 2008

ASSP is most easily implemented with Zimbra as a separate appliance. A simple and modest box running your favorite flavor of Linux will do the trick. Simply configure ASSP to point at your Zimbra host. This gives you not 1 but 2 anti-spam systems. If you prefer to keep it simple you could easily disable the provided system with Zimbra using the Admin console.

A second implementation would be only slightly more complex. It would involve changing the receiving SMTP port in Zimbra to a custom one of your choosing. Install ASSP and configure it to listen on the default port of 25 and specifying in the ASSP configuration to forward to localhost at the custom Zimbra specified port number. In this way both services could co-exist. This configuration is probably more susceptible to issues during upgrades, but reduces the amount of hardware to be maintained.

Jump to: navigation, search