Delivering mail to Google over IPv6 is tricky unless the stars align
in precisely the right manner. Doing so over IPv4 can still be
awkard, but is generally much simpler.
Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
hostlist reservedaddrs = 0.0.0.0/8 : 127.0.0.0/8 : 10.0.0.0/8 : 169.254.0.0/16 : 172.16.0.0/12 : 192.0.0.0/24 : 192.168.0.0/16 : 224.0.0.0/4 : 240.0.0.0/5 : 248.0.0.0/5
hostlist reservedaddrs = 0.0.0.0/8 : 127.0.0.0/8 : 10.0.0.0/8 : 169.254.0.0/16 : 172.16.0.0/12 : 192.0.0.0/24 : 192.168.0.0/16 : 224.0.0.0/4 : 240.0.0.0/5 : 248.0.0.0/5
-domainlist google_mxen = aspmx.l.google.com : gmail-smtp-in.l.google.com
+domainlist google_mxen = aspmx.l.google.com : gmail-smtp-in.l.google.com : \
+ *.aspmx.l.google.com : *.gmail-smtp-in.l.google.com
+
domainlist single_domain_mx = +google_mxen
<%- if @is_mailrelay -%>
domainlist single_domain_mx = +google_mxen
<%- if @is_mailrelay -%>
# expensive, you can specify the networks for which a lookup is done, or
# remove the setting entirely.
host_lookup = *
# expensive, you can specify the networks for which a lookup is done, or
# remove the setting entirely.
host_lookup = *
-# dns_ipv4_lookup = !localhost (disabled upon sgrans request, zobel, 2010-03-16)
+dns_ipv4_lookup = +google_mxen
# If this option is set, then any process that is running as one of the
# listed users may pass a message to Exim and specify the sender's
# If this option is set, then any process that is running as one of the
# listed users may pass a message to Exim and specify the sender's