Re: Dropping Google AAAA records (was: Force IPv4 by Destination MX)

2017-07-10 Thread Scott Talbert
On Sun, 9 Jul 2017, Wietse Venema wrote: This is how three years ago I solved IPv6 problems for all domains that have Google as an MX host. /etc/postfix/main.cf: smtp_dns_reply_filter = pcre:/etc/postfix/smtp_dns_reply_filter /etc/postfix/smtp_dns_reply_filter: # /domain ttl IN addr

Re: postscreen delay inprovement - multple IP addresses

2017-07-10 Thread techlist06
> http://www.postfix.org/POSTSCREEN_README.html#white_veto Noel. I had read that section of the manual but it didn't sink in. Now I get it perfectly. Thanks again, much appreciated. -- View this message in context: http://postfix.1071664.n5.nabble.com/postscreen-delay-inprovement-multpl

Re: Dropping Google AAAA records (was: Force IPv4 by Destination MX)

2017-07-10 Thread Mark Raynsford
On 2017-07-09T19:15:29 -0400 wie...@porcupine.org (Wietse Venema) wrote: > This is how three years ago I solved IPv6 problems for all domains > that have Google as an MX host. Thanks for this. Personally, I don't expect to hear back from Google, so I'll be implementing this one myself. M pgphP

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.