<<< Date Index >>>     <<< Thread Index >>>

Re: [Mutt] #3113: reinstate $imap_home_namespace



#3113: reinstate $imap_home_namespace
---------------------+------------------------------------------------------
  Reporter:  cout    |       Owner:  mutt-dev
      Type:  defect  |      Status:  new     
  Priority:  major   |   Milestone:          
 Component:  mutt    |     Version:  1.5.18  
Resolution:          |    Keywords:          
---------------------+------------------------------------------------------

Comment(by cout):

 Tcpdump reveals that mutt is executing a STATUS command for each mailbox.
 I suppose that's actually the right behavior, and it's a problem with
 imapd that the STATUS command is so slow for large mailboxes.  Ideally
 mutt should not block while waiting for the result of the STATUS command,
 but that's a separate issue.

 As for why setting $imap_home_namespace doesn't cause the mailboxes to be
 checked, it is not clear to me.

 Another difference between setting $imap_home_namespace and setting
 $folder is that INBOX shows up in the mailbox list with
 $imap_home_namespace, but not with $folder.  I have mutt configured as
 follows:

 set imap_user=pbrannan
 set spoolfile=imap://server/INBOX
 set folder=imap://server
 # set folder=imap://server/~/mail
 set imap_home_namespace=~/mail/
 set mail_check=15
 set timeout=120
 set imap_servernoise=no
 set check_new=yes

 The difference appears to be that $imap_home_namespace causes mutt to use
 the NAMESPACE command, which returns the inbox as a null string, whereas
 only using $folder causes mutt to skip the NAMESPACE command and only list
 the folders with the LIST command, which does not return the inbox.

 Using $folder only, mutt also prepends "../" to the folder list (I can see
 from the server output that this is being prepended by mutt and not by the
 server), which is not accessible.

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3113#comment:2>
Mutt <http://www.mutt.org/>
The Mutt mail user agent