834705 - hung "(not responding)" during "Looking for folders" (login to specific IMAP server is not normally executed)

Status: RESOLVED DUPLICATE of bug 859269

(MailNews Core :: Networking: IMAP, defect)

Description

[Wayne Mery (:wsmwk)]

Attachment: windbg stacktrace

entering an account on T43 laptop. account not accessed in a long time, so checked sync in account settings first - looks good, sync not set.
click get mail, enter password, hung

reproducible

build 20130117070400

Comment 1

[Wayne Mery (:wsmwk)]

also have minidump

Comment 2

[Wayne Mery (:wsmwk)]

need protocol log?

Comment 3

[DWidder]

It would seem I was premature in my pronouncement that Thunderbird had self corrected. After downloading my mail one time it returned to remaining stuck in the mode of "Looking for folders". Any further advice or suggestions?

Above you note "Platform: x86 Windows XP".  The original email requesting help was sent from a laptop running XP.  The system I am having problems with is a desktop running Windows7 with service Pack 1 installed and a 64 bit operating system if that is of any help.

Comment 4

[Wayne Mery (:wsmwk)]

DWidder, are you still seeing this?
And have you tried an earlier version to see if problem goes away?

xref bug 859269

Comment 5

[Wayne Mery (:wsmwk)]

DWidder, if you have further comments, please add them here. In particular, 
- it may be helpful if you are able to determine whether version 16 [1] has the problem
- is problem only with the RCN account?

Comment 6

[WADA:World Anti-bad-Duping Agency]

