Re: Problem migrating a mail domain (loops back)
- On Wed, Dec 05, 2012 at 12:45:37PM +0100, d.davolio@... wrote:
> mydestination = mail2.mastercom, localhost.mastercom, localhost,Remove the transport table entry responsible for this.
> mastertraining.it, registroelettronico.com, masterscuola.it,
> myhostname = mail.mastertraining.it
> relay_domains = $mydestination
> transport_maps = hash:/etc/postfix/transport
> With this config I keep having the bounce:
> Dec 5 12:06:10 mail2 postfix/smtp: 7FDFDA711C:
> to=<d.davolio@...>, relay=none, delay=0.01,
> delays=0.01/0/0/0, dsn=5.4.6, status=bounced (mail for
> mastervoice.it loops back to myself)
> I share this because it's odd enough in my eyes. I bet is some DNSAlmost certainly not, unless you have a chrooted /etc/resolv.conf
that uses an unexpected DNS server. (Debian systems like yours
often have chroot on by default).
> Anyway, I had to modify the transport table as workaround to deliverAre there any other entries in the transport table? Barring
> the email for mastervoice.it domain. Like this:
> .fax smtp:[192.168.1.211]
> mastervoice.it smtp:[ASPMX.L.GOOGLE.COM]
> autoreply.mastertraining.it gnarwl:
explicit transport overrides the smtp(8) delivery agent uses
MX records, which it is clearly not doing.
Therefore, you may have content_filter settings in master.cf, or
a "*" entry in the transport table.
The order of precedence is roughly:
- transport_maps exact match
- transport_maps "*" entry
Any of these can override the default nexthop. A wildcard possibility
is a firewall that rewrites all port 25 traffic back to your machine!
Report what you see when you telnet to the Google MX hosts from "mail2".