search for: pop3_haproxi

Even though it seems dovecot (using 2.2.33.1) supports haproxy's send-proxy-v2, it seems to lack send-proxy-v2-ssl (which also sends client's ssl state). It would be a nice feature for the backend server to identify clients so one wouldn't have to use disable_plaintext_auth on a production environment. --- haproxy.cfg frontend pop3 bind [::]:110 v4v6 bind

When is 2.3 scheduled to be released? Kevin > On Oct 26, 2017, at 7:57 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > Hi! > > There is support for haproxy SSL TLVs in 2.3. See > > https://github.com/dovecot/core/compare/f43567aa%5E...b6fbc235.patch > > Aki > >> On October 26, 2017 at 12:25 PM Rok Poto?nik <r at rula.net> wrote: >>

Hi all We experience some unexpected behavior with dovecot. It happens that emails marked as read get marked as unread (MUA is Thunderbird on port 143). Unfortunately this happens randomly, reproducing this issue is difficult. We could not find any pattern, it happens rarely. We are running dovecot version 2.2.24 on Debian Jessie (backports repository). /root at dovecot01:~# dovecot --version//

Hi! There is support for haproxy SSL TLVs in 2.3. See https://github.com/dovecot/core/compare/f43567aa%5E...b6fbc235.patch Aki > On October 26, 2017 at 12:25 PM Rok Poto?nik <r at rula.net> wrote: > > > Even though it seems dovecot (using 2.2.33.1) supports haproxy's > send-proxy-v2, it seems to lack send-proxy-v2-ssl (which also sends > client's ssl state).