George, I would suggest you post your queries on the list itself. This is what I feel to do:
1. Have 2 servers running the MTAs with user profiles in LDAP. 2. The LDAP should take care of routing the mails to domain2 as well 3. Its not practical to have .forward for every users. 4. Now have a IMAP/POP3 proxy like perdition. Doing this, the users will not know from where the mail is being fetched. Regards, Prashanth On Sat, 18 Dec 2004 21:40:13 +0530, George K Cyriac <[EMAIL PROTECTED]> wrote: > I happened to read your mails on the replication of mail servers. I am also > facing the same problem. A good number of persons have responded in the > list, but none of them satisfy the requirement. My first server is in > Chennai and second one in Trivandrum, both running redhat linux, sendmail > and procmail. Emails received at one server should be copied to the second > server and vice versa on a real time basis. Users should have the option of > picking mails from any of the servers. > > I am eager to know how you solved this problem. Have you got any good > solutions? > > As per my knowledge, we may be able to solve the problem by the following > methods. It is a very crude way and waste a lot of bandwidth. > > 1. Register two domains domain1 and domain2 for server1 and server2. Domain2 > should have DNS entries in domain1 so that sender domain will resolve. > > 2. Server1 will receive mails for domain1. > 3. Use procmail and formail to change the domain on the fly and send or > bounce the mail to domain2 in server2. I haven't tried this method, but I > hope that this can be configured. > 4. Another approach which I have successfully tested is very simple. keep a > .forward file in the home directory of each user and forward a copy of the > mail to [EMAIL PROTECTED] The DNS entries for domain2 are available in domain1 > in server1 and the sender domain will resolve so that mail reaches safely at > domain2 in server2. This approach assumes that the users in both > domains&servers are same. > 5. The .forward file can be created in the home directory of each user by a > simple cat command with the required variables for .forward. The cat command > can be replaced with rm if we want to remove the facility or restrict the > entry of some users in domain2. > The domain2 in server2 will be the secondary MX for domain1 in server1. So > even if the server1 fails, all mails will be forwarded to server2. domain2 > must be included as an alias in the server2. > > 6. The major problem with this method is that if a user in Trivandrum send a > mail, it will have to travel all the way to Chennai and then a copy will > come back to the server at Trivandrum, wasting bandwidth. > > 7. We may be able to identify the originating server using the header fields > in email eliminating the to and fro traffic, but I haven't made any work on > it. > > Kindly revert with your solutions and remarks. > > With Regards, > > George K Cyriac > Trivandrum > > > > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ linux-india-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/linux-india-help
