Can't change the no-reply email for newsletters

Hey,

I’ve installed Ghost on digitalocean, and configured mailgun to send emails according to the guides.

It now sends newsletters from no-reply@mydomain.com, but when I try to change the from address in newsletter settings, it won’t save and just says “retry” in red.

I also changed the SMTP settings to add a from address, but it has no effect.

What am I doing wrong?

3 Likes

same for me. surprised there are no replies or help on this yet.

Any luck figuring this out? I am running into the same issue unfortunately.

You cannot change the no-reply without having a domain email. Check my tutorial at Cách tạo email tên miền riêng miễn phí với Cloudflare từ A-Z

Feel free to use Google translate to English

Thanks cuongtran. I’ve got my own custom mail.domain.com configured and working with Mailgun, but when I try to use it with Ghost I encounter the error described in the OP. If I remove the Mailgun API configuration from Ghost (and have it sending email from my Ghost domain blog.domain.com) test email sends, albeit illegitimately since I don’t have the appropriate mail records configured in DNS for blog.domain.com.

You are sure about you setup Mailgun SMTP config.production.json on ghost installation? This setup for sending transaction emails like this, not Mailgun API.

Hey cuongtran, I didn’t modify any configuration files regarding email. I had reviewed the documentation here and my understanding was configuring the Mailgun API in the UI was intended for newsletter delivery: Why do I have to set up Mailgun for newsletters?Bulk email delivery for newsletters is a new feature which requires a bulk mail API. Currently the only bulk mail API we support is Mailgun.”

I ended up deciding not to use Ghost for newsletters for a few different reasons including this one, but I do appreciate you providing assistance!

It is related to some Openssl errors (check your logs “ghost log”

EASY TO FIX: update your config.production.json mail config and then restart ghost.

“secure”: true,
to
“secure”: false,

Should be something like this:

“mail”: {
“transport”: “SMTP”,
“options”: {
“service”: “Mailgun”,
“host”: “smtp.mailgun.org”,
“port”: 587,
“secure”: false,
“auth”: {
“user”: “—address”,
“pass”: “—pass”
}
}
},

Mailgun supports encrypted SSL connections. Consider if there’s another way to solve that error, like upgrading OpenSSL.