Gnus development mailing list
 help / color / mirror / Atom feed
From: Andrew Hobson <ahobson@eng.mindspring.net>
Subject: mail archival idea/feature request
Date: 09 Jul 1999 14:27:37 -0400	[thread overview]
Message-ID: <kjwvw9oezq.fsf@gamma.eng.mindspring.net> (raw)

The recent thread about mail archival got me thinking.  Maybe I'm
completely off the boat in the deep end, but here's how I'd like it to 
work.

At expiry time, instead of deleting the message, I'd like to move it
into another, non-expiring group.  That way I could archive all of my
incoming mail, but it would remain in the usual group until
expiration.  I could then determine at expiry time if I wanted to save
the message, and if so, which archival group to put it in.

I took a quick peek and I didn't see an easy way to do this, although
I'm a gnus neophyte.  It would seem to me that a customizable hook run
at expiry time that defaults to nnmail-delete-file-function (or
whatever is appropriate for the backend) would enable me to do what I
wanted.

I suppose I could deliver the mail to two groups at split time: one
for archival and one for usual purposes, but that seems less that
optimal.

Is there a way in pgnus to do this kind of archival?

Drew


             reply	other threads:[~1999-07-09 18:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-09 18:27 Andrew Hobson [this message]
1999-07-09 21:04 ` Lars Magne Ingebrigtsen
1999-07-09 21:39   ` Andrew Hobson
1999-07-11  8:58     ` Lars Magne Ingebrigtsen
1999-07-09 22:49 ` Kai.Grossjohann
1999-07-10 13:53   ` Andrew Hobson
1999-07-10 21:23     ` Kai.Grossjohann
1999-07-12 14:50       ` Andrew Hobson
1999-07-12 15:24       ` Karl Kleinpaste
1999-07-12 15:52   ` Wes Hardaker
1999-07-12 16:13     ` Kai Großjohann
1999-07-12 15:55 ` Wes Hardaker
1999-08-27 17:39   ` Lars Magne Ingebrigtsen
1999-09-01 16:53     ` Wes Hardaker
1999-09-01 19:06       ` Andrew Hobson
1999-09-03 21:32         ` Wes Hardaker
1999-09-03 22:11           ` Andrew Hobson
1999-09-07 17:33             ` Wes Hardaker
1999-09-25  7:51         ` Lars Magne Ingebrigtsen

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=kjwvw9oezq.fsf@gamma.eng.mindspring.net \
    --to=ahobson@eng.mindspring.net \
    /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).