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

Email from bugs.nyc1.psf.io generates email that soft fail SPF checks #546

Closed
rouilj opened this issue Jan 11, 2025 · 0 comments · Fixed by #549
Closed

Email from bugs.nyc1.psf.io generates email that soft fail SPF checks #546

rouilj opened this issue Jan 11, 2025 · 0 comments · Fixed by #549

Comments

@rouilj
Copy link
Contributor

rouilj commented Jan 11, 2025

Reported on the roundup issue tracker at: https://issues.roundup-tracker.org/issue2551388

It looks like the python.org SPF record doesn't include bugs.nyc1.psf.io host/address as a valid
source of python.org emails.

Maybe adding a:bugs.nyc1.psf.io or ip4:167.71.181.142/32 to the existing

   v=spf1 mx a:mail.wooz.org ip4:188.166.95.178/32  ip6:2a03:b0c0:2:d0::71:1 include:stspg-customer.com include:_spf.google.com include:mailgun.org ~all

can fix the issue, but I don't remember the length limit on an SPF record.

Thanks for your help.

ewdurbin added a commit that referenced this issue Jan 15, 2025
Towards #546, allows us to set SMTP settings on a per-tracker basis.

Adds some sample secrets for roundup to emulate what we have in prod and demonstrate this feature.
ewdurbin added a commit that referenced this issue Jan 15, 2025
Towards #546, allows us to set SMTP settings on a per-tracker basis.

Adds some sample secrets for roundup to emulate what we have in prod and demonstrate this feature.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant