From: Karl Chen <quarl@NOSPAM.quarl.org>
Subject: Maildir interoperability
Date: Thu, 18 Aug 2005 16:49:09 -0700 [thread overview]
Message-ID: <quack.20050818T1649.lthy86yst56@roar.cs.berkeley.edu> (raw)
In my opinion: nnmaildir is outrageous for using non-standard
marks that are non-interoperable with all other MUAs. The
original Maildir specification defined how marks should be used.
Nnmaildir uses a funky hard-link system (which also doesn't work
on many file systems/OSes). Synchronization scripts are a very
poor workaround.
In Googling this subject, I came across many rants,
e.g. http://bignachos.com/?page_id=5
The solution I've found to be satisfactory for now is to go
through a local IMAP server. This works, but it took a lot more
effort than the average user will devote, and is suboptimal.
Does anybody else here feel Gnus needs to support real Maildir?
Also, it would be very nice to be interoperable with IMAP, so Gnus
should also use the Maildir extension for subgroups that IMAP uses
(Maildir/.groupname). It could be a separate back-end, or Gnus
could automatically convert old-style marks.
--
Karl 2005-08-18 16:35
reply other threads:[~2005-08-18 23:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=quack.20050818T1649.lthy86yst56@roar.cs.berkeley.edu \
--to=quarl@nospam.quarl.org \
--cc=quarl+dated+1124840118.8e39fc@nospam.quarl.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).