Chris Petersen wrote: > Yeah. VPN and just host the imap server on our dsl line. > It's fast enough for the few times that people will be > checking their mail from home.
Fine. That appears to be the best practice (with minor worryings about security) See also thread "Best practices for internal/external servers" on comp.mail.imap >> One further possibility would be to play with a sibling domain, e.g. >> MyCompany.com and MyCompany.net, each having the same mailboxes. > > Why would that matter? DNS is smart enough to know which IP you're connecting > from, and route you to 192.168.xx when you're local and an external IP when > you're not (Look at "views" in bind). For a moment I thought users could keep both external and internal mailboxes. Both accessible from the office but only the external from the outside. That would probably generate _"Sorry mate, I knew you were abroad but I just clicked on your name and didn't realize I was sending it internally" sort of situations :-/ OTOH I'm not sure how the IMAP feature of allowing synchronization can be leveraged for implementing an intelligent replication of messages between external and internal servers. I mean having both servers acting as a proxy of each other so that all messages are always available from both servers. This would probably waste more bandwidth than it would save. As a synthesis, having a single server is the best practice, AFAICS. ------------------------------------------------------- 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
