Hi, Paul

Yes, this is all sorted now, thanks. The second domain went live last Monday and all mail is being handled from one server. You are right on the ball.

I realised that I would have issues with remote mail access and that, as you say, the name of the sending server does not matter. There are good reasons for separating the mail source for both domains, but I also decided that they were not important enough to warrant setting up what would be an overly complicated 'solution'.

I'm glad that I started on this as early as I did as it gave me enough time to realise this setup would require more effort to monitor and maintain than was really required.

Thanks a lot for replying - it's reassuring to read your response and to know that I got there in the end :)

Cheers!

Hi

We currently have two installations of Pegasus Mail on our network on two servers. There are also two installations of Mercury on the same servers.

Together they handle mail for three domains.

We have just one public IP address. So, what I do is have the mail for all domains delivered to one server (which is configured to handle mail
for @first.com and @second.com). The second server (which handles mail for @third.com) uses POP3 to get mail for @third.com from the
@first.com mercury installation. We use a synonyms file on the first server to identify local user accounts with their respective @first.com
and @second.com accounts.

We've hardly used the second server, but with a domain name change coming up I have to ensure that mail from the new domain name which will
be @third.com will be sent from a server that identifies itself as third.com.

Is this the best way to do this? Am I making it too difficult?

If anyone can a suggest a better way of doing this please post.

Thanks.

Something else I was wondering about, and this is a Pegasus Mail question, is that the PMail address books and distribution lists presently
reside on Server 1 and are used by everybody. I use the PML and PMR environment variables to point to \\server1\pmail\

Is it OK to have just one book and list location for both installations?

Hey Greenman.  Nobody seems to have answered any of these questions from February - is it an ongoing issue or is it all sorted now?

I have one server handling mail for many domains and a couple of points occured to me:

1.  Your statement "I have to ensure that mail from the [third.com] will be sent from a server that identifies itself as third.com" puzzles me.  My server only has one name but sends mail from several domains.  You have to be careful about SPF, but your other than that any server could send mail from any domain.

2.  I believe all of this could be handled by one server - there may be operational reason why you split it over 2 machines, but it may simplify the setup if you were able to consolidate all on one.