Closed
Bug 275276
Opened 20 years ago
Closed 20 years ago
the STAT command did not succeed
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jmanatee, Assigned: mscott)
Details
I get this error "the STAT command did not succeed" this is similar to bug
227378 but it is not resolved.
Below is a log of Thunderbird version 0.9 (20041103)
0[234760]: mail.pop3_response_timeout=45
0[234760]: Entering NET_ProcessPop3 63
0[234760]: POP3: Entering state: 1
0[234760]: POP3: Entering state: 2
0[234760]: POP3: Entering state: 4
0[234760]: RECV: +OK X1 NT-POP3 Server myserver (IMail 5.06 6813-2)
0[234760]: POP3: Entering state: 29
0[234760]: SEND: AUTH
0[234760]: Entering NET_ProcessPop3 37
0[234760]: POP3: Entering state: 3
0[234760]: RECV: -ERR authentication exchange failed
0[234760]: POP3: Entering state: 30
0[234760]: POP3: Entering state: 31
0[234760]: SEND: CAPA
0[234760]: Entering NET_ProcessPop3 168
0[234760]: POP3: Entering state: 3
0[234760]: RECV: +OK Capability list follows
0[234760]: POP3: Entering state: 32
0[234760]: RECV: TOP
0[234760]: POP3: Entering state: 32
0[234760]: RECV: USER
0[234760]: POP3: Entering state: 32
0[234760]: RECV: SASL LOGIN PLAIN CRAM-MD5
0[234760]: POP3: Entering state: 32
0[234760]: RECV: RESP-CODES
0[234760]: POP3: Entering state: 32
0[234760]: RECV: LOGIN-DELAY 120
0[234760]: POP3: Entering state: 32
0[234760]: RECV: PIPELINING
0[234760]: POP3: Entering state: 32
0[234760]: RECV: EXPIRE 30 USER
0[234760]: POP3: Entering state: 32
0[234760]: RECV: UIDL
0[234760]: POP3: Entering state: 32
0[234760]: RECV: IMPLEMENTATION Ipswitch_IMail_5.0
0[234760]: POP3: Entering state: 32
0[234760]: RECV: .
0[234760]: POP3: Entering state: 33
0[234760]: POP3: Entering state: 5
0[234760]: SEND: AUTH PLAIN
0[234760]: Entering NET_ProcessPop3 18
0[234760]: POP3: Entering state: 3
0[234760]: RECV: + VXNlcm5hbWU6
0[234760]: POP3: Entering state: 34
0[234760]: POP3: Entering state: 6
0[234760]: POP3: Entering state: 36
0[234760]: POP3: Entering state: 5
0[234760]: SEND: am9u
0[234760]: Entering NET_ProcessPop3 18
0[234760]: POP3: Entering state: 3
0[234760]: RECV: + UGFzc3dvcmQ6
0[234760]: POP3: Entering state: 34
0[234760]: POP3: Entering state: 6
0[234760]: Logging suppressed for this command (it probably contained
authentication information)
0[234760]: Entering NET_ProcessPop3 31
0[234760]: POP3: Entering state: 3
0[234760]: RECV: +OK maildrop locked and ready
0[234760]: POP3: Entering state: 34
0[234760]: POP3: Entering state: 7
0[234760]: SEND: STAT
0[234760]: Entering NET_ProcessPop3 58
0[234760]: POP3: Entering state: 3
0[234760]: RECV: -ERR [IN-USE] failed to lock or parse or multiple access
0[234760]: POP3: Entering state: 8
0[234760]: POP3: Entering state: 24
0[234760]: POP3: Entering state: 25
Comment 1•20 years ago
|
||
This is the servers fault.
"0[234760]: RECV: +OK maildrop locked and ready"
-> Login OK
"0[234760]: SEND: STAT
0[234760]: RECV: -ERR [IN-USE] failed to lock or parse or multiple access"
-> Server answers with an error after the STAT comand
-> invalid (Server fault)
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
This is the servers fault.
"0[234760]: RECV: +OK maildrop locked and ready"
-> Login OK
"0[234760]: SEND: STAT
0[234760]: RECV: -ERR [IN-USE] failed to lock or parse or multiple access"
-> Server answers with an error after the STAT comand
-> invalid (Server fault)
The server works with Outlook Express, Outlook and Pegasus. How is the server
failing?
Comment 3•20 years ago
|
||
It looks to me like someone is already logged into this mailbox. Do you have
webmail access to the inbox or some other client accessing the inbox?
>It looks to me like someone is already logged into this mailbox. Do you have
>webmail access to the inbox or some other client accessing the inbox?
No. This is my server located in my office. There is no one else logging into
it for any of my user accounts. Thungerbird does this with all my accounts (10
or 12 of them). Funny thing is I can get it to work occasionally by removing
the saved password, or changing the security settings, it will work only once
then go back to the "the STAT command did not succeed"
Comment 5•20 years ago
|
||
if that's a complete pop3 protocol log, I only see one connection getting made.
Could you try turning off secure auth in the advanced pop3 server settings?
Perhaps IMAIL is not happy with AUTH_PLAIN. And here's a possibly dumb question
- do you have thunderbird set to check for new mail every one or two minutes?
>if that's a complete pop3 protocol log, I only see one connection getting made.
>Could you try turning off secure auth in the advanced pop3 server settings?
>Perhaps IMAIL is not happy with AUTH_PLAIN. And here's a possibly dumb question
>- do you have thunderbird set to check for new mail every one or two minutes?
to get this log, I started TB via a batch file with the following lines:
set NSPR_LOG_MODULES=POP3:4
set NSPR_LOG_FILE=c:\temp\moz.log
start D:\thunderbird\thunderbird.exe
I got the error (checks mail when it starts) and then exit TB and copied and
pasted the log here. I have completely removed my profile and setup one account
trying to get that to work. so currently there is only one account configured.
Both "Use Secure Connection (SSL) and Use Secure Authentication" where not
checked. "Check for new messages every" was set to 10 min.
I was just thinking if you would like I can setup an account on the server and
you can test it from your end. Make sure it isn't me doing something stupid.
I am running Win2k SP4 & Thunderbird version 0.9 (20041103)
Comment 8•20 years ago
|
||
sure, that's great. Just e-mail me the logon info.
Comment 10•20 years ago
|
||
the pop3 server claims to support all sorts of authentication mechanisms (SASL
AUTH PLAIN AUTH LOGIN...). We try to use AUTH PLAIN, I think, and the server
fails. OE is just using USER PASS which is why it works. I believe the server is
mis-configured or broken (it shouldn't be advertising authentication mechanisms
that don't work). We probably need some way of allowing the user to override
which authentication mechanism we use, instead of having us always pick the most
secure offerec by the server.
Reporter | ||
Comment 11•20 years ago
|
||
This is what the mail server is logging:
CAPA
AUTH PLAIN
ZGF2aWRi
NjU0MzIx
12:19 16:06 POP3D(00000290) lock failed =0
12:19 16:06 POP3D(00000290) Parse error, check locks, multiple accesses for
davidb mail.inet-trans.com from 131.191.11.136
UGFzc3dvcmQ6
STAT
12:19 16:06 POP3D(00000290) connection aborted
Comment 12•20 years ago
|
||
didn't we have something like user_pref("mail.server.server1.auth_plain", false);
?
But it's just a broken server which should be fixed on the serverside.
Reporter | ||
Comment 13•20 years ago
|
||
>But it's just a broken server which should be fixed on the serverside.
I just made sure the latesst mail server service pack is installed and rebooted
the server with no change.
You say it is a broken server but I would think that ipswitch would know there
is a problem with there server. Do you have any suggestions as to how to fix
the server?
Comment 14•20 years ago
|
||
(In reply to comment #10)
> the pop3 server claims to support all sorts of authentication mechanisms (SASL
> AUTH PLAIN AUTH LOGIN...). We try to use AUTH PLAIN, I think, and the server
> fails.
While we (and the server) in reality do LOGIN as we know since bug 258077. But
ok, since the server reacts the same if we send AUTH LOGIN, that shouldn't be
the reason.
> OE is just using USER PASS which is why it works.
AFAIK unless you configure it to to SPA (weird, I know).
> I believe the server is mis-configured or broken (it shouldn't be advertising
> authentication mechanisms that don't work).
True. When directly connecting and loging in via PLAIN one can see that the
server gives a double response:
+OK maildrop locked and ready
-ERR [IN-USE] failed to lock or parse or multiple access
And following commands like LIST fail with "wrong state".
> We probably need some way of allowing the user to override which
> authentication mechanism we use, instead of having us always pick the most
> secure offerec by the server.
That's bug 259679.
Comment 15•20 years ago
|
||
(In reply to comment #12)
> didn't we have something like user_pref("mail.server.server1.auth_plain", false);
> ?
It's user_pref("mail.server.server?.auth_login", false); and switches off
everything else than USER/PASS.
Comment 16•20 years ago
|
||
(In reply to comment #13)
> You say it is a broken server
Yes, and you can simply test it by login in via telnet doing AUTH PLAIN (resp.
LOGIN) by hand.
> but I would think that ipswitch would know there is a problem with there
> server. Do you have any suggestions as to how to fix the server?
Maybe they do (and the bug is fixed not in a SP but newer version), maybe they
don't. Just have a look in bug 258077. AUTH PLAIN doesn't lead to the problems
your server has but it had a general problem with it not fixed before version
8.14 (and only because I reported it).
Reporter | ||
Comment 17•20 years ago
|
||
>It's user_pref("mail.server.server?.auth_login", false); and switches off
>everything else than USER/PASS.
I have placed this in the user.js file in my profiles directory. but I still
get the same error. I am new to thunderbird and the user.js configuration
method, should I modify this line in anyway?
>Maybe they do (and the bug is fixed not in a SP but newer version), maybe they
>don't. Just have a look in bug 258077. AUTH PLAIN doesn't lead to the problems
>your server has but it had a general problem with it not fixed before version
>8.14 (and only because I reported it).
I will contact Ipswitch Monday and see if they have a hot fix or any work
around. Or at minimum a discount on upgrading to the new version.
Reporter | ||
Comment 18•20 years ago
|
||
user_pref("mail.server.server?.auth_login", false);
I got it,... I tried mail.server.server0 & 1 and then I looked in prefs.js and
found that it was server2 tried that and now it seems to be working.
Thank you for your help
Comment 19•20 years ago
|
||
(In reply to comment #18)
> I got it,... I tried mail.server.server0 & 1 and then I looked in prefs.js and
> found that it was server2 tried that and now it seems to be working.
Yes, sorry I forgot to mention to replace the question mark with the number of
the server in question.
You need to log in
before you can comment on or make changes to this bug.
Description
•