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

Newsletter subscribers cannot reply directly via the newsletter to [email protected] (the sender) #3213

Closed
CGiattino opened this issue Feb 19, 2024 · 7 comments

Comments

@CGiattino
Copy link

CGiattino commented Feb 19, 2024

Description

Replies to mailchimp newsletter issues are not delivered or end up in spam.

sequenceDiagram
    Mailchimp->>Subscriber: Send campaign ✅
    note right of Subscriber: the subscriber hits "reply"<br>in their mail client (e.g. gmail).<br>This copies the content of<br>the campaign below their<br>actual reply.
    Subscriber->>Our World in Data: reply to ❌
Loading
  1. newsletter is sent by Mailchimp (reply-to: [email protected])
  2. subscriber receive newsletter
  3. subscriber hits "reply"
  4. email is sent to [email protected]
  5. email is not delivered (or end up in spam)

Charlie tried this multiple times and it was never delivered.

It seems to be something with the newsletter content itself — Charlie copied the newsletter contents to a fresh email to newsletter@, and it also was not delivered. But simply emailing newsletter@ a test email without any newsletter contents does work.

As a baseline, sending the email to both [email protected] and a disposable email at the same time:

More slack discussion here

Expected behaviour

Replies to the newsletter get delivered to us.

Context

@mlbrgl
Copy link
Member

mlbrgl commented Feb 20, 2024

@CGiattino partially rewritten description and shared with Mailchimp support

@mlbrgl
Copy link
Member

mlbrgl commented Feb 20, 2024

Their reply:

So after running a few test it looks like youre domain is fine. What I do see id you have a few free domains attached to account, it may be best to remove the google domains, as they do carry limitations
Limitations of Free Email Addresses: https://eepurl.com/dyil9c
Also if you if you see specific adresses effected this process may help those contacts as well,
Use Safe Sender Lists to Stay out of Spam Folders: https://eepurl.com/dyikij,

@CGiattino
Copy link
Author

huh, so besides the several spelling/grammar errors, what do you make of their reply — some things to investigate that might help with this?

@mlbrgl
Copy link
Member

mlbrgl commented Feb 21, 2024

I asked for clarification today:

I went through the two links you shared, and they both relate to emails sent from Mailchimp, whereas my question was about the deliverability of replies to these emails (❌ below).

sequenceDiagram
    Mailchimp->>Subscriber: Send campaign ✅
    note right of Subscriber: the subscriber hits "reply"<br>in their mail client (e.g. gmail).<br>This copies the content of<br>the campaign below their<br>actual reply.
    Subscriber->>Our World in Data: reply to ❌
Loading

Would you have any insights about this particular issue?

@mlbrgl
Copy link
Member

mlbrgl commented Feb 28, 2024

Skipping a back-and-forth for clarification, Mailchimp support suggested a possible workaround, by letting Mailchimp manage replies:

So this would be using the the domain that is sent with to manage replies. We also have a great way to manage campaign replies within Mailchimp as well. If you take a look at this page here: Set Up Your Mailchimp Inbox: https://eepurl.com/hcaXDr

This will allow you to have your own inbox within Mailchimp to manage replies that come in from your sent content.

Worth evaluating the cost/benefit. This would require some workflow adjustments.

@CGiattino
Copy link
Author

thanks @mlbrgl for looking into this — I'll discuss with @matt-mun

@ikesau
Copy link
Member

ikesau commented Mar 27, 2024

Without doing anything this seems to have been fixed 🤷

@ikesau ikesau closed this as completed Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants