[maildirpp] Improve compatibility

Message ID
DKIM signature
Download raw message
Hey Magnus,

I hope you are doing well! I wanted to share with you an issue I am
facing with the maildirpp crate. Here the thing:

- The Maildir standard does not provide anything about folders
  hierarchy. One Maildir targets one mailbox. The way to structure
  folders is up to the client. Let's say someone uses the mail
  synchronizer [mbsync]. The Maildir folder hierarchy is specific to
  mbsync: name of the inbox folder, nested vs flatten folders, folder
  name encoding/decoding of special characters etc. If someone wants to
  migrate from mbsync to [OfflineIMAP], it will probably not work.

- The Maildir++ standard restricts a bit more the hierarchy, as every
  sub folders need to start by a period. But same issues regarding
  nested vs flatten (.Archives.2024.January vs .Archives/.2024/.January)
  and encoding.

To improve compatibility between Maildir instances, a Maildir builder
with few options could be enough: Folder aliases, nested vs flatten,
encoding and decoding. But I am not sure if such a builder belongs to
the maildirpp crate. Maybe a more generic crate like `maildirs` could be
a better candidate (a crate to manage a group of Maildir-based
folders). Maildir++ could become an option.

What do you think?

Regarding m2dir, I wanted to give it a shot soon but it will be
delayed. The Maildir issue is more important for `email-lib` at the

[mbsync]: https://isync.sourceforge.io/mbsync.html
[OfflineIMAP]: https://www.offlineimap.org/

Clément DOUIN
Reply to thread Export thread (mbox)