https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7517
--- Comment #4 from Kevin A. McGrail <kmcgr...@apache.org> --- For completeness, here is the on-list reply Hi Seda, A bug such as this is as akin to contacting a wrench/spanner maker because your car won't start. At the ASF, we produce Free, Open Source Software that can be used by anyone and everyone however they choose. The issue relayed below is an implementation concern with frankweyer.com and ruralroute.com as I am not aware of any default rules that specifically target the .link TLD. You'll need to contact them and discuss the issue. Or if you can point to a problem in the tool (not the implementation), we would be happy to reconsider. However, extrapolating further Re: .link and my experience is that Uniregistry contacted me in October and I'm monitoring their TLD to identify if they have been able to be a handle on the previous abuse that plagued the TLD. There are problems that might be getting resolved with the TLD but if you are speaking officially for ICANN, What feedback can you provide about abuse with specific TLDs? For example, .stream, .trade, .pw, .top, .press, .bid & .date are fraught with problems. Please feel free to reach out to me at www.linkedin.com/in/kmcgrail so we can talk further offline. Regards, KAM -- You are receiving this mail because: You are the assignee for the bug.
