mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 16:25:55 +03:00
[GH-ISSUE #1214] [BUG] Docker Mailserver Integration #432
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#432
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @MahdiBaghbani on GitHub (Jul 14, 2025).
Original GitHub issue: https://github.com/lldap/lldap/issues/1214
Describe the bug
I'm using docker mailserver and the login into Roundcube is ok but when sending email, I receive error
To Reproduce
Setup RoundCube and docker mailserver and lldap
Login via roundcube (imap is done via dovcot ldap) -> OK
send email -> SASL auth fails
Expected behavior
Email get sent correctly.
Logs
Additional context
configs:
@MahdiBaghbani commented on GitHub (Jul 14, 2025):
I know this might not be really related to LLDAP, but I have recently been testing to migrate from OpenLDAP to LLDAP and encountered this problem, Also this issue is very similar to #642, but different in the error part
@nitnelave commented on GitHub (Jul 14, 2025):
The open LDAP migration tool cannot port over the passwords, so they all have to be reset. The error you're getting is an invalid password for the admin. Have you checked out the section in the FAQ for "I can't log in?"
@MahdiBaghbani commented on GitHub (Jul 14, 2025):
The admin password is hand copied, also i started with a fresh password for admin in LLDAP.
Didn't import anything, everything is new
The login into roundcube also shows that the admin binding succeeds when logging in
so i suspect there is something wrong with the SASL auth
@MahdiBaghbani commented on GitHub (Jul 14, 2025):
There is definitely a problem with saslauthd and lldap, although I don't know what.
Changing the config to force saslauth to use dovecot works
instead of sasl, dovecot does the binding with lldap and all is good.
@nitnelave commented on GitHub (Jul 14, 2025):
Lldap itself doesn't support sasl. Maybe that's the answer?
@MahdiBaghbani commented on GitHub (Jul 14, 2025):
Oh well, I didn't catch that, my bad.
Anyway, thanks for the software its quite helpful.