Re: STAT command failure

2017-10-25 Thread Joseph Tam
Andrew Charnley writes: It's also telling that it works for some accounts, and not for others. Try rebuilding the user's index cache by removing it (save a copy!) and see if that makes it work. If it does, you can send the buggy caches to the developer and see if they can

Re: STAT command failure

2017-10-24 Thread Andrew Charnley
On Tue, 24 Oct 2017 14:31:11 -0700 (PDT) Joseph Tam wrote: > Andrew Charnley writes: > > >>> Regarding STAT which appears to have an issue with Dovecot:- > >>> > >>> [23:50:46] POP< +OK Dovecot ready. > >>> [23:50:46] POP> USER x > >>> [23:50:46] POP<

Re: STAT command failure

2017-10-24 Thread Joseph Tam
Andrew Charnley writes: Regarding STAT which appears to have an issue with Dovecot:- [23:50:46] POP< +OK Dovecot ready. [23:50:46] POP> USER x [23:50:46] POP< +OK [23:50:46] POP> PASS [23:50:46] POP< +OK Logged in. [23:50:46] POP> STAT [23:50:46] POP< -ERR Unknown

Re: STAT command failure

2017-10-24 Thread Andrew Charnley
Hi, I can confirm this works. So two issues here; 1. Dovecot logging is useless - there is no logging or stderr output 2. Likely an issue with CLAWS email. I'm conversing with the CLAWS support group to see what they think. Regards, Andrew On Tue, 24 Oct 2017 07:28:00 +0200 (CEST)

Re: STAT command failure

2017-10-23 Thread Steffen Kaiser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 23 Oct 2017, Andrew Charnley wrote: Regarding STAT which appears to have an issue with Dovecot:- [23:50:46] POP< +OK Dovecot ready. [23:50:46] POP> USER x [23:50:46] POP< +OK [23:50:46] POP> PASS [23:50:46] POP< +OK Logged in.

STAT command failure

2017-10-23 Thread Andrew Charnley
Hi, Regarding STAT which appears to have an issue with Dovecot:- [23:50:46] POP< +OK Dovecot ready. [23:50:46] POP> USER x [23:50:46] POP< +OK [23:50:46] POP> PASS [23:50:46] POP< +OK Logged in. [23:50:46] POP> STAT [23:50:46] POP< -ERR Unknown command: I have enabled the logging