Scaling from 1 to N backend mail servers.
Distributing mails to different servers can serve many purposes.
Scale as you grow
Distribution of load. (one server may be exhausted, add another, and another, and so on.)
Quality Of Service
server10 connected to SAN, server 5 with daily backup, server 2 with weekly backup, server1 with no backup for free accounts
After distributing the mail to different servers, you are left with the task or informing your users which mail server their mails are on.
Example:
user: aghaffar@ispman.org -> please connect to pop10.ispman.org
user: cbarth@ispman.org -> please connect to pop1.ispman.org
This can easily become a support nightmare. Imagine if you decide to move mails of user aghaffar@ispman.org from mailhost10 to mailhost9 for the sake or performing some administration tasks on mailhost10.
A POP/IMAP proxy in this case solves the problem.
It listens for IMAP/POP connections on the frontend servers and proxies the connection to the correct mailhost by retrieving this value from the LDAP server.
now you can tell all your users to use pop.ispman.org no matter where their mail is stored.
pop.ispman.org can be an address of 1 or multiple machines.
Example:
pop IN A 192.168.1.1
pop IN A 192.168.1.2
pop IN A 192.168.1.3
pop IN A 192.168.1.4
|
|
ISPMan Sponsors
| - |
Sourceforge.net
has provided the development platform for this software.
Thank you sourceforge
|
| - |
envida.net
provides hardware and network for testing of ispman prooject. Envida also provides ISPMan support and other ISP related services.
|
| - |
marshallnet.net
provides dns hosting for this domain running under ISPMan
|
|
