Hmm, blocking connections is highly unusual for us, as it doesn't provide any feedback, usually we respond with a 5xx banner or to HELO. I would check to see if you can reach www.google.com on IPv6 from the same box, and if you can, then go ahead and send me your IPv6 address and I can escalate that.
Unusual means it's almost always a manual step taken in response to a spam or other bad acting campaign of extremely large magnitude... but sometimes those types of blocks can linger. Brandon On Wed, Sep 8, 2021 at 12:53 AM Slavko via mailop <mailop@mailop.org> wrote: > Dňa 7. 9. o 20:20 John Levine via mailop napísal(a): > > It appears that John Capo via mailop <j...@irbs.com> said: > >> The only IPv6 issues I have seen, other than transit only via HE, is > >> delivering to Google. Google seems to assume that mail via IPv6 is > spam. > >> The same mail flow via IPv4 is OK with Google. Proper DNS and all > that > >> stuff, of course. > > > > Google has clearly said that IPv6 mail has to be authenticated. Add DKIM > > signatures and you'll have a lot more success. > > When they try to check DKIM signature when IPv6 connection was refused > at all (redacted): > > 2021-09-03 11:10:19 1mM5DF-0005en-PL <= u...@domain.tld H=servac.skk > [192.168.10.11] S=1899 id=some...@domain.tld > 2021-09-03 11:10:19 1mM5DF-0005en-PL H=gmail-smtp-in.l.google.com > [2a00:1450:400c:c07::1b] Connection refused > 2021-09-03 11:10:21 1mM5DF-0005en-PL => 026...@gmail.com R=dnslookup > T=remote_smtp H=gmail-smtp-in.l.google.com [74.125.133.27] C="250 2.0.0 > OK h13si4784520wrs.127 - gsmtp" QT=3s DT=1s > 2021-09-03 11:10:21 1mM5DF-0005en-PL Completed QT=3s > > regards > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop >
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
