this post was submitted on 26 Apr 2025
43 points (100.0% liked)
Cybersecurity
0 readers
53 users here now
An umbrella community for all things cybersecurity / infosec. News, research, questions, are all welcome!
Rules
Community Rules
- Be kind
- Limit promotional activities
- Non-cybersecurity posts should be redirected to other communities within infosec.pub.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
@Jerry@hear-me.social
There is 2 mechanisms against this.
Your provider should check these.
Many providers don't accept email if one is missing or wrong, or flag theses emails as spam.
@lautreg SPF and DKIM are only used by the destination IMAP or POP3 servers to see what to do when they receive the email. In this case they reject it.
The delivery failure message is coming from the sending server as a courtesy message to the sender to let them know their email was not delivered. The protocol is to tell the FROM: address that the email could not be delivered. The SMTP, sending server, doesn't look at SPF, DKIM or DMARC or any DNS records or any other configuration related to it. It simply tells you the millions of emails sent with your FROM: address could not be delivered, one by one.
People keep bringing up SPF, DKIM, and DMARC, but it's not relevant to this problem.
@Jerry@hear-me.social
Oh yes.
I can't check, but I think there is setting to refuse connexion with the sender server if SPF doesn't mach.
Like the policy in the DMARC?
Or, in spamd/spamassassin, to just drop the incoming email in these case?
(I'm on phone, I may write more wrongly than usual)