Chris Petersen wrote:
[...] Our goal is to set up one server at our colo for fast handling of incoming mail. This server would do spam/virus scanning/blocking to reduce the download load on our in-office DSL connection. A second on-site server would be set up to receive mail from the first server for faster access from machines on our LAN.
Did you reach any conclusions about that? Often, a considerable amount of e-mail is intra-office, which calls for a server on the LAN. However, users want to read that mail also on the odd day that they are out of the office. A traditional solution is to dial in, but it looks obsolete since better WAN connections exist from most places. One further possibility would be to play with a sibling domain, e.g. MyCompany.com and MyCompany.net, each having the same mailboxes. How is that going to be configured? And will it work? The idea is to only transfer mail contents from one server to the other when needed. I guess I'd need an IMAP proxy in order to do that consistently and intelligently. Or is Coda smart enough? Thanks for sharing your thoughts ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
