Thanks for your encouraging reply.

 I am trying to implement this first in a virtual environment  and then will shift to a physical system.

When installing mercury, its asking for pmail, so that mercury can 'impersonate' /send message on user's behalf - this is what I understood.  I think, that part will be of interest.

I will update my findings here.

 Thanks again.

Hello,

Interested to know whether the following is possible:

Want to deploy an intranet mail server, sole mail server for our domain is Google Apps.

We want all mails to pass from Mercury mail server to Google Apps and then outside world.  Similarly, incoming mails will be collected by google apps first, then mercury intranet mail server will receive it and distribute in LAN.

 Is such a setup possible ?

Am a newbie, so please help me in this.

Thanks,

John.

I don't think you'll be able to get Mercury to send one message via bob@gmail.com and the next via bill@gmail.com. I mean that Mercury would likely only use one login when connecting to the gmail servers, which might be an issue. Gmail may re-write all messages as if they came from that one account, even if the reply-to headers are all different.

Tell you what: I'll shut up and let someone who knows the answer respond...

I haven't tested Google Apps Email myself, but from what I read about it I think it should work. Unlike Gmail you will be using your own domain name in the addresses, so the problem that Sharkfin points to should not occur. Using a secondary server seems to be part of the concept already, and there are several ways to forward mail to the secondary server (using active SMTP forwarding or collecting with POP3 from Mercury). Using Google Apps as SMTP relay for outgoing messages seems OK too.

/Rolf