I can confirm the bug is still there.
Version: 5.54.0
I also confirm that:
- Emails are being sent successfully via Mailgun
- I can change email sender in newsletter settings (via email confirmation sent and I receive it)
- I can change support email for Portal (via email confirmation and I receive it)
- I receive service emails from my ghost instance about new subscribers signing up.
As far as I can see, everything works fine. I have no idea why this notice is present.
This line in Ghost’s source code checks if direct email service is being used and the error originates from this assumption. But in the same time, in the screenshot above, Ghost correctly recognises I am using SMTP. So, what gives the error? I hope Ghost team will be able to investigate it. Apart from that, this notice does not bother me much.
Here’s email part of my config.production.json
"mail": {
"from": "join@domain.com",
"transport": "SMTP",
"options": {
"service": "Mailgun",
"host": "smtp.eu.mailgun.org",
"port": 465,
"secure": true,
"auth": {
"user": "name@subdomain.domain.com",
"pass": "passwordliveshere"
}
}
},
There’s one more report at this forum about the same bug: Ghost is currently unable to send email - But it can (just linking for… things to be linked)
P.S. Could we please edit this topic title? It would better be:
Ghost is currently unable to send email - Incorrect notification