transportmap ignores A record?
#currently investigating a masive mailbounce
I'm running postfix 2.9.4 on freebsd boxen.
Is it intentional that a transportmap reading in the form
intentionally ignores the A record of <hostname>?
In dns, <hostname> is like
<domainname> has address A
<domainname> has IPv6 address AAAA-1
<domainname> has IPv6 address AAAA-2
<domainname> mail is handled by 10 <blah-1>
<domainname> mail is handled by 10 <blah-2>
It keeps trying both AAAA addresses in a loadballanced manner I intented,
but blatantly ignores a usabable A host.
Am I missing some point here, or overlook a snippet of doc.
- On 12/13/2012 7:53 AM, Robert Joosten wrote:
> Hi,Some possibly related doc snippets;
> #currently investigating a masive mailbounce
> I'm running postfix 2.9.4 on freebsd boxen.
> Is it intentional that a transportmap reading in the form
> <domain> etrn-only:<hostname>
> intentionally ignores the A record of <hostname>?
In the case of SMTP, specify a service on a
non-default port as host:service, and disable MX (mail
exchanger) DNS lookups with [host] or [host]:port
The setting "smtp_address_preference = ipv6" is unsafe. It can fail
to deliver mail when there is an outage that affects IPv6, while the
destination is still reachable over IPv4.
Sorry for the generic help, but that kind of goes along with the
generic problem report. If you need more help, please see
-- Noel Jones