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
Which feature or improvement would you like to request?
I would like to strictly separate domains, even for email addresses linked to the same physical person.
Concretely, I want a way to have one inbox for each email address stored in the LDAP (so no need for the alias feature, I can use mailing lists for this if I ever need it).
This can be done by making Stalwart not treating all the stored mail fields as aliases for a user, coupled with the last configuration described in the next section.
Is your feature request related to a problem?
Initially, I wanted to separate mailboxes for each domain, in order to migrate them to their own mail infrastructure if they ever wanted to do so. However, duplicating entries in the LDAP server is not a maintainable solution, so I wanted to take advantage of the ability to fill up the mail field multiple times per person.
To concretize this idea, I first tried to find a way to distinguish accounts based on email entry, but I just cannot dismiss uid in Bind Auth, and because I use FreeIPA as my LDAP backend, stalwart is just unable to decrypt its passwords.
After trying my patch, and changing the LDAP filters to search by email instead of uid...
...I found that Stalwart still fills the aliases of the user with the other entries in the mail field of the LDAP. Consequently, when I log in with the other email address of the user, I face the following error:
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
In this branch, the feature has been hardcoded in the code, so there is no way to use the old behavior without reverting commits
A toggle may be available when configuring the LDAP server, just like this:
This would require Stalwart to have access to the password hash (because you generally can't log in to it with email), so Bind Auth would be disabled And because the identifier of the account is now the email address, the Name LDAP filter and the Name attribute should be disabled, as well as the email aliases field, because managing aliases with this option would not be possible
Which feature or improvement would you like to request?
I would like to strictly separate domains, even for email addresses linked to the same physical person.
Concretely, I want a way to have one inbox for each email address stored in the LDAP (so no need for the alias feature, I can use mailing lists for this if I ever need it).
This can be done by making Stalwart not treating all the stored
mail
fields as aliases for a user, coupled with the last configuration described in the next section.Is your feature request related to a problem?
Initially, I wanted to separate mailboxes for each domain, in order to migrate them to their own mail infrastructure if they ever wanted to do so. However, duplicating entries in the LDAP server is not a maintainable solution, so I wanted to take advantage of the ability to fill up the mail field multiple times per person.
To concretize this idea, I first tried to find a way to distinguish accounts based on email entry, but I just cannot dismiss
uid
in Bind Auth, and because I use FreeIPA as my LDAP backend, stalwart is just unable to decrypt its passwords.After trying my patch, and changing the LDAP filters to search by email instead of uid...
...I found that Stalwart still fills the aliases of the user with the other entries in the
mail
field of the LDAP. Consequently, when I log in with the other email address of the user, I face the following error:Code of Conduct
The text was updated successfully, but these errors were encountered: