Is the example config for LLDAP integration with Stalwart obsolete/wrong? #1163
Replies: 3 comments 2 replies
-
|
@xeoneox could you chime in? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, To the best of my knowledge it's necessary. I have not done extensive testing of other configurations. My tests were all based on making sure the configuration works. Once I had it working and passing my tests, I submitted it. I can't speak to the Stalwart documentation or what might be missing. Feel free to submit a PR if you have a fully working, more optimized, config. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. But what made you define two sets of filters? I didn’t see anything in the Stalwart documentation saying that the directory.<…>.bind.filter entries were needed or allowed. And so they might just be ignored. So did you read something that made you think they were necessary? Or did you just try “random” things until it worked? I'm not criticising, I’m just worried about adding things to my config when they don’t match Stalwart’s documentation. Of course Stalwart’s docs might also be wrong, or perhaps you read something somewhere that’s not been reflected in the current docs? I’m also trying to get some clarification from the Stalwart guys, but unfortunately they aren’t as responsive as you guys :-)
Thanks
Kevin
… On 2 May 2025, at 15:46, xeoneox ***@***.***> wrote:
Hi,
To the best of my knowledge it's necessary. I have not done extensive testing of other configurations. My tests were all based on making sure the configuration works. Once I had it working and passing my tests, I submitted it. I can't speak to the Stalwart documentation or what might be missing. Feel free to submit a PR if you have a fully working, more optimized, config.
—
Reply to this email directly, view it on GitHub <#1163 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABH6YQNXPPMO4R7QF24OYKT24OAK5AVCNFSM6AAAAAB4E3O3VGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMBRGUYTAMA>.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
-
|
It might also be worth mentioning on this page that mail aliases won't work when there's more than one mail alias as this doesn't seem to be supported by LLDAP. That confused me for a while. |
Beta Was this translation helpful? Give feedback.
-
Feel free to create a PR adding some explanations! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
In the documentation for Stalwart it says the
directory.<name>.filtersection should definenameandemailfilters. And these values are exposed in the GUI in the LDAP filters section. However, I was looking at LLDAP's example config for integration with Stalwart, https://github.com/lldap/lldap/blob/main/example_configs/stalwart.md, and here the config also definesdirectory.<name>.bind.filterentries, in addition to those indirectory.<name>.filter. So now I'm confused...If I enable bind authentication then am I supposed to configure the filters in the
directory.<name>.bind.filtersection, but this isn't documented, and the values aren't shown in the GUI? Or is this page in the LLDAP documentation wrong, or out of date, and there is a single place to define the filters irrespective of whether we are using bind authentication or not? Could whoever wrote this example config confirm if this config is still valid, and where the need for the second layer of filtering is documented if possible.Beta Was this translation helpful? Give feedback.
All reactions