When Websites Won’t Take No for an Answer

Re:When Websites Won’t Take No for an Answer by jlgaddis on Saturday May 14, 2016 @03:32PM (#11697683)

If I didn't run my own mail systems, that's what I would do.

Instead, I just blacklist the sender's IP address. It's even nicer when the sender (e.g. LinkedIn) publishes TXT RRs for SPF in their DNS zone as it allows me to easily blacklist all of them.

[ Parent | on HN ]

Re:When Websites Won’t Take No for an Answer by dredmorbius on Saturday May 14, 2016 @09:00PM (#11698815)

Note that as more senders use mail service providers, comprehensive blocking of all SPF records may have considerable collateral damage.

Whether you consider this good or bad may vary: it means MSPs have a valid claim that senders exercise Good Citizen practices on all mailings, not just those circulating via the MSP.

Then there are the major players. Yahoo's been a freaking PITA for years on outbound spam (both spam and joe-job bounces), with no effective reporting mechanism. Gmail's been largely better IME, other providers vary.

[ Parent | on HN ]