Email Sending Issues Occured on Different Email Provider on notification_email and reply_by_email_addresses

sptrf · August 28, 2021, 11:51am

Hello, recently I’ve encountered some issues on configuring the email sender as QQ Exmail (a.k.a 腾讯企业邮箱). My email configuration is listed as below:

DISCOURSE_SMTP_ADDRESS: smtp.exmail.qq.com
DISCOURSE_SMTP_AUTHENTICATION: login
DISCOURSE_SMTP_ENABLE_START_TLS: true
DISCOURSE_SMTP_OPENSSL_VERIFY_MODE: none
DISCOURSE_SMTP_PORT: 587
DISCOURSE_SMTP_USER_NAME: username@domain.tld
DISCOURSE_SMTP_PASSWORD: ***

I’ve also configured the notification_email in the setting panel.

However, when I tried to send test email from the panel, the system always returns that 501 mail from address must be same as authorization user .

I’ve double checked that the DISCOURSE_SMTP_USER_NAME and the notification_email are the same email address, and my SMTP settings also passed the test on SMTP Test Tool .

As I currently have no idea which part of my email configuration, may it be any way for me debug the issue or check the raw email that the discourse instance tried to send in order for me to diagnostic whether the from: address section of the email is correct?

Any help or comment is highly appreciated.

Here are some posts that I referenced for configuring the email.
https://community.jenkins-zh.cn/t/discourse/202

sptrf · August 28, 2021, 3:13pm

After some investigation, I guess this problem may be related to the conflict between the notification_email and reply_by_email_addresses. When the two variables are both configured, the outgoing email seems using reply_by_email_addresses as their from: address, which may be related to the code below:

github.com

discourse/discourse/blob/1472e47aae5bfdfb6fd9abfe89beb186c751f514/lib/email/message_builder.rb#L240

    
      
              end
          end
          
          
def alias_email(source)
            return source if @opts[:from_alias].blank? &&
              SiteSetting.email_site_title.blank? &&
              SiteSetting.title.blank?
          
          
  if @opts[:from_alias].present?
              %Q|"#{Email.cleanup_alias(@opts[:from_alias])}" <#{source}>|
            elsif source == SiteSetting.notification_email || source == SiteSetting.reply_by_email_address
              site_alias_email(source)
            else
              source
            end
          end
          
          
def site_alias_email(source)
            from_alias = Email.site_title
            %Q|"#{Email.cleanup_alias(from_alias)}" <#{source}>|
          end

However, when I switch the notification email to office 365 with the similar SMTP configuration, the email sends without any problem.

  #DISCOURSE_SMTP_ADDRESS: outlook.office365.com
  #DISCOURSE_SMTP_AUTHENTICATION: login
  #DISCOURSE_SMTP_ENABLE_START_TLS: true
  #DISCOURSE_SMTP_PORT: 587
  #DISCOURSE_SMTP_USER_NAME: 365@domain.tld
  #DISCOURSE_SMTP_PASSWORD: ***

Guessing the reason for this different behavior may be that office365 does not verify the from: field when sending mail, but only rewrites the from: field to the username of the office365 account when sending mail, and QQ Exmail will verify the from field of the sent mail, while incorrect from: field could cause the 501 error mentioned above.

Topic		Replies	Views
SMTP setting problem with Office365 Installation	6	2794	March 11, 2022
SMTP with office365? Installation email	13	7026	June 8, 2024
SMTP unrecognized authentication type with Office 365 Installation email	14	25104	March 3, 2023
Sending emails not working Installation	13	3780	August 9, 2021
Email not working (SSL_connect returned=1) Installation	16	2251	July 15, 2022

Email Sending Issues Occured on Different Email Provider on notification_email and reply_by_email_addresses

Related Topics