Closed Bug 1046287 Opened 10 years ago Closed 10 years ago

imap server directory setting not working anymore

Categories

(MailNews Core :: Networking: IMAP, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 859269

People

(Reporter: joey, Unassigned)

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release) Build ID: 20140716183446 Steps to reproduce: using uw imap server which requires an imap prefix of mail/ to be set set imap server directory to: mail/ try to open inbox tested on both linux and windows versions of thunderbird Actual results: initial open takes minutes to display because imap server is walking my entire home directory looking for mail files. from looking at server and thunderbird logging, i can see that the initial imap list command is not passing the imap prefix. a temporary workaround was to set all namespaces to mail/ i see that the lsub command is passing the imap prefix, so it looks to be just the list command that is broken Expected results: initial imap list command should be limited to the specified imap server directory.
I have the same problem, also while connecting to an uw-imapd. It seems that the imap server directory setting is ignored and never sent to the imap server. When using a previous version of Thunderbird (24.5.0), the network communication is: < * OK [CAPABILITY IMAP4REV1 I18NLEVEL=1 LITERAL+ SASL-IR LOGIN-REFERRALS AUTH=PLAIN AUTH=LOGIN] server.domain IMAP4rev1 2007b.404 at Thu, 31 Jul 2014 13:19:53 +0200 (CEST)\r > 1 authenticate plain\r < + \r > XXXXXXXXXXXX=\r < 1 OK [CAPABILITY IMAP4REV1 I18NLEVEL=1 LITERAL+ IDLE UIDPLUS NAMESPACE CHILDREN MAILBOX-REFERRALS BINARY UNSELECT ESEARCH WITHIN SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] User XXX authenticated\r > 2 namespace\r < * NAMESPACE (("" "/")("#mhinbox" NIL)("#mh/" "/")) (("~" "/")) (("#shared/" "/")("#ftp/" "/")("#news." ".")("#public/" "/"))\r < 2 OK NAMESPACE completed\r > 3 lsub "" "mail/*"\r When using Thunderbird 31.0, the network communication (with the same configuration) is: < * OK [CAPABILITY IMAP4REV1 I18NLEVEL=1 LITERAL+ SASL-IR LOGIN-REFERRALS AUTH=PLAIN AUTH=LOGIN] servername.domain IMAP4rev1 2007b.404 at W ed, 30 Jul 2014 16:09:21 +0200 (CEST)\r > 1 authenticate plain\r < + \r > XXXXXXXXXXXX\r < 1 OK [CAPABILITY IMAP4REV1 I18NLEVEL=1 LITERAL+ IDLE UIDPLUS NAMESPACE CHILDREN MAILBOX-REFERRALS BINARY UNSELECT ESEARCH WITHIN SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] User XXX authenticated\r > 2 list "" "*"\r So, apparently, Thunderbird now uses "list" instead of "lsub", but does not provide the server directory any more. Perhaps the omission has happened while changing "lsub" to "list"? Unfortunately, I have no communication log for versions bethween 24.5.0 and 31.0.
thunderbird sends the list command first to discover all folders, then it sends the lsub afterwards (which does have the prefix set). did you see my workaround to set all namespaces to "mail/"? that at least gets around the issue for the moment.
Ah, so the LIST command is new, not a replacement. My problem is that in my homedir, I have a cyclic symlink ( ~/foo/bar -> ~/foo ). UW Imapd does not realize this, so it tries to make a recursive list of infinite depth (foo, foo/bar, foo/bar/bar, foo/bar/bar/bar etc.). This never terminates, so the LIST goes on forever. I never get to the LSUB. This means that I cannot read my mail at all with the current Thunderbird, not even with your workaround.
Duplicate of bug 799821 / bug 1046392
Component: Untriaged → Networking: IMAP
Keywords: regression
Product: Thunderbird → MailNews Core
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Hi Joe. And Jørgen. Do you find this problem to be gone in 31.2.x? or from https://www.mozilla.org/en-US/thunderbird/channel/
Flags: needinfo?(joey)
Flags: needinfo?(jel)
Yes, it is gone in 31.2.0. Thanks :-)
Flags: needinfo?(jel)
yes, has been fixed for a few releases now.
Flags: needinfo?(joey)
You need to log in before you can comment on or make changes to this bug.