On 2025-05-22 16:55, Aki Tuomi via dovecot wr,ote:
I see you a local 10.20.20.20 statement there, which changes how the inbox prefix behaves, and I'm guessing (?) you are testing from 10.20.20.20 as it's local, not remote.
Which would explain why.
Also to add a bit that the "local_ip" (not real_local_ip) gets updated with haproxy proxy protocol (when enabled), so it will remote haproxy's local IP.
Aki, I have a little feature request to consider.
According to this: https://github.com/dovecot/core/blob/release-2.4.1/NEWS
- config: Support DNS wildcards in local_name, e.g. local_name *.example.com { .. } matches anything.example.com, but not multiple.anything.example.com.
- config: Support multiple names in local_name, e.g. local_name "1.example.com 2.example.com" { .. }
"local_name" filter now supports multiple values, which is handy.
It would be also handy if "local" filter also support multiple values. Since it also matches on proxy IP in environment with front proxies, in environments where you have few proxies ahead of your dovecot server you have to add every IP or use subnet. In case your proxies are in different subnet then you have to make a copy of whole config and simply double/multiply whole config by number of proxies - which is not nice. By simply allowing user to add multiple IPs for "local" filter you could fix that pain easily. If it is worth in your opinion could you please also report this feature request? Many thanks in advance. Greets.
DK