> On Nov 17, 2016, at 1:23 PM, Niklaas Baudet von Gersdorff ([email protected]) > <[email protected]> wrote: > > Francis Lachapelle [2016-11-17 12:56 -0500] : > >>> Francis Lachapelle [2016-11-17 10:20 -0500] : >>> >>>> Sniff your IMAP traffic to see the error returned from your IMAP server. >>> >>> What's the best way to do that? I tried `tcpdump` but I cannot >>> decipher its output. Because SOGo and Dovecot communicate over >>> 993 there will be not a lot for me to see, I guess. >> >> Use imapproxy and configure SOGo to connect to imapproxy rather than >> directly to your Dovecot server. > > I see. Looks like a tool for my utility belt, anyway. :-) I'm > setting it up. > > And imapproxy's log is more informative? Or shall I configure > SOGo to connect to imapproxy on 143 while imapproxy connects to > Dovecot on 993, so that I can tcpdump between SOGo and imapproxy?
The latter. >>> anything suspicious. However, I suspect that this is not an issue >>> with Dovecot but with SOGo because other clients such as Mutt and >>> AquaMail work as expected. >> >> We still need to know the full discussion exchanged between SOGo and Dovecot >> if there is one. > > Of course. > > Niklaas -- [email protected] https://inverse.ca/sogo/lists
