Re: Force IPv4 by Destination MX

2017-07-10 Thread Wietse Venema
Scott Talbert: > 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.

Re: Force IPv4 by Destination MX

2017-07-09 Thread Scott Talbert
On Sun, 9 Jul 2017, Wietse Venema wrote: Jul 7 23:10:57 bear postfix/smtp[29598]: 92F8422A0C90: to=, 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:

Re: Force IPv4 by Destination MX

2017-07-09 Thread James Cloos
> "WV" == Wietse Venema writes: WV> Sorry, transport mapping happens before DNS lookup. Maybe you can WV> fix your IPv6 setup by making sure that the PTR record for your WV> IPv6 address resolves properly That is not sufficient. Goog's v6 MXs stopped accepting from me, too, recently. And I

Re: Force IPv4 by Destination MX

2017-07-09 Thread Wietse Venema
Viktor Dukhovni: > > > On Jul 9, 2017, at 11:39 AM, Scott Talbert wrote: > > > >>> Jul 7 23:10:57 bear postfix/smtp[29598]: 92F8422A0C90: to=, > >>> 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.goog

Re: Force IPv4 by Destination MX

2017-07-09 Thread Viktor Dukhovni
> On Jul 9, 2017, at 11:39 AM, Scott Talbert wrote: > >>> Jul 7 23:10:57 bear postfix/smtp[29598]: 92F8422A0C90: to=, >>> 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]

Re: Force IPv4 by Destination MX

2017-07-09 Thread Scott Talbert
On July 9, 2017 11:52:44 AM EDT, wie...@porcupine.org wrote: >Scott Talbert: >> On Sun, 9 Jul 2017, Wietse Venema wrote: >> >> >> Jul 7 23:10:57 bear postfix/smtp[29598]: 92F8422A0C90: >to=, >> >> relay=aspmx.l.google.com[2607:f8b0:400d:c0b::1a]:25, delay=0.65, >> >> delays=0.13/0/0.29/0.22, ds

Re: Force IPv4 by Destination MX

2017-07-09 Thread Wietse Venema
Scott Talbert: > On Sun, 9 Jul 2017, Wietse Venema wrote: > > >> Jul 7 23:10:57 bear postfix/smtp[29598]: 92F8422A0C90: to=, > >> 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:c

Re: Force IPv4 by Destination MX

2017-07-09 Thread Scott Talbert
On Sun, 9 Jul 2017, Wietse Venema wrote: Jul 7 23:10:57 bear postfix/smtp[29598]: 92F8422A0C90: to=, 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:

Re: Force IPv4 by Destination MX

2017-07-09 Thread Wietse Venema
Scott Talbert: > Jul 7 23:10:57 bear postfix/smtp[29598]: 92F8422A0C90: to=, > 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] O

Re: Force IPv4 by Destination MX

2017-07-09 Thread Scott Talbert
On Sun, 9 Jul 2017, Mark Raynsford wrote: Unfortunately Google has stopped accepting mail from my server via IPv6 and I haven't been able to figure out why or resolve the problem. Hello. Are you by any chance seeing this message? Jul 9 08:43:06 mail postfix/smtp[18059]: C95E4849A: to=*, re

Re: Force IPv4 by Destination MX

2017-07-09 Thread Scott Talbert
On Sun, 9 Jul 2017, Wietse Venema wrote: Unfortunately Google has stopped accepting mail from my server via IPv6 and I haven't been able to figure out why or resolve the problem. However, it accepts mail via IPv4 just fine. Thus, I would like to configure Postfix to use IPv4 when sending mail t

Re: Force IPv4 by Destination MX

2017-07-09 Thread Mark Raynsford
On 2017-07-08T23:27:31 -0400 Scott Talbert wrote: > > Unfortunately Google has stopped accepting mail from my server via IPv6 > and I haven't been able to figure out why or resolve the problem. Hello. Are you by any chance seeing this message? Jul 9 08:43:06 mail postfix/smtp[18059]: C95E4849

Re: Force IPv4 by Destination MX

2017-07-09 Thread Wietse Venema
Scott Talbert: > Hello, > > New to Postfix here. > > Unfortunately Google has stopped accepting mail from my server via IPv6 > and I haven't been able to figure out why or resolve the problem. > However, it accepts mail via IPv4 just fine. Thus, I would like to > configure Postfix to use IPv4

Re: Force IPv4 by Destination MX

2017-07-08 Thread Benny Pedersen
Scott Talbert skrev den 2017-07-09 05:27: New to Postfix here. http://postfix.1071664.n5.nabble.com/smtp-IPv4-IPv6-map-td61342.html