User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 I just upgraded from 1.5 to 1.6. Now the problem appears that when I'm clicking on a message of one of my Cyrus IMAPD accounts, the mouse pointer changes to the hour glass, but nothing happens (only sometimes "Loading Message..." is shown). Messages that have been downloaded before this upgrade are shown as usual. The Read/Unread status of the mail remains unchanged. Changing this status is possibly by clicking on the green dot. My other IMAP accounts work well. Reproducible: Always Steps to Reproduce: 1. Try to download a new message 2. 3. Actual Results: Mouse pointer becomes a hour glass, sometimes "Loading Message..." is shown. Read/Unread status remains unchanged. Expected Results: The message should be downloaded and displayed. I had the same problem with Mozilla 1.6 beta and decided to downgrade again. Mozilla 1.5 works well. I didn't test 1.6 alpha.
Reporter, please attach an IMAP protocol log; see http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap
Also, Fabian, have you set your online directory in your mozilla advanced imap server settings to anything, like INBOX., or something like that? Or have you changed your personal namespace? e-mailing me your prefs.js might be helpful. thx.
Created attachment 139432 [details] The IMAP logfile This is the IMAP logfile of my last session. I opened MailNews and clicked on the inbox. dingmail.dasding.de is the server with this problem.
Thanks for the fast answers. I attached the prefs.js and the IMAP logfile. I discovered that not only downloading the message body fails. It is also not possible to download new messages. It looks like the whole Inbox hangs and I can only see the status before the upgrade. My IMAP Server Directory is not set. The personal namespace is "INBOX."
Unfortunately, your log has a bunch of nulls in it where the interesting data would be. I don't know what causes that but other people have had that problem. Can you tell if you're even logging onto the server successfully? Do you have your password stored in the password manager? Without being able to see the log, I'm just guessing here, but it's possible that your server is one of those servers that advertise cram-md5 support, but drop the connection when it's used - I fixed our handling of that last night...Could you try today's Mozilla 1.7 nightly build and see if it works for you? You might also try generating a log again and see if you get more non-null data in it...
I tried the nightly build and it works. Obviously it's the cram-md5 problem (I posted bug 208026 in last June and thought it was already fixed). Do you need some more information or is the problem solved for you now? I could check the server logs if you want to.
yes, there was a regression in the cram-md5 code - someone made a patch which turned it back on by default (which I reviewed, my bad). If the nightly build works, then I'll just mark this fixed. If there's a 1.6.1 or something, I'll try to get that fix in.
Thank you very much!