Error on login page about SMTP server not being configured

AI-generated summary

R23D_Printing reported a persistent error message on their login page stating “All outgoing email is disabled because no SMTP server has been configured,” despite successful test emails and functional user registrations. Initially, NateDhaliwal suggested using a transactional service, but R23D_Printing clarified they were using a paid Google Workspace account. After following the Google Workspace configuration guide and later switching to Mailgun, all email delivery logs confirmed successful sending, yet the error banner remained. bondero noted experiencing the same issue on a fresh install where SMTP was correctly configured. NateDhaliwal suspected a bug since test emails worked. supermathie confirmed the message was displaying incorrectly and escalated the issue. R23D_Printing temporarily hid the message with a theme component. tgxworld identified the specific regression and linked the fix in pull request #38074. NateDhaliwal confirmed that running ./launcher rebuild app would apply the merged fix, resolving the false error display.

I just noticed this error message on my login page:

All outgoing email is disabled because no SMTP server has been configured. No emails of any kind can be sent.

When i check Admin>Email Settings, I see this:

I can’t post attachments, but I can upload the app.yml file if that helps. I am fairly certain it is correct, but I am new to this.

One thig to note: When I send a test email to my personal Gmail account from this screen, I do receive it.

Any help would be greatly appreciated!

Hi there, you’d need to use a transactional email service, and not Gmail. Something like Brevo or Mailgun.

Can you explain why? We are using a paid Google Workspace account. This isn’t free Gmail. I use this to send email from my WordPress/Woocommerce site just fine. And, honestly, I feel like it is a really working. Or at least people are able to register. So I don’t know… :man_shrugging:t2:

(I might have been mistaken, confused this with Gmail) Hmm… if you’re using Google Workspace, did you follow this guide?

The thing is, it was working (and seems to be working now for Gmail accounts only). I will go through this guide and see if I missed anything.

OK. I went through this entire thing, and still the same thing. I have no idea. Should I try running the setup script again?

I have the same issue.
Fresh install, I mistyped SMTP settings during the install wizard, then I followed the troubleshooting guide, got SMTP correctly configured by fixing containers/app.yml and did a ./launcher rebuild app. Send test email works, signup email verifications work, discourse-doctor is happy too…

I switched over to Mailgun. I seeing the logs that emails are sending. discord-doctor worked to mail-tester.com. Test emails from the Discourse settings to various domains work. So, I’m not sure why the error is still showing up.

To confirm, a rebuild doesn’t work? Are you using Discourse ID?

I’m not sure what that means

Does ./launcher rebuild app help? Are you using Discourse ID? Thanks.

Got you. I assume ./launcher rebuild app is working. I updated the app.yml file, saved it, and ran the command. It went through the rebuild and brought in the new SMTP settings.

I do see “Login with Discourse ID” on the login page. My user account is a local account.

Hmm… that’s odd. This could be a bug, since the test emails do send.

I am on the latest version. Is there any place to report it? Any additional info/files/logs needed?

Could you check out Troubleshooting Outgoing Email? That may help.

Everything as far as the sending of the email looks good. Both the Discourse email logs and the Mailgun logs show successful deliveries. So, I don’t think this is really an SMTP issue at this point. It is something somewhere that is rendering that error incorrectly.

I’ve confirmed this message is displaying at incorrect times and I’ve asked someone to look into it.

YAY!!! I’m glad I’m not crazy!! I created a quick and dirty theme component to hide it until an “official” solution is found.

Can you check this setting?