You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I understand correctly and how it was working before (but not anymore) connections are refused if they have a user/password when the authentication is off (default).
Currently on 3.3.6. and the "Configuring Clients" wiki page says: "Authentication is not required, but will be accepted if your client insists on their configuration"
The text was updated successfully, but these errors were encountered:
rnwood
changed the title
Connection fails when the client sends in auth credentials while authentication is off
[Bug] Re-introduce 'allow any credentials' mode for SMTP
Apr 23, 2024
Thanks for pointing out this regression in features and docs that need to be updated.
I think this is important because some clients will insist on authenticating even if the server isn't offering it.
Currently if the require auth setting is off, smtp4dev doesn't advertise auth at all. The client will fail it insists on trying anyway.
I will add a new Allow authentication setting that defaults to on to match the old behaviour. So the server will advertise auth by default.
I will also add a Allow any credentials / Use configured users switch with it defaulting to the former. So the server will accept any username/password combination by default.
If I understand correctly and how it was working before (but not anymore) connections are refused if they have a user/password when the authentication is off (default).
Currently on 3.3.6. and the "Configuring Clients" wiki page says: "Authentication is not required, but will be accepted if your client insists on their configuration"
The text was updated successfully, but these errors were encountered: