Hi,
I'm working on migrating my v2.3 -> v2.4 configuration.
>From my 2.3 config I have
...
fts flatcurve {
commit_limit = 2000
29 max_term_size= 60
min_term_size= 3
Hi,
In a new dovecot 2.4 config I'm setting up a inet_listener for a service.
I want to use an env var in `listen` expansion, like
service imap-login {
inet_listener imaps {
listen = %{env:LAN_IPv4}, 127.0.0.1
}
}
This
https://doc.dovecot.org/2.4.1/core/settings/variables.h
Hi,
On Sat, Sep 20, 2025, at 10:49 AM, Aki Tuomi via dovecot wrote:
> The current $ENV: expansion is whitespace delimited.
>
> Aki
Is the need to use the $ENV expansion format in 'listen' intentional?
Is that planned to be changed to be consistent with the docs?
Is there a list of parameters t
Hi,
On Sat, Sep 20, 2025, at 9:13 AM, Aki Tuomi via dovecot wrote:
> Can you try
>
>listen = $ENV:LAN_IPv4 , 127.0.0.1
>
>note the space before comma
>
>Aki
With
cat dovecot.conf
importEironment {
E_LAN_IPv4 = %{env:LAN_IPv4}
E_LAN_IPv6 = %{env:LAN_IPv6}
}
cat dovecot.e
Hi,
I'm trying to clean up my migrated v2.4 config.
I'm still having a hard time with environment variable expansions :-(
They work in most places. But so far for me not in
mail_plugin_dir
ssl_client_* or ssl_server_*
listen=
For example, this config using literal file paths works great
Hi,
I’m working with Dovecot 2.4.1 and the acl plugin.
I'm trying to get per-mailbox shared namespace+acl configured and working
dynamically.
One owner (ow...@example.com) has a real Maildir folder "TEST_SHARE" at the top
level
cd /mail/path/example.com/owner/Maildir
ls -1
