From: Brian Landers <brian@bluecoat93.org>
Subject: best practice for maintaining nnmaildir folders
Date: 01 Apr 2002 18:50:57 -0500 [thread overview]
Message-ID: <m3sn6fgeqm.fsf@hedwig.bluecoat93.local> (raw)
I wish to maintain my nnmaildir folders using shell tools. For example,
use 'find' and the like to archive old messages from cron. I'm using
the nnmaildir.el backend under gnus 5.8.8 and would like to know if
there is anything I need to do inside gnus to keep nnmaildir happy.
Obviously, if I move a bunch of messages from the shell, then
nnmaildir's idea of what messages there are is going to be incorrect.
Do I need to quit gnus, run my shell scripts, then restart? Is there a
'regenerate' command or something that needs to be run, or will
nnmaildir figure it all out?
Thanks,
Brian
--
Brian C. Landers | http://www.bluecoat93.org
brian@bluecoat93.org |
----------------------+-------------------------------------------------
"Destinations are often a surprise to the destined" -- Thessaly, Sandman
reply other threads:[~2002-04-01 23:50 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=m3sn6fgeqm.fsf@hedwig.bluecoat93.local \
--to=brian@bluecoat93.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).