> On 29/09/2025 18:58 EEST Andy Baugh via dovecot <[email protected]> wrote: > > > I mean... yes and no? Sure "all settings are global" (in scope) per the > syntax doc, but some just can't be applied/make no sense outside of named > filters/namespaces (what I'd consider a "scope" as an administrator). >
This is true. But they can be set outside namespace context, and they'll still get applied there. > Far as I've dealt with it, those settings only ever apply within the scope of > a namespace with mailboxes anyways, so it's certainly a better place for it. > I personally put them there because if I didn't, things exploded when doing > doveconf -n as config test, though my setup is quite a bit more complicated, > so other factors may be at play (if anything, I'd suspect the quota plugins, > as those seem very opinionated about where their params are set). > This is of course personal preference, but not a strict requirement and does not need to be done for things to work. > I did think for a second that it might be something that the passdb was > returning, as that's the other context I've encountered this error in, but > the query seems to not include that key... > > Maybe the authdb also needs to get updated to return "maildir" AS > `mail_location` too... hard to say without actually understanding what data > is in that field however. More than likely if this `maildir` is in the "old" > format from authdb, it'll need to be split out into 4 fields on the colon > delimiter it used to have. In 2.4 there is no "mail_location" setting in passdb or outside passdb, you can return mail_path instead. > -- > Thomas "Andy" Baugh | Software Development Engineer IV > [email protected] > http://www.webpros.com/ > Aki _______________________________________________ dovecot mailing list -- [email protected] To unsubscribe send an email to [email protected]
