Hi all. I have a strange feature request that I need to implement in Courier. Bear with me, as I am still coming up to speed on all this.
The company set up is where part of the users are in the States, and part are in India. They are all part of the same domain. They want two physical mail stores, one in the States, one in India. The "need" is to have the system set up in such a way that any email coming to any user gets delivered to BOTH mail stores.(yes, i know this is a bit crazy, i have argued my point til i'm blue in the face, and they are the bosses...) The reasoning behind this is that if one server goes down, the other will catch any emails, and the users can immediately switch over to the other server to access their emails. Basically, what I need is a setup such that any email sent to anybody on my domain hits a primary forward-only SMTP server. This SMTP server should verify that the user exists on the domain, then forward this message to each the two separate mail servers, but only after doing a virus scan and a running a spam filter on it. All this is pretty straight forward and can easily be accomplished via aliases, filtering etc. Here is where it gets tricky. The big fellas upstairs then want the ability to synchronize mailboxes between the two mail stores on an hourly or nightly basis. For instance if one user in the States uses pop.us.mydomain.org to pop/imap his mail, his US mail box will be the master for the nightly sync. If a user in India pops his mail from pop.in.mydomain.org to pop/imap his mail, then the India mail box will be the master for the nightly sync. I would like to employ this method rather than just "wipe non-master->push master data to non-master", as this would save immense bandwidth. I thought about this. With unix tools, it appears from the outset, to be pretty easy(rsync, perl, possible IMAP commands, etc). However, it occurs to me that since the Main MTA will only be forwarding the email, and the actual MDAs will be the servers in the States/India, the messages, though the same in body and subject content, will not be the same in overall content. The MDA's will append some of their unique info just prior to delivery. This means I can't just hash the message to get a KEY to sync on. Since I have to scan the emails for Spam and Virii(thereby necessitating the use of filters on the MTA server), I have just come up with the idea to run the email through a third "filter" which inserts a special unique line in the header portion of the message. That way, I can later use that unique header as a key for the messages. Do any of you have any recommendations for a better way to maybe do this? I have the Virus Scanner stuff working okay, so I have had to go through the Filter bit. I'm still not super strong with it, but I [think] this is the best way to approach it. What do you think? Should I stop smoking so much crack? or will it slide? Thanks In Advance, bill ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
