Closed
Bug 385157
Opened 17 years ago
Closed 9 years ago
"Can't create index file" when opening IMAP subfolder. Perhaps caused by server RFC violation
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: dcentner, Unassigned)
Details
(Whiteboard: [has protocol log])
Attachments
(1 file)
227.76 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4 Build Identifier: Version 2.0.0.4 (20070604) Using multiple IMAP-Accounts with subfolder structure (estimated 40 folders, max. 5 levels) after some time I get a warning when changing to some of the subfolders. As I use a german TB-version I don't know the exact english text, but it should be something like "Can't open index file, maybe path is too long or your rights are restricted". I have to shut down TB and restart to have access to the folders before after a while the same happens again. I dont see anything common to these folders, it appears with different accounts. I used the same structure with 1.5.x.x before upgrading to 2.0 without any probs. Reproducible: Sometimes Steps to Reproduce: 1. 2. 3. Actual Results: warning, no access to folder Expected Results: no warning, access to folder
As I had the problem again, here is the original german error message: "Die Indexdatei zu <foldername> kann nicht erstellt werden. Eventuell ist der vollständige Pfad zu lang oder es handelt sich um einen Schreib-/Lesefehler", in english that means: "The index file for <foldername> could not be created. Perhaps the complete path is too long or a Read/Write-Error has occured."
Comment 2•17 years ago
|
||
Can you attach an imap protocol log of that? <http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap>
Comment 4•17 years ago
|
||
Don't know where you sent it, but attach it to this bug instead. (Use the Add an attachment link.)
Hi Magnus, i took several tries to get some useful information into my logs but i didnt succeed. As what I can read out of it, it seems that TB looks up some status information from mailfolders in another account while I change the folder in the frontend. The ip/name-translation in the log is quite confusing, here is how the accounts are configured: account IMAP-server IMAP-User SMTP-Server SMTP-User user1@onecompany.de 192.168.110.1 user1@onecompany.de edv-proxy user1@onecompany.de info@onecompany.de 192.168.110.1 info@onecompany.de 192.168.110.1 info user1 web.de imap.web.de user1 smtp.web.de user1 As you can see, out local mail system resides on 192.168.110.1 alias edv-proxy (different naming was a must in former TB-Versions). As we have lots of users a reverse dns lookup of 192.168.110.1 could also result in things like smtp.nai.onecompany.de, mail1.nai.onecompany.de, mail2.nai.onecompany.de an so forth. web.de is a well known internet provider in germany. So I am a bit confused about log entries with ProcessCurrentURL:imap://user1%40web%2Ede@edv-proxy.onecompanynaila.de:143/select%3E/INBOX which I think is a wrong kombination of user@server. By the way, the same (wrong) kombination is in the password-list. So it is astonishing, that I receive mails from this account most of the time. (Rem: I replaced some account information with some less confidential)
I didnt have this error in versions 1.x. I hope, that you have success in locating the fault, because its very stupid to close and reopen TB every half an hour. Could it help to remove the web.de account, clear the password and recreate the account? Greetings from north bavaria
Oops, just read an error: for the info@onecompany.de account the IMAP user should be info not info@onecompany.de. IMAP user is always the same as SMTP user. Sorry for that.
Comment 8•17 years ago
|
||
Did you get the error while you made the log? What is the name of the sub folder you try to change to?
yes, i switched logging on some days ago and when i received the error i shut down TB and copied the log. I switched to "Unbekannt" and "Sent" subfolder of the web.de account receiving the error for both of them.
Comment 10•17 years ago
|
||
I got the 11M imap log sent to me, these should be the relevant lines I think: 1444[74d5498]: ReadNextLine [stream=2f5e458 nb=43 needmore=0] 1444[74d5498]: 4d3c8c0:smtp.nai.thierron.de:S-Trash:CreateNewLineFromSocket: * OK [UNSEEN 1] Message 1 is first unseen 1444[74d5498]: ReadNextLine [stream=2f5e458 nb=42 needmore=0] 1444[74d5498]: 4d3c8c0:smtp.nai.thierron.de:S-Trash:CreateNewLineFromSocket: * OK [UIDVALIDITY 1084777414] UIDs valid 1444[74d5498]: ReadNextLine [stream=2f5e458 nb=41 needmore=0] 1444[74d5498]: 4d3c8c0:smtp.nai.thierron.de:S-Trash:CreateNewLineFromSocket: * OK [UIDNEXT 28059] Predicted next UID 1444[74d5498]: ReadNextLine [stream=2f5e458 nb=92 needmore=0] 1444[74d5498]: 4d3c8c0:smtp.nai.thierron.de:S-Trash:CreateNewLineFromSocket: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft \Recent $MDNSent $Redirected $Forwarded) 1444[74d5498]: ReadNextLine [stream=2f5e458 nb=109 needmore=0] 1444[74d5498]: 4d3c8c0:smtp.nai.thierron.de:S-Trash:CreateNewLineFromSocket: * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $MDNSent $Redirected $Forwarded \*)] Limited 1444[74d5498]: ReadNextLine [stream=2f5e458 nb=38 needmore=0] 1444[74d5498]: 4d3c8c0:smtp.nai.thierron.de:S-Trash:CreateNewLineFromSocket: 402 OK [READ-WRITE] SELECT completed 1444[74d5498]: 4d3c8c0:smtp.nai.thierron.de:S-Trash:ProcessSelectedStateURL: uid validity not ok 1444[74d5498]: 4d3c8c0:smtp.nai.thierron.de:S-Trash:SendData: 403 store 1:* +FLAGS.SILENT (\Deleted)
Reporter | ||
Comment 11•17 years ago
|
||
I removed all data from the "Trash" subfolder on the IMAP server and the TB profile, i removed the web.de account from TB and the passwords of it. After a while, i got the same error messages again. I will soon deinstall TB and install 1.x again
Comment 13•16 years ago
|
||
Confirming; this requires an engineer to look at the protocol trace. Gerv
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•15 years ago
|
Whiteboard: [has protocol log]
Comment 14•15 years ago
|
||
(In reply to comment #5) > IMAP log file > 124 STATUS "Objekte - laufend/M&APw-nchen S&APw-ddeutscher Verlag" (UIDNEXT MESSAGES UNSEEN RECENT) > * STATUS "Objekte - laufend/M�nchen S�ddeutscher Verlag" (MESSAGES 1 RECENT 0 UIDNEXT 2 UNSEEN 0) > 124 OK STATUS completed Server returns folder name with garbage(not properly converted to modified UTF-7) in STATUS response. The garbage is seen for all "&APw-" part of folder name in STATUS response. What is real folder name in German? "&APw-" part corresponds to "u umlaut"? I think server side error/server side RFC violation is trigger of problem. Is your server correctly set up? If the garbage in STATUS response is the cause, I think this bug's problem won't occur, if Tb uses folder name which Tb sent in STATUS command(obtained by LIST, LSUB etc.) instead of one in STATUS response. But I believe it's impossible, because support of "* STATUS sent ..." response to "STATUS Sent ..." command(and vice versa, Server of case insensitive folder name) becomes impossible if such change will be made.
Comment 15•15 years ago
|
||
Can you open folder named "Objekte - laufend/M&APw-nchen S&APw-ddeutscher Verlag"? (Does your server return garbage to SELECT command too?) Associated local file name : ...\Objekte - laufend.sbd\M&APw-nchen S&APw-ddeutscher Verlag ...\Objekte - laufend.sbd\M&APw-nchen S&APw-ddeutscher Verlag.msf
Comment 16•14 years ago
|
||
I have the same problem with Thunderbird 3.0.1 in 2 different installations!
Comment 17•9 years ago
|
||
Dieter, ubeger, Do you still see this problem
Flags: needinfo?(uwe.beger)
Flags: needinfo?(dcentner)
Summary: "Can't create index file" when opening IMAP subfolder → "Can't create index file" when opening IMAP subfolder. Perhaps caused by server RFC violation
Whiteboard: [has protocol log] → [closeme 2015-07-15][has protocol log]
Comment 18•9 years ago
|
||
Resolved per whiteboard
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(uwe.beger)
Flags: needinfo?(dcentner)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2015-07-15][has protocol log] → [has protocol log]
You need to log in
before you can comment on or make changes to this bug.
Description
•