Configuring Perdition: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
== Perdition use cases == | == Perdition use cases == | ||
[[Perdition]] is a proxy for the [[POP]] and [[IMAP]] protocols that allows a user to connect to any [[Perdition]] server, regardless of their account's [[zimbraMailHost]], and use a [[POP]] or [[IMAP]] client to access their mail. | |||
[[Perdition]] is useful in multi-node installations, where several [[mailstore]] servers may be accessed through the same hostname (either via round-robin [[DNS]] or a [[load balancer]]). | |||
[[Perdition]] is also useful for offloading the [[SSL]] connection from the [[tomcat]] server, and handling it in the proxy. This can reduce the load on the mailstore server, as well as work around some [[IMAP]] [[SSL]] bugs. | |||
== Setting the ports == | == Setting the ports == | ||
== Perdition certificates == | == Perdition certificates == | ||
== Enabling the service == | == Enabling the service == |
Revision as of 15:03, 25 July 2006
Perdition use cases
Perdition is a proxy for the POP and IMAP protocols that allows a user to connect to any Perdition server, regardless of their account's zimbraMailHost, and use a POP or IMAP client to access their mail.
Perdition is useful in multi-node installations, where several mailstore servers may be accessed through the same hostname (either via round-robin DNS or a load balancer).
Perdition is also useful for offloading the SSL connection from the tomcat server, and handling it in the proxy. This can reduce the load on the mailstore server, as well as work around some IMAP SSL bugs.