I’ve just spawned a new instance of Discourse and didn’t have valid settings for DISCOURSE_SMTP_*
.
However, signing up the admin user allegedly worked:
(of course, no email had been sent)
Same problem with re-sending the activation email:
I’ve just spawned a new instance of Discourse and didn’t have valid settings for DISCOURSE_SMTP_*
.
However, signing up the admin user allegedly worked:
(of course, no email had been sent)
Same problem with re-sending the activation email:
Could it be because only DISCOURSE_SMTP_ADDRESS
is checked to exist?
https://github.com/discourse/discourse_docker/blob/master/templates/web.template.yml#L24
What exact settings did you have? I don’t feel this is a bug, more of GIGO.
Mail is sent in a background job, there is no simple way of alerting an end user about this kind of issue
We could probably raise the volume for admins
It is flag worthy when mail suddenly stops working
That would already be covered by logster escalating alerts for periods with lots and lots of recurring errors, the work that @tgxworld is doing.
Exactly. I had all the other SMTP settings commented out, so in theory this is WAI, but in practice most SMTP servers will require user/pass too.