On Mon, Mar 09, 2015 at 03:08:15PM -0400, James B. Byrne wrote:
> > report the output of:
> >
> > $ printf "---%s---\n" "$(postconf -h myhostname)"
> > $ printf "---%s---\n" "$(postconf -h smtp_helo_name)"
> >
> > Make that "-hx" instead of "-h" if your Postfix is recent enough.
>
> [root@inet08 ~]# printf "---%s---\n" "$(postconf -h myhostname)"
> -bash: printf: --: invalid option
Oops: $ printf -- "---%s---\n" ...
That's why I in practice use printf "=== ...", but for some reason
typed "---" instead when composing my reply.
> [root@inet08 ~]# echo $(postconf -h myhostname)
> inet08.hamilton.harte-lyne.ca
And yet they object.
> [root@inet08 ~]# echo $(postconf -h smtp_helo_name)
> $myhostname
>
> [root@inet08 ~]# echo $(postconf -hx smtp_helo_name)
> inet08.hamilton.harte-lyne.ca
In that case you need to figure why the results might be different
for the Postfix smtp(8) client.
$ posttls-finger -l none -o myhostname=inet08.hamilton.harte-lyne.ca
"[mx01.1and1.com]"
posttls-finger: Connected to mx01.1and1.com[74.208.5.21]:25
posttls-finger: < 220 perfora.net (mxeueus001) Nemesis ESMTP Service ready
posttls-finger: > EHLO inet08.hamilton.harte-lyne.ca
posttls-finger: < 250-perfora.net Hello inet08.hamilton.harte-lyne.ca
[192.0.2.1]
posttls-finger: < 250-SIZE 157286400
posttls-finger: < 250 STARTTLS
posttls-finger: > QUIT
posttls-finger: < 221 perfora.net Service closing transmission channel
You're almost certainly sending some other helo name. Check
master.cf for overrides. If that does not make it obvious, put
the destination IP on "debug_peer_list" and check what command is
actually sent in verbose logs (or get a tcpdump).
It is also possible some (firewall) proxy or other is interposed
between your MTA and the Internet and the proxy is hijacking the
EHLO/HELO command.
--
Viktor.
