Mail subdomain problem

Product Support Self-hosting

AI-generated summary

Mail Subdomain Problem

rodseb is experiencing an issue with their Discourse setup, specifically with the mail subdomain. They have followed the troubleshooting guide and made the necessary modifications, but are still encountering a Net::ReadTimeout error when sending emails.

Their Discourse configuration includes:

DISCOURSE_SMTP_ADDRESS: mail.spm-corp.fr
DISCOURSE_SMTP_PORT: 465
DISCOURSE_SMTP_USER_NAME: XXXX@spm-corp.fr
DISCOURSE_SMTP_PASSWORD: "XXXXXXXXXXXX"
DISCOURSE_SMTP_DOMAIN: spm-corp.fr
DISCOURSE_NOTIFICATION_EMAIL: XXXX@spm-corp.fr

Despite resetting the Discourse folder and discourse_docker, the issue persists. Stephen inquired about the domain specified in the error message, while JammyDodger noted that the topic was previously marked as solved but lacks a solution.

1

Hello,
I have a weird problem, I have done the commands and modifications, but I still have this error.

  ## TODO: The SMTP mail server used to validate new accounts and send notifications
  # SMTP ADDRESS, username, and password are required
  # WARNING the char '#' in SMTP password can cause problems!
  DISCOURSE_SMTP_ADDRESS: mail.spm-corp.fr
  DISCOURSE_SMTP_PORT: 465
  DISCOURSE_SMTP_USER_NAME: XXXX@spm-corp.fr
  DISCOURSE_SMTP_PASSWORD: "XXXXXXXXXXXX"
  #DISCOURSE_SMTP_ENABLE_START_TLS: true           # (optional, default true)
  DISCOURSE_SMTP_DOMAIN: spm-corp.fr

  DISCOURSE_NOTIFICATION_EMAIL: XXXX@spm-corp.fr

I edited and ran the command

rails r "SiteSetting.notification_email ......

nothing wants to work
I always have this error

  Rendered layouts/email_template.html.erb (Duration: 0.3ms | Allocations: 34)
Delivered mail 87e79779-6693-4fa2-b5f3-3647b6e19768@forums.spm-corp.fr (5043.4ms)
Job exception: Net::ReadTimeout

the Discourse link is forums.spm-corp.fr
I have no communication problem between the mail server and Discourse
I even reset the Discourse folder and that of discourse_docker

Thank you for your help

I’m sorry if this topic has already been discussed.

2

Have you modified the error message to show discourse.example.com, or is that the domain specified on your site?

4

I put discourse.example.com to camouflage the domain, but yes it is a personal domain

I edited to make it more comprehensive

5

I spotted that this topic had been marked as solved, but it doesn’t appear to contain a solution. Did you get everything sorted in the end @rodseb?