Error 550-5.7.1 when sending emails

Forged

I decided to connect my Mailcow mail server to Authelia so that users could request password recovery via email.

Authelia.conf:

notifier:
#  disable_startup_check: true
  smtp:
    host: mail.domain.com 
    port: 587
    username: auth@domain.com 
    password: MyPass 
    sender: "DreamVR SSO <auth@domain.com>" 
    timeout: 10s

With this configuration, messages are sent, but when sending a message to gmail.com, I receive a message from Gmail:

host aspmx.l.google.com[74.125.205.27] said:
    550-5.7.1 Messages missing a valid Message-ID header are
    not 550-5.7.1 accepted. For more information, go to 550-5.7.1

Indeed, in rspamd this message shows ID: undef.

If I try to send a message to gmail.com from this mailbox through the web UI, the message is sent and the recipient sees it, so the ID is correctly assigned to the message.

I would like to understand how this can be fixed; I did not find any parameters in the Authelia config that could influence this.

DocFraggle

May I ask why you don’t use the Mailcow password recovery option?

Forged

DocFraggle

You probably misunderstood my request. Authelia is an SSO system that I use for authentication in my services. It, in turn, retrieves authentication data from the Active Directory server.

Therefore, there is a possibility that a user may forget their credentials, and to avoid bothering the AD server administrator, I want to give the user the ability to reset their password themselves. Since each user has an email account and there is a Mailcow container running on the server, I decided to simply connect it to Authelia. It automatically sends an email to the user with a link to reset their password from Authelia.

Most of the clients have email accounts mainly on gmail.com.
I mainly use Mailcow for sending notifications and technical information.

Here is how the message looks; as you can see,
the ID: undef

DocFraggle

OK. So if Authelia is sending these mails, did you check this issue? Sounds like your problem, and they are writeing something about a template solution:

authelia/authelia3683

Forged

Indeed, I was using an outdated version of Authelia, prior to the changes made to the Message ID. When I was searching for a solution to the problem, I assumed that even if Authelia didn’t set the ID, Mailcow should handle this and add the headers on its own.

Thank you for helping me look at the problem from a different perspective and quickly resolve it!