Gnus development mailing list
 help / color / mirror / Atom feed
From: Nevin Kapur <nevin@jhu.edu>
Subject: Re: Expiry of drafts
Date: Fri, 17 Aug 2001 18:24:06 -0400	[thread overview]
Message-ID: <m33d6qjpfd.fsf@fermat.mts.jhu.edu> (raw)
In-Reply-To: <m3lmkiwqrk.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Fri, 17 Aug 2001 19:16:47 +0200")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Nevin Kapur <nevin@jhu.edu> writes:
>
>> I would like to know how the expiry of articles in nndrafts:drafts
>> takes place.
>
> There is no expiration in the drafts group.

Oh, I didn't know that.

>> Something weird is happening for the drafts groups though. All my
>> current drafts seem to land up in a group nnml:Archive-2001-Aug. I
>> have the following set up as drafts' group parameters:
>>
>> ((expiry-wait . immediate)
>>  (expiry-target . delete)
>>  (gnus-dummy
>>   (gnus-draft-mode))
>>  (gnus-use-scoring nil))
>
> Oh.  Er, unless you specify that you want expiration the drafts group,
> I guess.  Why would you want that?

I don't. I was under the impression that there *was* expiry in drafts
and I needed to disable it. Anyway if one does want expiry and sets
the expiry-target group parameter, it is not honored.

> Anyway.  Hm.  How do you do your expiration?

I have my own function that looks at headers for each article and
decides what to do with it. In some groups I don't want expiry and I
disable it in them with group parameters.


-- 
Nevin


      reply	other threads:[~2001-08-17 22:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-14 18:48 Nevin Kapur
2001-08-17 17:16 ` Lars Magne Ingebrigtsen
2001-08-17 22:24   ` Nevin Kapur [this message]

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=m33d6qjpfd.fsf@fermat.mts.jhu.edu \
    --to=nevin@jhu.edu \
    /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).