-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
implement inbound email reports for roundup #354
Conversation
CC @rouilj |
Resulting files (note hostname will be different since this was rendered from local dev, specifically
|
Hmm:
in main.cf looks suspect. I think it needs to be:
I think you want to replace:
with something like (been years since I last salted my systems so this might need work):
So you are using the tracker email domains rather than the web SAN domains. issues.roundup-tracker.org and mail.roundup-tracker.org are cnamed to bugs.python.org. Also did you want to add a warning like:
to the top of The rest looks good. Thanks for your fast work on this. |
Thanks for the review @rouilj. My only concern is that we don't have a valid TLS cert for roundup-tracker.org for Postfix to serve, since we fetch via LetsEncrypt and share the cert between the HTTP front-end (nginx) and postfix. I'm going to ship this and we'll see. |
I got the expedited Delivery Status Notifications and successfully submitted (and closed) an issue on the roundup tracker. Calling this closed. |
Resolves #352