Re: [mailop] SPF notification question
I have an automated system in place for our customers, partners, and friends domains to catch that and then I make them aware. There’s currently about 108 on my list that are broken. I’m not going to put a spotlight on everyone, but here’s a list of .edu domains: ashland.edu dmu.edu sdstate.edu usd.edu If anyone has some good connections to those schools, please send a note of encouragement. Success rate is about 5 to 10%. If I get a response from someone in the first few days after my first note then it’s usually 80% chance it will be resolved in two weeks. There’s some who think that the problem is our spam filtering server and lot of confusion on who/where to send my note – I usually encourage their IT consultant/department or their email or DNS resource. Frank From: mailop On Behalf Of Liam Fisher via mailop Sent: Thursday, June 04, 2020 9:05 AM To: mailop@mailop.org Subject: [mailop] SPF notification question Quick question to the hive mind about SPF. What do you usually do for domains that have broken SPF records? I mean the ones affecting your inbound to local delivery. Do you notify the sender and what's the usual process? ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] SPF notification question
Wow! Open ended question, and also depends on the SPF record.. Some you WANT to block at the edge (aside from the whole email forwarding thing) and some you may simply want to filter. But by rejecting, that IS a notification .. hehehe.. However, for many individuals out there trying their best to run an email server, they have a hard enough time getting DNS right... let alone SPF.. This is where is is probably best to 'be kind to the animals'.. UNLESS of course, it is something important that is likely to get forged/faked/phished like a bank. But in reality, most of us are too busy to spend time on reporting.. Assume if it is broken, they will notice pretty quickly anyways.. The big guys rejecting your email is often when people first start looking at SPF.. But during this difficult time, we want to be nice to our neighbours when we can be, and phishing attack rates never higher.. So, if you can spare the cycles.. sure.. why not.. But when a bank screws up on their SPF.. yeah, the best thing is to block them, and that will get their attention ;) For them, we need to set them to higher standards.. IMHO Other opinions? On 2020-06-04 7:05 a.m., Liam Fisher via mailop wrote: Quick question to the hive mind about SPF. What do you usually do for domains that have broken SPF records? I mean the ones affecting your inbound to local delivery. Do you notify the sender and what's the usual process? -- "Catch the Magic of Linux..." Michael Peddemors, President/CEO LinuxMagic Inc. Visit us at http://www.linuxmagic.com @linuxmagic A Wizard IT Company - For More Info http://www.wizard.ca "LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd. 604-682-0300 Beautiful British Columbia, Canada This email and any electronic data contained are confidential and intended solely for the use of the individual or entity to which they are addressed. Please note that any views or opinions presented in this email are solely those of the author and are not intended to represent those of the company. ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] SPF notification question
On Thu, 4 Jun 2020 10:05:02 -0400 (GMT-04:00), Liam Fisher via mailop wrote: >What do you usually do for domains that have broken SPF records? SpamAssassin adds 7.5 points, enough for classification as spam, absent any mitigating factors. This is generally a desired outcome. >Do you notify the sender and what's the usual process? I can't imagine doing that. There would be hundreds of notifications daily to domains used once by spammers (or misused by spammers) with no practical outcome that I can perceive. And my day job is our customers' deliverability. mdr -- Sometimes half-ass is exactly the right amount of ass. -- Wonderella ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] SPF notification question
Dnia 4.06.2020 o godz. 10:05:02 Liam Fisher via mailop pisze: > What do you usually do for domains that have broken SPF records? I > mean the ones affecting your inbound to local delivery. Well, as SPF is a fundamentally flawed idea, I don't check SPF (nor DKIM, nor DMARC) at all on incoming mail. I only use them on outbound mail, mostly to satisfy Google ;). In my opinion, the only case you should care about SPF is when a domain publishes "-all" as the ONLY entry in the SPF record, ie. it indicates that it doesn't send mail at all. (But I don't even bother to check this :)) I rather like to rely on old fashioned methods like RBLs, manual black/white lists and content analysis for spam filtering. -- Regards, Jaroslaw Rafa r...@rafa.eu.org -- "In a million years, when kids go to school, they're gonna know: once there was a Hushpuppy, and she lived with her daddy in the Bathtub." ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
[mailop] SPF notification question
Quick question to the hive mind about SPF.What do you usually do for domains that have broken SPF records? I mean the ones affecting your inbound to local delivery.Do you notify the sender and what's the usual process? ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
