Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Re-introduce 'allow any credentials' mode for SMTP #1425

Closed
ahmed2m opened this issue Apr 23, 2024 · 2 comments
Closed

[Bug] Re-introduce 'allow any credentials' mode for SMTP #1425

ahmed2m opened this issue Apr 23, 2024 · 2 comments

Comments

@ahmed2m
Copy link

ahmed2m commented Apr 23, 2024

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"

@rnwood 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
@rnwood
Copy link
Owner

rnwood commented 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.

@rnwood
Copy link
Owner

rnwood commented Apr 24, 2024

PR #1428

@rnwood rnwood closed this as completed Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants