[GH-ISSUE #520] smtp without authentication configured stills tries to authenticate #190

New issue

Closed

opened 2026-02-27 08:15:47 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 08:15:47 +03:00

Owner

Originally created by @leanderjanssen on GitHub (Apr 3, 2023).
Original GitHub issue: https://github.com/lldap/lldap/issues/520

I've tried to configure lldap to use smtp without authentication, by removing both the user and password parameters from the [smtp_options] section.

This are the smtp options I've configured:

[smtp_options]
enable_password_reset=true
server="smtp.<snip>.net"
port=587
smtp_encryption="STARTTLS"
from="LLDAP Admin <lldap@<snip>.net>"
reply_to="Do not reply <lldap@<snip>.net>"

But when trying the initiate a password reset lldap still tries to start an authenticated smtp session.

lldap    | 2023-04-03T18:21:29.732179549+00:00  DEBUG    │  ┝━ 🐛 [debug]: Sending email to 'leander@<snip>.net' as 'LLDAP Admin <lldap@v<snip>.net>' via 'admin'@'smtp.<snip>.net':'587'

This debug output also shows its trying to use the admin user. This doesn't seem right when trying to do an unauthenticated smtp session.

lldap    | 2023-04-03T18:21:32.062651465+00:00  WARN     │  ┝━ 🚧 [warn]: Error sending email: lettre::transport::smtp::Error {
lldap    |     kind: Permanent(
lldap    |         Code {
lldap    |             severity: PermanentNegativeCompletion,
lldap    |             category: Unspecified3,
lldap    |             detail: Five,
lldap    |         },
lldap    |     ),
lldap    |     source: "5.7.8 Error: authentication failed: ",
lldap    | }

Here is also some logging from the smtp server:

Apr 03 18:21:29 smtp postfix/submission/smtpd[4381]: Anonymous TLS connection established from unknown[2001:<snip>:a32]: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
Apr 03 18:21:32 smtp postfix/submission/smtpd[4381]: warning: unknown[2001:<snip>:a32]: SASL PLAIN authentication failed:
Apr 03 18:21:32 smtp postfix/submission/smtpd[4381]: lost connection after AUTH from unknown[2001:<snip>:a32]
Apr 03 18:21:32 smtp postfix/submission/smtpd[4381]: disconnect from unknown[2001:<snip>:a32] ehlo=2 starttls=1 auth=0/1 commands=3/4

Used lldap version: 0.4.2 (docker image nitnelave/lldap:latest-alpine)

Originally created by @leanderjanssen on GitHub (Apr 3, 2023). Original GitHub issue: https://github.com/lldap/lldap/issues/520 I've tried to configure lldap to use smtp without authentication, by removing both the `user` and `password` parameters from the `[smtp_options]` section. This are the smtp options I've configured: ``` [smtp_options] enable_password_reset=true server="smtp.<snip>.net" port=587 smtp_encryption="STARTTLS" from="LLDAP Admin <lldap@<snip>.net>" reply_to="Do not reply <lldap@<snip>.net>" ``` But when trying the initiate a password reset lldap still tries to start an authenticated smtp session. ``` lldap | 2023-04-03T18:21:29.732179549+00:00 DEBUG │ ┝━ 🐛 [debug]: Sending email to 'leander@<snip>.net' as 'LLDAP Admin <lldap@v<snip>.net>' via 'admin'@'smtp.<snip>.net':'587' ``` This debug output also shows its trying to use the `admin` user. This doesn't seem right when trying to do an unauthenticated smtp session. ``` lldap | 2023-04-03T18:21:32.062651465+00:00 WARN │ ┝━ 🚧 [warn]: Error sending email: lettre::transport::smtp::Error { lldap | kind: Permanent( lldap | Code { lldap | severity: PermanentNegativeCompletion, lldap | category: Unspecified3, lldap | detail: Five, lldap | }, lldap | ), lldap | source: "5.7.8 Error: authentication failed: ", lldap | } ``` Here is also some logging from the smtp server: ``` Apr 03 18:21:29 smtp postfix/submission/smtpd[4381]: Anonymous TLS connection established from unknown[2001:<snip>:a32]: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 Apr 03 18:21:32 smtp postfix/submission/smtpd[4381]: warning: unknown[2001:<snip>:a32]: SASL PLAIN authentication failed: Apr 03 18:21:32 smtp postfix/submission/smtpd[4381]: lost connection after AUTH from unknown[2001:<snip>:a32] Apr 03 18:21:32 smtp postfix/submission/smtpd[4381]: disconnect from unknown[2001:<snip>:a32] ehlo=2 starttls=1 auth=0/1 commands=3/4 ``` Used lldap version: 0.4.2 (docker image nitnelave/lldap:latest-alpine)

kerem closed this issue

2026-02-27 08:15:47 +03:00

kerem commented

2026-02-27 08:15:48 +03:00

Author

Owner

@nitnelave commented on GitHub (Apr 3, 2023):

From the error message, the email sender sees the smtp.user as "admin", so it tries to authenticate.

You can double check the configuration by starting LLDAP in verbose mode, it will start by dumping the config to the logs.

There are 4 places where the flag can come from: the config file, the command line, the environment variables, and the defaults.

In this case, the value comes from the defaults (and you could argue that it's a bug).

I'll make a note to change that, but in the meantime you can solve your problem by adding a user: "" to your SMTP configuration.

@nitnelave commented on GitHub (Apr 3, 2023): From the error message, the email sender sees the smtp.user as "admin", so it tries to authenticate. You can double check the configuration by starting LLDAP in verbose mode, it will start by dumping the config to the logs. There are 4 places where the flag can come from: the config file, the command line, the environment variables, and the defaults. In this case, the value comes from the defaults (and you could argue that it's a bug). I'll make a note to change that, but in the meantime you can solve your problem by adding a `user: ""` to your SMTP configuration.

kerem commented

2026-02-27 08:15:48 +03:00

Author

Owner

@leanderjanssen commented on GitHub (Apr 3, 2023):

I'll make a note to change that, but in the meantime you can solve your problem by adding a user: "" to your SMTP configuration.

Great, that indeed fixes the issue. Thanks.

@leanderjanssen commented on GitHub (Apr 3, 2023): > I'll make a note to change that, but in the meantime you can solve your problem by adding a `user: ""` to your SMTP configuration. Great, that indeed fixes the issue. Thanks.

kerem referenced this issue

2026-02-27 08:18:09 +03:00

[PR #190] [MERGED] Add example for Gitea #600