It appears that Jeffrey Walton <noloader@xxxxxxxxx> said: >Reputation does not seem to work very well in some cases. For example, >I have almost 10,000 pieces of offensive pornographic spam from >Microsoft and its Sharepoint (using domain sharepointonline.com). I >also have a truckload of similar offensive pornographic spam from >Teams (using domain teams.microsoft.com). This is a perverse result of the success of IP reputation. Crooks have largely given up sending directly since their networks' reputation is so bad, so these days they try to set up or hijack accounts at large providers and send mail from there. For reasons I do not understand, Google does a reasonably good job of keeping them out other than annoying whack-a-mole B2B spammers, AWS does a great job, and Microsoft fails completely and gushes spam from onmicrosoft.com and Sharepoint. I haven't seen much Teams spam but maybe I'm just lucky, or it's because I have no Teams account. >> So far, the only mail server I've seen that uses IPv6 with a reverse hostname is Google/gmail. That's great for them to send email, but it does nothing to permit >them to receive email. Let's look at my tiny mail server. $ host gal.iecc.com gal.iecc.com has address 192.55.226.66 gal.iecc.com has IPv6 address 2001:470:1f07:1126:0:43:6f73:7461 $ host 192.55.226.66 66.226.55.192.in-addr.arpa domain name pointer gal.iecc.com. $ host 2001:470:1f07:1126::43:6f73:7461 1.6.4.7.3.7.f.6.3.4.0.0.0.0.0.0.6.2.1.1.7.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa domain name pointer gal.iecc.com. Setting the rDNS is the least of the issues. The IETF's current mail server also has rDNS for both v4 and v6, although for some reason it stopped sending IPv6 mail in March and nobody noticed. R's, John
