[BUG] - Can not send mail using an SMTP relay without authentication

[smoofy]

First Check

• This is not a feature request.
• I added a very descriptive title to this issue (title field is above this).
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the Mealie documentation, with the integrated search.
• I already read the docs and didn't find an answer.
• This issue can be replicated on the demo site (https://demo.mealie.io/).

What is the issue you are experiencing?

Unable to send email with a Google Workspace SMTP Relay service configured with no authentication.

Steps to Reproduce

Mealie mail configuration:

SMTP_HOST: smtp-relay.gmail.com
SMTP_PORT: 587
SMTP_AUTH_STRATEGY: NONE
SMTP_FROM_NAME: Mealie
SMTP_FROM_EMAIL: [email protected]

Relay configuration:

Allowed Senders: Only addresses in my domains
Only accept mail from the specified IP addresses: ON
Allowed IP addresses: Home
Require SMTP Authentication: OFF
Require TLS encryption: ON

Please provide relevant logs

(550, b"5.7.1 Invalid credentials for relay [my.ip.address]. The IP address you've
5.7.1 registered in your Workspace SMTP Relay service doesn't match the
5.7.1 domain of the account this email is being sent from. If you are
5.7.1 trying to relay mail from a domain that isn't registered under your
5.7.1 Workspace account or has empty envelope-from, you must configure your
5.7.1 mail server either to use SMTP AUTH to identify the sending domain or
5.7.1 to present one of your domain names in the HELO or EHLO command. For
5.7.1 more information, go to
5.7.1 https://support.google.com/a/answer/6140680#invalidcred - gsmtp", '[email protected]')

Mealie Version

Docker image v2.3.0 d6de0d0b3d3ffd63a72ac75eec43c4802c3dcc31

Deployment

Docker (Synology)

Additional Deployment Details

No response

[nakal]

I want to confirm a variant of this bug. For me the setting SMTP_AUTH_STRATEGY: TLS implicitly requires that you need a user and password.

It's still wrong. Because TLS is just transport encryption. It has nothing to do with authentication.

I created a user account on my internal MTA, so it doesn't bother me anymore.