From: prj@po.cwru.edu (Paul Jarc)
Cc: ding@gnus.org
Subject: Re: nnmaildir, expiry problem
Date: Thu, 21 Feb 2002 13:12:08 -0500 [thread overview]
Message-ID: <m3lmdmd7qp.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <zds.p90.m3sn7vg6pn.fsf@tcob1.net> (Sean Rima's message of "Wed, 20 Feb 2002 21:54:12 +0000")
Sean Rima <spamtrap@tcob1.net> wrote:
> (setq nnmail-expiry-wait-function
...
> What else do I need to do or can you not expire mail whilst using
> nnmaildir.
You can, but nnmaildir doesn't look at nnmail-* unless you tell it to
(via the group parameters that nnmaildir *does* look at). nnmaildir
is Different.
(add-to-list 'gnus-parameters
'("" (expire-age . [(your-expire-age-function)])))
(defun your-expire-age-function ()
(if nnmail-expiry-wait-function
(* 86400 ;; seconds per day
(nnmail-expiry-wait-function
(gnus-group-real-name gnus-newsgroup-name)))
nnmail-expiry-wait))
I'll see how much it would impact the existing nnmaildir code to make
this the default when the expire-age parameter is not set, so you
could pretend nnmaildir looks directly at nnmail-*.
See <URL:http://multivac.cwru.edu./nnmaildir/using/#group-setup>,
which I really ought to add to the Gnus manual soon.
paul
next prev parent reply other threads:[~2002-02-21 18:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 21:54 Sean Rima
2002-02-21 17:26 ` Kai Großjohann
2002-02-21 17:26 ` Kai Großjohann
2002-02-21 20:24 ` Sean Rima
2002-02-21 20:24 ` Sean Rima
2002-02-21 18:12 ` Paul Jarc [this message]
2002-02-21 19:06 ` cvs commit stalling (was: nnmaildir, expiry problem) Paul Jarc
2002-02-21 19:06 ` Paul Jarc
2002-02-21 20:25 ` nnmaildir, expiry problem Sean Rima
2002-02-21 20:25 ` Sean Rima
2002-02-21 21:28 ` Sean Rima
2002-02-21 21:46 ` Paul Jarc
2002-02-21 21:46 ` Paul Jarc
2002-02-21 23:03 ` Sean Rima
2002-02-21 23:03 ` Sean Rima
2002-02-21 21:28 ` Sean Rima
2002-02-21 18:12 ` Paul Jarc
2002-02-20 21:54 Sean Rima
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=m3lmdmd7qp.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=ding@gnus.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).