On 27/05/2025 17:43 EEST DK via dovecot <dovecot@dovecot.org> wrote: On 2025-05-27 11:37, Aki Tuomi via dovecot wrote: This has now been fixed, see https://github.com/dovecot/ core/compare/ df48cb8c8ce8c53f48072fc34afd26b20ebe94cf%5E...34642ffa6b9eeea7b7a1d16e3325059937c8186b.patch Hello again. While waiting for dovecot 2.4 fixed deb package I tested "local" and "local_name" behind haproxy on dovecot 2.3.21.1+dfsg1-1~bpo12+1 Seems there is different kind of bug. Please look into it. Here are findings: Log: auth: Debug: client in: AUTH#0111#011CRAM-MD5#011service=imap#011secured=tls#011session=/ njT1h42s2YKFhNk#011lip=Z.Z.Z.Z#011rip=Y.Y.Y.Y#011lport=993#011rport=26291#011real_lip=A.A.A.A#011real_rip=B.B.B.B#011real_lport=143#011real_rport=51062#011local_name=imap.fqdn.com Result: - "local" behind reverse proxy is properly passed to dovecot and seen by dovecot and works - "local_name" behind reverse proxy is properly passed to dovecot and seen by dovecot but does not work. Tested configs and results: WORKS: - local Z.Z.Z.Z { ... } DOES NOT WORK: - local_name imap.fqdn.com { ... } - local_name "imap.fqdn.com imap2.fqdn.com imap3.fqdn.com" { ... } - local Z.Z.Z.Z { local_name imap.fqdn.com { ... } } - local Z.Z.Z.Z { local_name "imap.fqdn.com imap2.fqdn.com imap3.fqdn.com" { ... } } Greets. DK _______________________________________________ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org Unfortunately we no longer look into 2.3 bugs as it's no longer under development. Aki