On Sun, 9 Jul 2017, Wietse Venema wrote:
Jul 7 23:10:57 bear postfix/smtp[29598]: 92F8422A0C90: to=<a...@xyz.com>,
relay=aspmx.l.google.com[2607:f8b0:400d:c0b::1a]:25, delay=0.65,
delays=0.13/0/0.29/0.22, dsn=5.7.1, status=bounced (host
aspmx.l.google.com[2607:f8b0:400d:c0b::1a] said: 550-5.7.1
[2607:f308:1:1::2 12] Our system has detected that this message
...
Was your mail really sent from 2607:f308:1:1::212? According to DNS,
your primary MX is bear.techie.net, with IP addresses 205.134.185.202
and 2607:f308:1:1::2.
If may be worthwhile to fix the SMTP client IP address with
"smtp_bind_address6 = 2607:f308:1:1::2", at least for off-site
email.
No, it's sent from 2607:f308:1:1::2. I don't know what the extra spaces + 12
after the IP address mean in that error report from gmail.
Likely Google sees your address as 2607:f308:1:1::212, but long SMTP replies
get folded across multiple lines, and unfolded with the whitespace you observe.
Here is an example from a few posts ago in this thread, with long
lines broken with backslash-newline for readability.
Jul 9 08:43:06 mail postfix/smtp[18059]: C95E4849A: to=*, \
relay=gmail-smtp-in.l.google.com[2607:f8b0:400d:c0b::1b]:25\
, delay=1.3, delays=0.29/0.04/0.53/0.46, dsn=5.7.1, status=\
bounced (host gmail-smtp-in.l.google.com[2607:f8b0:400d:c0b\
::1b] said: 550-5.7.1 [2001:19f0:5:752:f000:: 1] Our \
system has detected an un...
Note the spaces inside the IPv6 address.
You can convince yourself with tcpdump, or set "smtp_bind_address6
= 2607:f308:1:1::2" and see if that makes a difference.
Again, it would not be the first time that some IPv6 stack grabs
an unexpected IPv6 address.
Okay, so I confirmed with Wireshark that my server is definitely using
2607:f308:1:1::2 and not 2607:f308:1:1::212. In fact, I see this in part
of the exchange:
250-mx.google.com at your service, [2607:f308:1:1::2]
So, it remains a mystery as to what that 12 means. Perhaps some sort of
code indicating why the message was rejected?
Scott
