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
from
mail setting is ignored for signup emails
#15222
Comments
Duplicate of #15191 |
Hi @ErisDS. Thank you for commenting. Yes it is a duplicate of #15191, but that one got closed. And I do still believe that this is unexpected behavior. The signup email does use the So the reason this is unexpected behavior, is because when inviting a staff member, the entire Please let me know if I can provide any more information. And thank you for looking into this! :) |
I also just noticed that when a subscriber is logged in, the I think that the blog owner, should be able to set the support email address? Letting users sent an email to a |
I closed the other issue as a support request and routed the opener to the forum. The same is true for you. You're asking for help on how to use a feature, and that request for help does not belong on GitHub. |
Issue Summary
My email setting in
config.production.json
looks like this:This config works for the emails sent to invited staff members. For these emails the correct
from
email address as specified in the above config is used.But when someone subscribes, the email with the signup link they receive is sent from
noreply@<blog-domain>
. I.e. thefrom
as specified in the config, is not used here.Given that this is a transactional email and not a newsletter (bulk/mass) email, I would expect that that the mail config is used.
Please let me know if there is any more info I can provide. :)
Thank you so much for your time and effort looking into this!
Steps to Reproduce
Ghost Version
5.8.0
Node.js Version
v16.16.0
How did you install Ghost?
Self hosted - AWS
Database type
MySQL 8
Browser & OS version
No response
Relevant log / error output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: