From: Greg Troxel <gdt@work.lexort.com>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: auto auto-expirable
Date: Fri, 05 Jun 2009 08:34:40 -0400 [thread overview]
Message-ID: <smud49iq2ov.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <b4my6scjj4v.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon, 01 Jun 2009 20:20:00 +0900")
[-- Attachment #1: Type: text/plain, Size: 1993 bytes --]
My own usage falls more in line with the intent of the patch than
opposing it. I have not studied the details and hope that an ab initio
perspective is useful.
Basically, I have groups with 3 different settings:
no auto-expire (INBOX, etc. for real mail - I manually delete)
auto-expire (mailing lists, and I tick things I want to keep)
total-expire (spam, other low-value stuff like daily output mail)
Sometimes mail gets miscategorized by procmail, either because of spam
filtering errors (both ways), header regexp hairiness, or because I was
in To: in list mail.
What I do is "B m <group-where-it-belongs>". When mailing-list mail
ends up in my INBOX or spam (I filter at 1 SA point, so people using
junky MUAs from yahoo end up there), I generally have glanced at it
enough to know I don't care and want it to be marked expirable in the
mailinglist group. If I wanted to keep it I'd tick it right there. I
do want to put it in the mailinglist group because I want the next day's
bayesian training run to pick it up as ham; it might have just been
learned as spam.
If I move a message from a mailinglist group to another group, I'd like
the E flag to be set as if the message had been there in the first place
and then read.
I realize other people might not like this. So I think what's needed is
a global variable
expirable-per-destination
that if t means that the expirable mark on a message which is moved to a
destination is set according to what it would have been if
the message had been in the destination in the first place
the message has been read or not read there, based on whether it was
read or not read in the group it was in before.
Operationally, I think this just means.
if expirable-per-destination
messages moved into auto-expire groups
set expire-flag if read-flag
messages moved into other groups
clear expire-flag
else
status quo
People that don't like this can just not set expirable-per-destination.
[-- Attachment #2: Type: application/pgp-signature, Size: 193 bytes --]
prev parent reply other threads:[~2009-06-05 12:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 11:19 Katsumi Yamaoka
2009-05-29 12:08 ` Didier Verna
2009-06-01 3:36 ` Mike Kupfer
2009-06-01 8:35 ` Didier Verna
2009-06-01 11:20 ` Katsumi Yamaoka
2009-06-01 12:47 ` Tim Landscheidt
2009-06-02 2:23 ` Mike Kupfer
2009-06-02 11:12 ` Katsumi Yamaoka
2009-06-02 11:38 ` Katsumi Yamaoka
2009-06-04 4:13 ` Mike Kupfer
2009-06-13 14:22 ` Tim Landscheidt
2009-08-12 8:28 ` Katsumi Yamaoka
2009-06-02 17:34 ` Reiner Steib
2009-06-05 12:34 ` Greg Troxel [this message]
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=smud49iq2ov.fsf@linuxpal.mit.edu \
--to=gdt@work.lexort.com \
--cc=ding@gnus.org \
--cc=yamaoka@jpl.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).