On Thu, Apr 16, 2020 at 7:07 PM Viktor Dukhovni
<postfix-us...@dukhovni.org> wrote:
>
> > # postconf -Mf
> > smtp       unix  -       -       n       -       -       smtp
> > relay      unix  -       -       n       -       -       smtp
>
> Please add:
>
>   smtpv      unix  -       -       n       -       -       smtp -v
>
> > So I decided to change the destination SMTP server in "transport".
> > Instead of 10.0.0.10 I used 10.0.200.50.
>
> And add a transport entry:
>
>           debug.example smtpv:[10.0.200.50]
>
> > Here's the result:
> >
> > postfix/smtp[22953]: AB3AB12404F: to=<v...@mydomain.org>,
> > relay=10.0.200.50[10.0.200.50]:25, delay=0.09, delays=0.09/0/0/0,
> > dsn=5.4.6, status=bounced (mail for [10.0.200.50] loops back to
> > myself)
>
> Then send mail to <nobody@debug.example> and report the resulting
> verbose logging (you can use "collate").

Wietse was right.

One of these mailbox servers has indeed the same "SMTP name" as one of
the Postfix servers. In this case, I do get a message like this in the
log:
host XXX greeted me with my own hostname YYY

However, it's only a WARNING, and I didn't  see this message in my
previous logs (the ones I posted earlier).
I'm only configuring the Postfix servers, so I guess the mailbox
server had the same name by mistake.

Anyway, I just changed the smtp name of the mailbox server, and now
the messages are properly handed over to it from Postfix.

Maybe along with the warning, Postfix should also say that this is why
it thinks that it is looping back to itself.

Thanks for the "smtp -v" tip. It may come in handy in the future.

Vieri

Reply via email to