Skip to content

Set Hour of Code Email Reply-To Field - #47996

Merged
sureshc merged 2 commits into
stagingfrom
set-hourofcode-email-replyto
Sep 8, 2022
Merged

Set Hour of Code Email Reply-To Field#47996
sureshc merged 2 commits into
stagingfrom
set-hourofcode-email-replyto

Conversation

@sureshc

@sureshc sureshc commented Sep 8, 2022

Copy link
Copy Markdown
Contributor

Google Mail (and possibly other email providers) are frequently classifying Hour of Code sign up email receipts as spam due to DKIM and DMARC failing. Account Sign Up and Password Reset emails are transmitted with much of the same code and the same AWS Simple Email Service configuration, but are typically passing DKIM and DMARC and are typically NOT being classified as spam.

After reviewing differences between the email headers between the two types of emails, speculatively set the Reply-To SMTP header in Hour of Code sign up email receipts.

Links

Testing story

Deployment strategy

Follow-up work

Privacy

Security

Caching

PR Checklist:

  • Tests provide adequate coverage
  • Privacy and Security impacts have been assessed
  • Code is well-commented
  • New features are translatable or updates will not break translations
  • Relevant documentation has been added or updated
  • User impact is well-understood and desirable
  • Pull Request is labeled appropriately
  • Follow-up work items (including potential tech debt) are tracked and linked

@sureshc
sureshc requested review from a team and breville September 8, 2022 00:32
@@ -1,5 +1,6 @@
---
from: "Hadi Partovi (Code.org) <hadi_partovi@code.org>"
reply-to: hadi_partovi@code.org

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we use noreply@code.org here?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Emails sent to hadi_partovi@code.org get routed to Support, which can be convenient for people to be able to get help.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we can try this in two phases? First check whether specifying a reply-to improves delivery? And then switch to noreply?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The two-phase approach SGTM!

@sureshc
sureshc merged commit ad1c554 into staging Sep 8, 2022
@sureshc
sureshc deleted the set-hourofcode-email-replyto branch September 8, 2022 14:13
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 this pull request may close these issues.

4 participants