On Tue September 27 2005 21:27, Chris Petersen wrote: > I've been toying with an interesting idea at work, and since I > couldn't come up with any ideas on my own (or my circle of > friends/coworkers), I thought I'd present it here for more opinions > (since courier is our current choice of mail server).
Good choice. :-) > 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. Would laptops that could, potentially, access either server be involved? DNS can present one or the other, so no problem there, but they would point to the same IMAP SSL, so might there be a certificate issue? I assume you have full access to/control of the coloc, so it knows local LAN users, aliases, etc.? > That much I think courier can handle (or so I've inferred from > conversations on this list), and will most likely be what we do, but > what I'm wondering is if anyone has heard of a way that the servers > could be replicated (like a database does) so that people offsite > could check their mail (IMAP) at the colo server instead of coming in > via our slow DSL connection. So far, I've heard of several one-way > options (eg. rsync or drbd), but nothing capable of passing changes > both directions to keep both the colo and local servers completely in > sync. As M4 suggests, Coda could be an option for you. It worked well for me in a lab environment similar to what you describe. I never got to the point of having a low-speed link betweens server, although what I read on the Coda list indicated most normal loads should be handled, especially with the coloc filtering much of the gunk... (actually, thinking back on this, Coda wouldn't have much more overhead than what the coloc would be doing anyway - delivery to your local server. A rare exception would an alias expanded to many users at the coloc would be many multiple deliveries rather than forwarding the entire domain...) However, one of Coda's limitations prevented me from utilizing it in a production environment - the 4000 or so files per directory. http://coda.wikidev.net/Limitations Several users here have upwards of that in one or more maildirs (IMAP folders), and I'm not currently in a position to force splitting them up... :-( jerry ------------------------------------------------------- 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
