From: "Sven Bretfeld" <sven.bretfeld@gmx.ch>
To: "Greg Troxel" <gdt@work.lexort.com>
Cc: "Sven Bretfeld" <sven.bretfeld@gmx.ch>, ding@gnus.org
Subject: Re: Marking a whole imap-Folder as Expired
Date: 5 Oct 2011 00:05:31 +0200 [thread overview]
Message-ID: <87k48ks990.fsf@gmx.ch> (raw)
In-Reply-To: <smuk48mz3o9.fsf@linuxpal.mit.edu> (Greg Troxel's message of "Mon, 03 Oct 2011 07:59:34 -0400")
Hi Greg
Greg Troxel <gdt@work.lexort.com> writes:
> "Sven Bretfeld" <sven.bretfeld@gmx.ch> writes:
>> Therefore, I have several messages in my inboxes marked with "O" (old),
>> which excludes them from the expiry-process. Back in Gnus I have to
>> manually set them to expired with by hitting "E" one after the other.
>
> Not what you asked, but I do this totally differently.
>
> I use gnus as my main mail reader, and also thunderbird, osx/Mail.app,
> and iphone/Mail. While my mailinglist mail is like news, I consider my
> INBOX to be not like news, and basically only want to explicitly delete
> things.
>
> So, I have all the non-gnus MUAs set up to delete by moving to
> nnimap+[foo]:Trash (vs "Deleted Messages" with whitespace), and then
>
> Then I bind 'd' to
>
> (defun gdt-gnus-move-to-trash ()
> (interactive)
> (gnus-summary-move-article nil gdt-trash-newsgroup))
>
> and delete messages when I'm done with them.
Its interesting to read how other people cope with the ideosyncratisms
of Gnus (compared to other mail readers). I do it differently. Since I'm
using Gnus I got used to treat emails like news, and I like to have them
out of sight after I have read them. Therefore it annoys me to see all
my old mails when I'm in K9. In Gnus I organize my mails in a GTD-style
structure. If it takes more than two minutes, I mark it unread and shift
it to a "processing" folder: Action, Waiting, Review, Urgent etc. This
workflow is interrupted in K9 where all my expired mails become visible
again. Therefore I have my inboxes (the workflow-folders as well as the
main inbox) set to auto-expire immediately with an "Expired" folder as
the expiry-target. Just to have expired mails out of sight for K9. The
"Expired" folder keeps mails for 14 days, this is the expected
time-frame where it is possible that I have to visit that mail again due
to follow-ups or reference purposes. After that they expire into a spool
folder where they are fetched by fetchmail (POP) (and deleted from the
server) to one of my local machines where they are stored in an
ever-growing archive.
> This whole scheme is built around the notion that I want reading the
> INBOX on my phone to be useful, which for me means that all mailinglist
> mail (and anything that gets even 1 point with spamassassin) does not
> go to INBOX.
I split mails similarly. The major INBOX is only for personal mail,
which is then manually "processed" into the work-flow folders.
Mailing-lists I don't access with my mobile or tablet. I only read them
with Gnus. If I like to read them en route I ssh into the PC.
Greetings,
Sven
next prev parent reply other threads:[~2011-10-04 22:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 6:51 Sven Bretfeld
2011-10-03 11:59 ` Greg Troxel
2011-10-04 22:05 ` Sven Bretfeld [this message]
2011-10-07 1:06 ` Dan Christensen
2011-10-10 15:19 ` Eric S Fraga
2011-10-03 15:16 ` Eric S Fraga
2011-10-04 22:13 ` Sven Bretfeld
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=87k48ks990.fsf@gmx.ch \
--to=sven.bretfeld@gmx.ch \
--cc=ding@gnus.org \
--cc=gdt@work.lexort.com \
/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).