(In reply to Wayne Mery (:wsmwk) from comment #2)
> need protocol log?

Yes, it's needed in almost all IMAP related funny phenomenon while server communication.
What is reason why you never provide IMAP log for problem analysis by developrs even after you are aware of similarity of this bug to bug 859269?

Comment 7

[Wayne Mery (:wsmwk)]

(In reply to WADA from comment #6)
> (In reply to Wayne Mery (:wsmwk) from comment #2)
> > need protocol log?
> 
> Yes, it's needed in almost all IMAP related funny phenomenon while server
> communication.
> What is reason why you never provide IMAP log for problem analysis by
> developrs even after you are aware of similarity of this bug to bug 859269?

The reasons are several, which we need not go into. Not to worry, I've just emailed you log. I used TB 21.0b1. In this imap log, tb hung after I selected the *second* imap account.  Status bar has "looking for folders".

Comment 8

[WADA:World Anti-bad-Duping Agency]

IMAP log sent to me from Wayne Mery.
> in this imap log, tb hung after I selected the *second* imap account

It looks three IMAP accounts are accessed.
> 9ddf000:mail.lehigh.edu:NA:CreateNewLineFromSocket:
>         * OK [CAPABILITY IMAP4REV1 I18NLEVEL=1 (snip)
> bab5800:mail.lehigh.edu:NA:CreateNewLineFromSocket:
>         * OK [CAPABILITY IMAP4REV1  I18NLEVEL=1 (snip)
> bab3800:imap.googlemail.com:NA:CreateNewLineFromSocket:
>         * CAPABILITY IMAP4rev1 UNSELECT ID

Problem with which?
Which is the *second* imap account?
Problem with both IMAP accounts on mail.lehigh.edu?
If Gmail IMAP is first account, no problem in third account?
If first=first mail.lehigh.edu account, second=second mail.lehigh.edu account, no problem in first mail.lehigh.edu account? 
What is difference from login process in IMAP log obtained by Tb 17?
No problem in account definition? For example,
  No SSL is accepted if access in campus.
  SSL is required if access from outside of campus,
  and if no SSL, server simply ignores request from client.

Following is logs for 9ddf000:mail.lehigh.edu.
It's same for bab5800:mail.lehigh.edu, and it occurs at same time.

(1) Open connection. Invoked for select>/INBOX 
> 0[2310140]: 9ddf000:mail.lehigh.edu:NA:SetupWithUrl: clearing IMAP_CONNECTION_IS_OPEN
> 4064[a456290]: ImapThreadMainLoop entering [this=9ddf000]
> 4064[a456290]: 9ddf000:mail.lehigh.edu:NA:ProcessCurrentURL: entering
> 4064[a456290]: 9ddf000:mail.lehigh.edu:NA:ProcessCurrentURL:imap://<UserID>@mail.lehigh.edu:993/select%3E/INBOX:  = currentUrl

(2) Greeting comes.
    CAPABILITY responce code in OK greeting.
    So, CAPABILITY command is not issued by Tb.
> 4064[a456290]: ReadNextLine [stream=a519a68 nb=162 needmore=0]
> 4064[a456290]: 9ddf000:mail.lehigh.edu:NA:CreateNewLineFromSocket: * OK [CAPABILITY IMAP4REV1 I18NLEVEL=1 LITERAL+ SASL-IR LOGIN-REFERRALS AUTH=PLAIN AUTH=LOGIN] rain Panda IMAP 2010.417 at Wed, 10 Apr 2013 22:14:45 -0400 (EDT)

(3) select auth method => try to login
> 4064[a456290]: try to log in
> 4064[a456290]: IMAP auth: server caps 0x5027, pref 0x0, failed 0x1006, avail caps 0x0
> 4064[a456290]: (GSSAPI = 0x1000000, CRAM = 0x0, NTLM = 0x20000, MSN =  0x0, PLAIN = 0x100000, LOGIN = 0x0, old-style IMAP login = 0x200000)auth external IMAP login = 0x0
> 4064[a456290]: trying auth method 0x1000

(4) nothing occurs, and finally, connection is closed
> 4064[a456290]: 9ddf000:mail.lehigh.edu:NA:ProcessCurrentURL: aborting queued urls
> 4064[a456290]: 9ddf000:mail.lehigh.edu:NA:TellThreadToDie: close socket connection
> 4064[a456290]: ImapThreadMainLoop leaving [this=9ddf000]

FYI.
Log for login to Gmail IMAP is; 
>  try to log in
>  trying auth method 0x4
                          <= no log after here, if mail.lehigh.edu
>  got new password
>  IMAP: trying auth method 0x4
>  old-style auth
>  Logging suppressed for this command (it probably contained authentication information)

By the way, it doesn't seem problem with Gmail IMAP. Have you viewed file content(simple text file) by yourself? Why should I remove many many log lines by Gmail IMAP in log(==noise) to extract above log lines for relevant server only? Why you don't exclude logs for Gmail IMAP when getting log? Why no timestamp?
Stop any automatic access to Gmail IMAP when getting log, if Gmail IMAP is irrelevant to your problem, please. I believe you are not general Tb user who frequently adds complaint only comments to bug at B.M.O :-)

Comment 9

[Wayne Mery (:wsmwk)]

it hung on accessing the wsm0 account.
I'll try to get a better log.
do you need more than imap?

Comment 10

[Joe H]

I upgraded to Thunderbird 21.0 and now get "Looking for folders" when I startup. I am unable to access new messages.

If I uncheck "Show only subscribed folders" and restart I no longer get the messages. The problem is that I have accumulated a huge number of folders over that last few decades and this makes saving email to the appropriate folder unwieldly.

The server is uw-imap which is running more or less unchanged soince 2009.

If I can supply uselful logs, etc., please let me know and I will do my best.

Comment 11

[David Lechner (:dlech)]

@Joe H, The fact that not using subscribed folders changes the behavior in your case makes me think you may be affected by bug 859269. This bug has similar symptoms, but a different problem. 

You can run an imap log and see if it looks like this bug or the other.

Logging instructions if you need them: https://wiki.mozilla.org/MailNews:Logging

If it turns out to be bug 859269, then just post there rather than on this bug.

Comment 12

[Joe H]

Thanks David, I suspect bug 859269 is more relevant. Your logging link was very useful.

Comment 13

[Wayne Mery (:wsmwk)]

I guessing my issue was bug 859269. I don't have ability to quickly reproduce, that system is gone