Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Maildir++ subfolders
Date: Mon, 14 Sep 2020 14:27:53 -0700	[thread overview]
Message-ID: <878sdcyrom.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87y2lczyut.fsf@fedora.osfans.org>

Kevin Shell <kshell@gmx.com> writes:

> Kevin Shell <kshell@gmx.com> writes:
>
>> Hello list.
>>
>> How to get Gnus display Maildir++ subfolders?
>> They all start with dot(.) character, but Gnus ignores all
>> folders start with dot.
>
> I use the Gnus nnmaildir backend.

Looks like the code explicitly ignores folders that start with a dot,
and forbids you from creating groups whose name starts with a dot.

I'm not a maildir expert, but it looks like the standard maildir format
doesn't provide for multiple folders, and the maildir++ format does
provide for multiple folders, but *requires* them to start with a dot.

Dovecot (the only program I know well that deal with maildir) uses
maildir++ by default, but allows you to turn on a setting that uses
non-dot-prefixed, potentially nested folder names.

But beyond that it looks like the "normal" thing to do is dot-prefixed
folder names (and subfolders emulated with multiple dots).

Does anyone know why nnmaildir does it the way it does? I suppose it
might make sense to give nnmaildir servers the option to choose between
"traditional layout" and "filesystem layout".

Eric



  reply	other threads:[~2020-09-14 21:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14  5:46 Kevin Shell
2020-09-14  5:55 ` Kevin Shell
2020-09-14 21:27   ` Eric Abrahamsen [this message]
2020-09-15  0:10     ` Kevin Shell
2020-09-15  4:13       ` Eric Abrahamsen
2020-09-15  6:04         ` Kevin Shell
2020-09-15 11:16           ` Eric S Fraga
2020-09-15 15:59             ` Eric Abrahamsen
2020-09-16 14:45               ` Eric S Fraga

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878sdcyrom.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).