On Monday 31 October 2011 07:48:08 Janantha Marasinghe wrote:
> I have just setup a backup MX
Why? In most cases they are more trouble than they are worth. Spam
magnets which do nothing to help you, unless your primary MX is down
for 3 or more days. (In the latter case, address that problem first!
You need more reliable primary hosting.)
> My DNS entries are
>
> 10 mail.domain.com
> 20 mail2.domain.com
Domain.com is a real Internet name. Do not use it as an example; we
have example.{com,net,org,many others} for that purpose.
> My main.cf on the mail2 is as follows
>
> relay_domains = domain.com, $mydestination
You do not want/need $mydestination on there. That is a compatibility
hack for pre-2.0 versions of Postfix.
> relay_recipient_maps = hash:/etc/postfix/relay_recipients
>
> I'm now testing out the testing out taking down postfix on the
> mail.domain.com and it do get queued on the 2nd, but i see on
> mail.log that mail2 tries to connect to itself as well
> Oct 31 18:16:32 fs2 postfix/smtp[7557]: connect to
> mail.domain.com[xxxxxxxxxxxxxxxxx]:25: Connection refused
> Oct 31 18:16:32 fs2 postfix/smtpd[7551]: disconnect from
> snt0-omc2-s7.snt0.hotmail.com[65.55.90.82]
> Oct 31 18:16:53 fs2 postfix/smtp[7557]: connect to
> mail2.domain.com[xxxxxxxxxxxxxxxxxx]:25: Connection timed out
> Oct 31 18:16:53 fs2 postfix/smtp[7557]: 466AB26C0114:
> to=<u...@domain.com>, relay=none, delay=23, delays=1.9/0.01/21/0,
> dsn=4.4.1, status=deferred (connect to
> mail2.domain.com[xxxxxxxxxxxxxxxxxx]:25: Connection timed out)
>
> Is this a normal behaviour?
Typically when using relay_domains, one also uses transport_maps for
these domains, to tell Postfix where to route the mail. Lacking such
an override, Postfix will use what's in DNS.
As an alternative, you could use split DNS ("view" in BIND terms) for
the backup MX host.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
