On Tue, Dec 04, 2012 at 08:48:47PM +0100, Daniele Davolio wrote:
> Here the requested output:
> mail2:~# host -t mx mastervoice.it
> mastervoice.it MX 10 ASPMX.L.GOOGLE.COM
> mastervoice.it MX 20 ALT1.ASPMX.L.GOOGLE.COM
> mastervoice.it MX 20 ALT2.ASPMX.L.GOOGLE.COM
> mastervoice.it MX 30 ASPMX2.GOOGLEMAIL.COM
> mastervoice.it MX 30 ASPMX3.GOOGLEMAIL.COM
>
> I'm at home now, I'll look first for your hints tomorrow morning in
> office!
> I'll let you know what I'll discover.
> Thanks for your always needed help, and patience.
> Davo
>
>
> On Tue, 4 Dec 2012 13:16:45 -0500 (EST), Wietse Venema
> <[email protected]> wrote:
> > Ralf Hildebrandt:
> >> * [email protected] <[email protected]>:
> >>
> >> > Dec 4 15:13:41 mail2 postfix/smtp[26167]: 4E21EA735A:
> >> > to=<[email protected]>, relay=none, delay=0.1,
> >> > delays=0.1/0/0/0, dsn=5.4.6, status=bounced (mail for mastervoice.it
> >> > loops back to myself)
> >>
> >> What is the result of
> >> % host -t mx mastervoice.it
> >> on that machine?
> >
> > There's also an A record. Postfix will deliver mail there if
> > "disable_dns_lookups=yes" or smtp_host_lookup does not contain
Naturally, loops can also happen when routing is forced via transport
table entries, content filters, ...
So the MX records may be fine, but the OP's configuration may
specify an explicit relayhost, default_transport with a nexthop,
relay_transport with a nexthop, a transport table entry, ...
--
Viktor.
