Currently Ghost uses the name of your publication in the from: name field. This isn’t ideal as real names could increase the open rate of the newsletter… but your publication might not use your real name.
I’d suggest a field to add a custom ‘from’ name in Settings → Email Newsletter.
Even better if the ‘from’ name could be defined by the authors name.
So if you have more writers on your site, the newsletter can have the person who wrote the newsletter/post as sender: For example “Kevin from Ghost” or “John from Ghost” instead of just Ghost.
Maybe even just first and lastname and not the publication name. So I think the ‘from name’ should be a part of the individual post and not in settings.
By default the ‘from’ address for mail sent from Ghost is set to the title of your publication, for example <noreply@your-publication.com> . To override this to something different, use:
Try to use a real, working email address - as this greatly improves delivery rates for important emails sent by Ghost (Like password reset requests and user invitations). If you have a company support email address, this is a good place to use it.
I added this to my configuration file, and I’m still getting emails from:
PUBLICATION NAME <email address defined in Settings>
I know my config file is being read, because I updated the Mailgun settings in the file (improperly), and got an error upon sending an email, then I fixed the config, and mail started working again.
Any idea what to do to force the “from” field to be read?
And requestedFromAddress is being set as the value of message.from. I’m not sure how to trace that value back further. Is it because I have the value for “Newsletter email address” set in my Email Newsletter settings? If so, there’s no way to unset it.
Config is for system emails (staff user invites, etc) - Newsletters are send using a bulk mail API with different settings. Currently it’s not possible to change the ‘from’ name on newsletters, but this is on our roadmap and will be possible in future
For sure. I’ve read through that page, and I was aware of the distinction. But that page doesn’t get into how the from configuration parameter works. That explanation is only on the Configuration Help page, and as far as I can tell, it doesn’t clearly state that the “From” field only applied to Transactional emails.
Furthermore, everything else in the mail part of my configuration field is about bulk mailing, so it stood to reason that the “from” property would similarly apply.