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

Fix mailchimp spam issue + custom domain email #75

Closed
jessesquires opened this issue May 19, 2020 · 7 comments
Closed

Fix mailchimp spam issue + custom domain email #75

jessesquires opened this issue May 19, 2020 · 7 comments
Assignees
Labels
bug A bug on the website

Comments

@jessesquires
Copy link
Member

jessesquires commented May 19, 2020

Reports that emails are going to spam because sender domain (@protonmail) is not owned by us.

Investigate getting an @techworkersco email address.


DNS records

  • Create a CNAME record for k1._domainkey.techworkerscoalition.org with value dkim.mcsv.net
  • Create a TXT record with this value: v=spf1 include:servers.mcsv.net ?all

Docs

The article below has information on what needs to be changed. Set Up Custom Domain Authentication: DKIM and SPF: http://eepurl.com/b43Lqb

If protonmail.com is not your domain (which it looks like it may be a free email service) then you may consider instead getting a custom domain to send from. The following two articles give a bit more context:

Limitations of Free Email Addresses: https://eepurl.com/dyil9c
Purchase a Domain in Mailchimp: https://eepurl.com/gtdfG5

@jessesquires jessesquires added the enhancement Improvement or fix label May 19, 2020
@jessesquires jessesquires self-assigned this May 19, 2020
@jessesquires jessesquires added bug A bug on the website and removed enhancement Improvement or fix labels May 19, 2020
@jessesquires jessesquires changed the title Fix mailchimp spam issue Fix mailchimp spam issue + custom domain email May 21, 2020
@jessesquires
Copy link
Member Author

@techworkersco/newsletter-folks This is now completed. 🎉

Emails will be sent from news-noreply@techworkerscoalition.org. The domain is verified and authenticated.

This is a "no-reply" address to send from only. We will still use our proton mail account for everything else.

@anaulin
Copy link
Member

anaulin commented May 23, 2020

Nice. Thanks for sorting this out, @jessesquires 😻

@stationaery
Copy link
Collaborator

stationaery commented May 23, 2020 via email

@anaulin
Copy link
Member

anaulin commented May 24, 2020

I can think of two reasons:

  1. Administration and maintenance overhead.
  2. It makes having an encrypted Protonmail account moot if we're forwarding email through other, presumably un-encrypted, services.

That said, I don't know if we care about having an encrypted Protonmail account for this. In which case, if it was possible to set up a @techworkerscoalition.org account, that might be nicer than using the Protonmail one. Would require some more set up and relying on whoever runs techworkerscoalition.org to help administer it, though.

@stationaery
Copy link
Collaborator

stationaery commented May 24, 2020 via email

@dellsystem
Copy link
Collaborator

thanks for sorting this @jessesquires!

I personally never pay attention to whether an email address is no-reply so I don't really mind that. The protonmail email is listed at the bottom of the email, right?

@jessesquires
Copy link
Member Author

The protonmail email is listed at the bottom of the email, right?

Correct. The "email us" link goes to proton mail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A bug on the website
Projects
None yet
Development

No branches or pull requests

4 participants