No, you do not _need_ an MX entry for each host (if you have only one, that
is the server that will be used). But your DNS, its MX records and
preference can determine which host the sender connects to, to deliver to
you. If you do have MX as Marius suggests, then the sender should always try
peerserver1, first, then each server in turn, if no response from the
earlier one(s). If MX all had same preference, then any of the four could
accept the new mail (sort of 'load splitting'). The accepting peer will
still have to check the others if user account is not on this machine. Since
users would be connecting to only 1 of the peers, outbound mail would be
handled by that server (assuming you have not configured IMail to use a
Gateway), so again a form of outbound 'load splitting'. I suppose you could
use a Gateway, the same on for all, if you wished. Just means that the IMail
servers would all be funneling through the Gateway. A fast Gateway, might be
able to handle many IMail peers.

I would recommend that all peers have A records in DNS.

Daniel Donnelly
Ipswitch Technical Support
________________________________________________________
See our Knowledge Base at http://support.ipswitch.com/kb

----- Original Message -----
From: "Gaudin, Marius (Softec)" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 09, 2000 10:12 AM
Subject: RE: [IMail Forum] Another Peering Issue


> Perhaps you need a separate MX entry for each one of the peer servers,
e.g.
>
> mydomain.com IN MX 10 peerserver1.mydomain.ch.
> mydomain.com IN MX 20 peerserver2.mydomain.ch.
> mydomain.com IN MX 30 peerserver3.mydomain.ch.
> mydomain.com IN MX 40 peerserver4.mydomain.ch.
>
> If Ipswitch's knowledge base does not clear up the issue, send them a mail
> and ask. My questions have usually been answered within one day.
>
> Marius
>

Please visit http://www.ipswitch.com/support/mailing-lists.html 
to be removed from this list.

An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/

Reply via email to