Thanks, Ed.
I don't actually want to do that. I was wondering how to set up a
secondary MX record and how the secondary mail server delivers mails
when the primary mail server is down. I have tried with my home network
here for testing purpose only.
Please, may I ask you assist further for my situation below:
I have on my DNS server the zone file /var/named/mydomain.com.zone as
follows:
$TTL 86400
@ IN SOA ns.mydomain.com. root.mydomain.com. (
1
1D
2H
1W
1H )
IN NS ns.mydomain.com.
IN MX 10 mail1.mydomain.com.
IN MX 20 mail2.mydomain.com.
ns IN A 192.168.1.100
mail1 IN A 192.168.1.101
mail2 IN A 192.168.1.102
I also have proper reverse zone set up (which is not necessarily shown,
here).
I tried to stop the mail service on mail1.mydomain.com, expecting that
from then on, whenever there is mail for the domain, mail2.mydomain.com
should be the one to receive and queue that mail. Yes, it actually did;
however, I got the error 553 (system config error): "mail loops back to
me (MX problem)".
Both my mail servers mail1 and mail2 run Sendmail in RH9.0 and they both
point to ns.mydomain.com as their DNS server, which runs BIND also in
RH9.0.
Please, you have any clues to the problem?
Regards,
Vidol
On Sat, 2003-08-23 at 08:23, Ed Greshko wrote:
> On Sat, 2003-08-23 at 02:19, Vidol Loeung wrote:
>
> > That means, the host mail1.mydomain.com will be contacted first by a
> > client for mail delivery to the domain. Only if that fails would the
> > host mail2.mydomain.com be contacted instead.
> >
> > Well, that is just the theory from the DNS part. But from the
> > mail-service part, how could I set up both servers (mail1 and mail2) to
> > receive mails for the same single domain with the same set of user names
> > and same places of mailboxes. Is there such a thing as user/mailbox
> > synchronization between the two mail servers?
>
> The short answer is that you wouldn't do what you propose. Depending on
> the size of the organization, the typical configuration is that the 2
> systems you describe act only as "front-ends" accepting email from the
> Internet and generally acting as the gateways for internal systems
> sending emails out to the Internet.
>
> These 2 systems would then redistribute incoming emails to multiple
> smaller systems or a single system internally.
>
> Now, that is not to say you can't have multiple servers acting on the
> same "message store". I have done that, with varying degrees of
> success, with commercial SW using NFS mounted message store. I've not
> tried it with open-source SW.
>
> Regards,
> Ed
>
> --
> http://www.shorewall.net Shorewall, for all your firewall needs
>
--
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list
