Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

softfail SPF for Valimail #155

Open
amcl61 opened this issue Jul 27, 2022 · 3 comments
Open

softfail SPF for Valimail #155

amcl61 opened this issue Jul 27, 2022 · 3 comments
Labels
enhancement New feature or request
Milestone

Comments

@amcl61
Copy link

amcl61 commented Jul 27, 2022

Hello,

We use the Valimail product for DMARC which their spf macro uses softfail, ~all, sample below. We are receiving "Not Recommended -5" on our domains and subdomains.

v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all

There are other companies using their product for DMARC eg. Uber.com

I've attached their document as to why they use softfail instead of hardfail and would like the SPF area for "Set up SPF records to prevent spoofing" to consider not marking these as needing improvement and instead as ok.

https://support.valimail.com/support/solutions/articles/48001197890-why-valimail-uses-an-spf-soft-fail-and-not-a-hard-fail

Thank you,

@cammurray
Copy link
Owner

@amcl61 cheers for the article. IMO the advice is only really valid in instances where DMARC is deployed and in some level of enforcement (which still sucks how many organizations are not here yet).

Possibly what we could do here is consider SPF soft-fail informational in instances of a p=reject/p=quarantine DMARC policy on the matching domain. The only concern here that i have is instances of subdomains this is going to become a bit complicated (SPF needs explicit records on the subdomain where DMARC falls back down the chain in absence of an explicit record at the subdomain).

@cammurray cammurray added the enhancement New feature or request label Aug 2, 2022
@amcl61
Copy link
Author

amcl61 commented Aug 24, 2022

Thanks Cam!

@cammurray
Copy link
Owner

Bumping in to vnext.

@cammurray cammurray added this to the vnext milestone Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants