55 lines
2.2 KiB
Plaintext
55 lines
2.2 KiB
Plaintext
MBOX-Line: From jjmckay at comaxis.com Fri Feb 6 15:43:24 2015
|
|
To: imap-protocol@u.washington.edu
|
|
From: Jeff McKay <jjmckay@comaxis.com>
|
|
Date: Fri Jun 8 12:34:53 2018
|
|
Subject: [Imap-protocol] Use of namespace in LIST command
|
|
In-Reply-To: <alpine.BSF.2.11.1502061048080.17451@orthanc.ca>
|
|
References: <54D41703.6060403@comaxis.com>
|
|
<CAKHUCzzsi8tRLxGj8s+isS0pNpP2NyVCs1oD_z6L29pktEMHQg@mail.gmail.com>
|
|
<54D5078A.8030207@comaxis.com>
|
|
<alpine.BSF.2.11.1502061048080.17451@orthanc.ca>
|
|
Message-ID: <54D5519C.2020600@comaxis.com>
|
|
|
|
This customer was telling me that Thunderbird sees the folders just
|
|
fine, so I did a trace of TB's traffic and found it
|
|
is doing both LIST and LSUB. To be honest I had not heard of the LSUB
|
|
command before. It seems to me that retrieving
|
|
subscribed folders is going to give a subset of the entire folder list,
|
|
and I want the entire list. But in this case, LIST by
|
|
itself leaves off all the folders we were missing. In tests with some
|
|
other imap servers my theory is correct - LIST gives
|
|
me what I want, except for this case. So I can work around it for this
|
|
guy but I'm wondering if doing both commands
|
|
(then eliminating duplicates) is the best practice.
|
|
|
|
On 2/6/2015 10:56 AM, Lyndon Nerenberg wrote:
|
|
>> For example here are a couple attempts. What does the message "mh
|
|
>> format names disabled" mean?
|
|
>
|
|
> The #mh namespaces refer to the MH mua, which uses a local message
|
|
> store in the user's home directory. If the user uses MH, the #mh
|
|
> namespace can be used to access those folders via UW IMAPD.
|
|
>
|
|
> The message about their not being a .mh_profile indicates that the
|
|
> user is not using MH. Therefore the #mh namespaces don't apply to
|
|
> them, and nothing will show up under them.
|
|
>
|
|
> Or perhaps they have carried across an old set of MH folders, but
|
|
> aren't actively using MH any more. In that case, they might now have
|
|
> an .mh_profile file. If this *is* the case, have them
|
|
>
|
|
> echo Path: Mail > ${HOME}/.mh_profile
|
|
>
|
|
> and it should start working. (Replace Mail with the path to their MH
|
|
> folder store if they don't use the default ${HOME}/Mail.)
|
|
>
|
|
> http://www.nongnu.org/nmh/ is a good starting point for information on
|
|
> the current release of the MH mailer.
|
|
>
|
|
> --lyndon
|
|
>
|
|
>
|
|
>
|
|
|
|
|