How can I increase the non matching SPF spam score?
In WHM 110, is there a way to increase the non matching SPF rule score? For some reason, somebody sending me an email with an envelope from MY OWN EMAIL can get through my Thunderbird's inbox with a tiny score. Normally, a non matching SPF record should score WAY HIGHER than "1.5", see below:
0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.5000]
1.5 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail)
X-Spam-Flag: NO
According to this thread from 5 years ago, the non matching SPF record should score like 4.0 or something like that?
-
It might help if you change "~all" (softfail) to "-all" (fail) in your SPF record. 0 -
So, being a dedicated server with tons of customers on it, am I expected to go in more than 100 accounts and manually edit all the ~all for -all one by one? This will take all day. If I could just increase the rule from score +1.5 to like +6.0 somewhere in WHM that would fix the whole issue in a second. 0 -
A couple thoughts. There's usually an automated way to do just about everything. A careful regex script could likely update all the DNS records to replace the character in the DNS zones, although you would then need to update the serial number as well. If you want the SPF to fail, it really should be setup with the hard fail - option instead of ~ at the DNS level as that just eliminates one more place of confusion. We do have an option inside cPanel (not globally) to adjust the value in cPanel >> Spam Filters >> Calculated Spam Score Settings (under the Advanced section) so you could make the change there. This is per account though, but the file just writes this code: score SPF_FAIL 6.0
to the /home/username/.spamassassin/user_prefs file for the account. You could make a script to manually add that line to each user's file on the system. That's the only ways I can come up with help automate this process.0 -
So, being a dedicated server with tons of customers on it, am I expected to go in more than 100 accounts and manually edit all the ~all for -all one by one? This will take all day. If I could just increase the rule from score +1.5 to like +6.0 somewhere in WHM that would fix the whole issue in a second.
Just a thought, contact the customers who are affected and give them the few steps needed to login -> zone manager -> edit the record -> save Then you're only really doing it once and leveraging your customers to act upon and understand why changes are being made to their zones. Teach a man to fish, etc.0 -
Nice catch, @phil99 - with that support article being less than 2 months old, even I wasn't aware! 0
Please sign in to leave a comment.
Comments
7 comments