Gnus development mailing list
 help / color / mirror / Atom feed
From: Jody Klymak <jklymak@apl.washington.edu>
Cc: ding@gnus.org
Subject: Re: Expiry
Date: 27 Sep 1999 12:19:23 -0700	[thread overview]
Message-ID: <d7v4now4.fsf@apl.washington.edu> (raw)
In-Reply-To: Adam Kornick's message of "27 Sep 1999 14:52:03 -0400"


Hi Adam,

I'm no wiz on these things, but is it correct to set both auto-expiry
and total-expiry to t?  I bet you really should only use one or the
other.  I personally use total-expiry, with a seven day grace pesiod
on mailing lists and no expiry on personal mail.  So for this mailing
list I have

;;; Editing the group parameters for `nnimap+kraken:mail/ZIn.xemacs-nt'.
;; Type `C-c C-c' after you've finished editing.

((uidvalidity . "936820603")
 (total-expire . t)
 (expiry-wait . 7.0))

i.e. nothing newer than seven days is expired.  

While for my personal mail boxes I have

((uidvalidity . "902853515")
 (visible . t))

So nothing is expired unless I explicitly set it so.  I also set d to
equal E since it makes more sense to me - in my .gnus:

;; remap d to E
(define-key gnus-summary-mode-map "d" 'gnus-summary-mark-as-expirable)

Stuff I want to expire gets a "d", stuff I want to keep seeing gets a
"!", and stuff I want to keep, but not see all the time gets no
action.  Of course, this means I have to do a little cleaning in my
personal mailbox once in a while, but thats OK. 

Hope this is of help,

Jody

>>>>> "AMK" == Adam Kornick <akornick@whgrp.com> writes:

    AMK> I have been attempting to automagically delete old messages
    AMK> from mailing lists that I read with pgnus 0.97.  I have
    AMK> edited the group parameter buffer (`G p') as follows.

    AMK> --- ;;; Editing the group parameters for `nnfolder:gnus'.  ;;
    AMK> Type `C-c C-c' after you've finished editing.

    AMK> ((auto-expiry t) (total-expiry t)) ---

    AMK> However, read articles are not automatically marked as
    AMK> expired, and read articles are not expired, so it seems that
    AMK> neither variable setting is having an affect.  Clearly I
    AMK> either do not understand expiration or have made an obvious
    AMK> mistake or both.  Anybody who can help me set up expiry to
    AMK> remove read messages without marking them by hand as
    AMK> expirable, I would appreciate your help.

    AMK> Thanks,

    AMK> -- Adam Kornick Coastal Engineer Woods Hole Group

-- 
Jody Klymak                         APL/School of Oceanography,
Doctoral Candidate                  University of Washington
mailto:jklymak@apl.washington.edu   (206)-685-9080
http://www.ocean.washington.edu/people/grads/jklymak/



  parent reply	other threads:[~1999-09-27 19:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-27 18:52 Expiry Adam Kornick
1999-09-27 19:13 ` Expiry Toni Drabik
1999-09-27 21:05   ` Expiry Adam Kornick
1999-09-27 21:15     ` Expiry Lars Magne Ingebrigtsen
1999-09-27 19:19 ` Jody Klymak [this message]
1999-09-27 19:30   ` Expiry Toni Drabik
1999-09-27 22:25     ` Expiry Kai Großjohann
1999-09-28  2:29     ` Expiry Jody Klymak

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=d7v4now4.fsf@apl.washington.edu \
    --to=jklymak@apl.washington.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).