4. You could set to use Mercury as http://en.wikipedia.org/wiki/Smarthost for local users on same domain and allow Relay Non-local mails thrum using single relay mail account.

Hopefully that some experienced user can explain how to set it up. I've been able to set it up when using MercE but with little bit more settings it should be manageable with MercC.

 Additionally in my case I was using 2 mercury servers inside two separate network workgroups of same LAN with 12 users in one workgroup and 53 in second where second Mercury server relayed all domain emails to first Mercury server using MercC where first one has done final delivering using MercE. So other way around First gets all mails for domain then all unknown emails for addresses not in first users group are saved in relay account that second Mercury server get using MercD and distribute to user accounts.

 Sorry again for complex description but when you get it done it works :( hopefully you will get an idea how to solve.

 Again: None of these methods would solve the problem where there is a user with the same name on both systems.

Hello,

We have two internal mail servers, with different local users set up on each. The primary server (as far as MX priority) is Mercury, with a few hundred local users. The secondary server (a Zimbra server) also has unique local users. We have configured the Zimbra server to route non-local users to the Mercury server but don't know how to do the same on Mercury. i.e. a message comes into Mercury; the users doesn't exist on that server but does on Zimbra; how to tell Mercury to pass the message (relay?) to Zimbra. Also, is there a potential for a loop here if the users doesn't exist on either server. Both servers are in the same domain.

Thanks

[quote user="viking956"]

Hello,

We have two internal mail servers, with different local users set up on each.

Major problem, two mail server serving the same domain with different users.  The real solution here is to provide both servers with their own domain.  Use one as the gateway server that receives all mail for the domain and forwards the mail to the other.  The other server would never receive mail for the domain directly.

The primary server (as far as MX priority) is Mercury, with a few hundred local users. The secondary server (a Zimbra server) also has unique local users. We have configured the Zimbra server to route non-local users to the Mercury server but don't know how to do the same on Mercury. i.e. a message comes into Mercury; the users doesn't exist on that server but does on Zimbra; how to tell Mercury to pass the message (relay?) to Zimbra. Also, is there a potential for a loop here if the users doesn't exist on either server. Both servers are in the same domain.

Since Zimbra is forwarding all mail for non-local user to Mercury

though there are going to be problems.   Zimbra will be receiving

and forwarding mail that is going the be rejected by Mercury (Reject mail for non-local users) or even

worse forwarded off to the internet and you now have a open relay for

the spammers.  This needs to be fixed on the Zimbra side to only forward mail for known users of the other system.

There are a couple of way to get Mercury to forward the mail for non-local users off to the other server.  Since the domain is going to be identical on both systems you need to setup an alias for all users on the Zimbra system. 

1.  The first method would convert the user@domain.com to user@[<ip address>] so that Mercury/32 will forward the mail to the other host using literal addressing.  This assumes that Zimbra can use literal addressing.

2.  The second method would be to alias the user to a local account Zimbra and then have the Zimbra server pull the mail using POP3 form this account.

3.  The third method would alias as in step 2 but use WSMTPEx for forward the mail.  This also assumes Zimbra can use literal addressing.

None of these methods would solve the problem where there is a user with the same name on both systems.[/quote]