tag:blogger.com,1999:blog-11363338361980298.post885781431401845021..comments2024-03-07T16:47:43.989-05:00Comments on Contoso.one: Setting up email for Brand Protection domainsKevin Chttp://www.blogger.com/profile/08785413212771476129noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-11363338361980298.post-27936740492887873072023-06-01T12:04:35.262-04:002023-06-01T12:04:35.262-04:00Hi! That's a great question!
No. Not really.
...Hi! That's a great question!<br />No. Not really. <br />The best that you can do is use something like an Exchange Transport Rule to say "if SPF Fails, reject the message with a custom error" <br /><br />But I say "not really" because this is an EXTREMELY time consuming process and you are cutting your domain off from being able to receive an ENORMOUS portion of ALL EMAILs sent in the world. <br /><br />It is frankly astounding how many companies that are quite established don't have the basic level of a minimal SPF, or aren't just basically allowing everything with ?all or even literally +all<br /><br />The only hope you have of enforcing this on them is rejecting their emails, with a message that they should contact IT, perhaps. If you accept their emails, but just mark them as "Insecurely delivered" then the sending company basically NEVER cares enough to fix it. Kevinhttps://www.blogger.com/profile/04650521821118072860noreply@blogger.comtag:blogger.com,1999:blog-11363338361980298.post-12859022562270693042020-12-07T09:54:15.830-05:002020-12-07T09:54:15.830-05:00Hi,
Is there any possibility to enforce SPF on t...Hi, <br /><br />Is there any possibility to enforce SPF on the multiple third party domains (domains that we don't manage and/or administer) from our side? We can implement SPF on the email domains that we owned. Please shed light on this. RADIOHEADhttps://www.blogger.com/profile/16048824654996482845noreply@blogger.com