wasm-demo/demo/ermis-f/imap-protocol/cur/1600095000.22600.mbox:2,S

38 lines
1.4 KiB
Plaintext

MBOX-Line: From lyndon at orthanc.ca Fri Feb 6 10:56:17 2015
To: imap-protocol@u.washington.edu
From: Lyndon Nerenberg <lyndon@orthanc.ca>
Date: Fri Jun 8 12:34:53 2018
Subject: [Imap-protocol] Use of namespace in LIST command
In-Reply-To: <54D5078A.8030207@comaxis.com>
References: <54D41703.6060403@comaxis.com>
<CAKHUCzzsi8tRLxGj8s+isS0pNpP2NyVCs1oD_z6L29pktEMHQg@mail.gmail.com>
<54D5078A.8030207@comaxis.com>
Message-ID: <alpine.BSF.2.11.1502061048080.17451@orthanc.ca>
> 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