Gnus development mailing list
 help / color / mirror / Atom feed
From: janneke@gnu.org
Subject: [PATCH] Expiry-target for nnmh
Date: 23 Nov 2000 11:07:15 +0100	[thread overview]
Message-ID: <m3bsv7roh8.fsf@appel.lilypond.org> (raw)

Hi,

My first patch to Gnus implements expiry-target for the nnmh backend.

    http://appel.lilypond.org/software/gnus-5.8.7.jcn1.diff

Is expiry-target widely used?  I'm new to Gnus; and sometimes a bit
confused about what one would actually use.  The auto-expiry feature
of read articles looks very promising, but it's not exactly what I
want.  Before, using plain mh and scripts, I used to move only mail
that I had answered semi-automatically to my archives, so that my
read-but-unanswered-messages would stay in my inboxes for
manual-archiving.  Can this be easily automated with Gnus?

While this was fine for personal mail, it was maybe not the perfect
solution for mailinglist-mail (answering bug-reports).  With Gnus, it
would be possible to improve on this, by auto-expiring only mail that
has been read, and of which the tread is longer than 1.  This way,
unanswered bug reports/help requests won't expire untill they're
answered by someone.  How do you handle this, or does this require
some more hacking?

Greetings,
Jan.

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org



             reply	other threads:[~2000-11-23 10:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-23 10:07 janneke [this message]
2000-11-23 15:21 ` Kai Großjohann
2000-11-30  1:50 ` ShengHuo ZHU
2000-11-30 19:40 ` Feature request: "Security" feature Raja R Harinath
2000-12-01  1:28   ` ShengHuo ZHU
2000-12-01  3:06     ` Michael Welsh Duggan
2000-12-01  4:22       ` ShengHuo ZHU
2000-12-01  3:06   ` Kevin A. Burton

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=m3bsv7roh8.fsf@appel.lilypond.org \
    --to=janneke@gnu.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).