David (and others on list),
Hi, again. Thanks for the advice so far. (I took your suggestion and
joined the list.)
So, I understand from you that what I had hoped to do is not possible
in mutt. Instead, I think I'm going to turn the question now on its
head, question _my_ assumptions in reading mailing list mail and ask
for further advice :).
I come from pine (which I never liked) and mh (which I was quite fond
of, though not as much as mutt, but in any case isn't available in my
present computing environment; neither for that matter do the
sysadmins support IMAP for the workaround you propose; and I've found
some relatively easy things like procmail are hard here since I'm on
an AFS cell). Anyway...
I'd appreciate your (and/or other peoples') suggestions for
efficiently dealing with high-traffic mailing lists (100+ messages per
day each). I use to do digests in pine with the persistent delete
flags I was hoping for here, but now I find that mutt's threading of
messages, combined with procmail's sorting them into individual
inboxes per mailing list, allows me to be probably 5-10 times more
efficient in handling mail than the previous digest way (and
_especially_ simplifies replying to such mail).
But, how do most people handle keeping track of which mail has been
read? flags? old/new? Or what else can people suggest to further ease
things?
Thanks so very much for any and all replies.
Take care,
Daniel
On Fri, Dec 15, 2000, David T-G wrote:
Daniel --
...and then Daniel Freedman said...
% Hi,
Hello!
%
% Apologies upfront if this is well-known, but I searched mutt.org's FAQ
% and manual, google's linux area , deja, etc. and came up completely
% empty.
%
% I'd very much like to be able to set a message's status to 'deleted',
% but: without synchronizing my mailbox/folder so as to actually expunge
...
% similar, but I'd prefer to be unanbiguous in my mind and use the
% DELETE flag instead.
While that makes some sense, and I can understand your thoughts about
threading becoming messy, that is not available in mutt. You can either
quit or change and that will both sync your mailbox and mark items as old
if you have mark_old set or you can just sync (bound by default to $) to
write flag settings and purge deleted items, but there's no way to keep
them around.
%
% Thanks so much for the suggestions (just a pointer to the right
% document would also be appreciated).
All I can suggest is that you read your mail through an IMAP connection,
which apparently does allow you to store a 'D'elete flag across sessions.
You might, though it's somewhat messy, whip up a macro that sets the
X-Label: field to anything you wish; you could later go back and limit
your view to just those messages and then truly delete them. You can
even display the X-Label field in your index, so you could just make it
'D' and have another status-like column to show you what is what. If I
were to do that, though, I'd probably set the field to something like the
day of the month or even the julian day and then delete only the oldest
marked messages.
%
% Take care,
HTH HAND
%
% Daniel
%
%
% PS. Please cc me on replies as I don't subscribe. Thanks so much.
Ah, but you should ;-)
%
% --
% Daniel A. Freedman
% Laboratory for Atomic and Solid State Physics
% Department of Physics
% Cornell University
:-D
--
David T-G * It's easier to fight for one's principles
(play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie
(work) [EMAIL PROTECTED]
http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
--
Daniel A. Freedman
Laboratory for Atomic and Solid State Physics
Department of Physics
Cornell University
