Am 10.06.21 um 17:00 schrieb Vytis Marciulionis via mailop: > > Hello mailbox providers, > > > > Recently we have introduced anew /24 IP range to our mail sending > infrastructure: > > 45.86.119.0/24 > > > > This is not a new process and we did not encounter any issues before. > However, initially this particular range came > with geolocation being registered to Turkey in RIPE. That has, obviously, > caused some mailbox providers, that check IP > address geolocationof incoming emails, to recognize it as IP sending emails > that originate from Turkey and thathas > caused delivery issues. > > > > The geolocation of thisnew range was changed around month agobefore we > started any warmups. However,this week we were > informed by one Australian provider that they still had the old geolocation > set for this IP rangeand thus our mails > were strictly rate-limited. If you are a mailbox provider and you check > geolocation as one of the filtering/rate > limiting/sender reputation criteria, could you double check which geolocation > you see for this /24 IP range? Do not > hesitate to get back to me off-list. > I'm using origin.asn.cymru.com lookup (granted, it's not really a geolocation service but it delivers country codes) which still returns TR as the country code for that range:
0.119.86.45.origin.asn.cymru.com. 14290 IN TXT "203501 | 45.86.119.0/24 | TR | ripencc | 2019-06-12" I'm not a big mailbox provider, though, and I'm watching my rules very closely. Country-based rules are only returning 450 temp errors, so this would show up pretty soon on the radar and be fixed in short time as this is a common case for adjustments. Cheers, Hans-Martin
_______________________________________________ mailop mailing list [email protected] https://list.mailop.org/listinfo/mailop
