STAT command failure
Andrew Charnley
ac at igaro.com
Tue Oct 24 11:38:21 EEST 2017
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)
Steffen Kaiser <skdovecot at smail.inf.fh-brs.de> wrote:
> -----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 xxxxx
> > [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:
>
> This response usually has the offending command behind the colon - at
> least in Dovecot v2.2
>
> BTW: could you launch a secure connection, e.g. from the mail server
>
> telnet localhost 110
>
> then type in the commands yourself:
>
> user xxxxx
> pass ***
> stat
>
> - --
> Steffen Kaiser
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEVAwUBWe7PYHz1H7kL/d9rAQKI4Af7Bn/6d5UQnINGPMSdkQgNyy5h0cWHvsmQ
> U8guJnwtlEcLe0MdJD++vrM6jVeFBjgNqZrqD5Je9dei2GaNz8ti4iwr3WEi2k3I
> rkBjznX2Z2bIxpXIFjA3T4I0xSnJ7ohv3qhk1ixebpiNzi9MoA53OYre3r/ghsq8
> px6L/vMpuyQ0hiztQKyMpNUBtCE4Y/epG0R5Qy5u1VqQY4giJvSWKWdT0dE4XTkZ
> MNUt+d+/RlGTFHc6iiw+mDCUEzOnwIhuTEd25TJhh5Gm/8FS4zu1ayqHoRiRE0gB
> uTE2C842BSEuN0yUVucWc35ZWra4yW59Ugf+9OYJbU5LjBwF4Bkrqw==
> =H1JT
> -----END PGP SIGNATURE-----
More information about the dovecot
mailing list