Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Peter Solodov <peter@alcor.concordia.ca>
Subject: nnmail-expiry-wait, nnmail-expiry-wait-function and gnus-parameters
Date: Fri, 04 Apr 2003 10:16:26 -0500	[thread overview]
Message-ID: <87adf6pa2d.fsf@lorien.concordia.ca> (raw)

Hi,

I've installed recent version of Gnus (Oort Gnus v0.17) and found that
group parameters can now be specified in gnus-parameters variable.
This is a welcome change, I've always wanted to specify parameters
this way rather than in .newsrc.eld.  So I went on and partially did
it.  Here's what gnus-parameters is now:

   (("^nnml:\\(inbox.*\\|sent.*\\|junk\\)"
     (gnus-use-scoring nil)
     (adapt nil))
    ("^nnml:inbox$"
     (nnmail-expiry-wait 31))
    ("^nnml:sent$"
     (nnmail-expiry-wait 15))
    ("^nnml:junk$"
     (nnmail-expiry-wait 7))
    ("^nnml:reports.*"
     (gnus-show-threads nil)
     (gnus-signature-face nil)
     (gnus-use-scoring nil)
     (adapt nil)
    (nnmail-expiry-wait 30))
   ("^nnml:reports.newsflash.usenet"
    (nnmail-expiry-wait 7)))

Before that I used to specify expiry wait periods in
nnmail-expiry-wait-function, but now it kind of made sense to put
periods in gnus-parameters.  nnmail-expiry-wait is set to 'never.  I'm
using total expiry for all my mail.

So the question is will expiry process use gnus-parameters when
expiring articles?

I guess I should also mention I've had an unpleasant surprise already.
By default nnmail-expiry-wait was set to 7 (before I set it to 'never)
and Gnus expired a lot of messages in "^nnml:reports.*" groups which
were not yet 30 days old.  That clearly was wrong.  Thankfully, those
messages were not that important, but it scares me Gnus could do that
to my more important mail.  I need to get that part straight.

TIA,

        - Peter

-- 
Peter Solodov                    | Concordia University 
http://alcor.concordia.ca/~peter | Montreal, QC, Canada


                 reply	other threads:[~2003-04-04 15:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87adf6pa2d.fsf@lorien.concordia.ca \
    --to=peter@alcor.concordia.ca \
    /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).