From: Simon Josefsson <jas@extundo.com>
Subject: Re: B DEL is being treated as expiry?
Date: Fri, 26 Jul 2002 14:51:00 +0200 [thread overview]
Message-ID: <iluznwer6tn.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3ptxeuyuj.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Tue, 23 Jul 2002 13:40:14 -0400")
prj@po.cwru.edu (Paul Jarc) writes:
>> My 1-line fix makes it do that, again, for both the non-default
>> nnmail-expiry-target case as well as the group parms expiry-target
>> case.
>
> But only by chance, and only for certain backends. The backend
> interface must define how this is expressed, and all backends must be
> made to conform to that specification. g-s-d-a is not supposed to
> know the details of how backends decide what to do with expirable
> articles; it's only supposed to know what to pass to
> nnchoke-request-expire-articles.
I think the problem under discussion only happens for nnmail backends,
since the problem only happens when expiry targets which is a nnmail
thingie. So making the problem go away for nnmail backends only would
solve it.
(It also works for nnimap. Nnimap is not a nnmail backend strictly
speaking, but it uses most of the same variable anyway, for extra
confusion.)
next prev parent reply other threads:[~2002-07-26 12:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 11:21 Karl Kleinpaste
2002-07-23 11:49 ` Kai Großjohann
2002-07-23 13:40 ` Josh Huber
2002-07-23 13:58 ` Nevin Kapur
2002-07-23 16:03 ` Karl Kleinpaste
2002-07-23 16:16 ` Paul Jarc
2002-07-23 16:23 ` Karl Kleinpaste
2002-07-23 16:36 ` Paul Jarc
2002-07-23 17:01 ` Karl Kleinpaste
2002-07-23 17:40 ` Paul Jarc
2002-07-23 18:09 ` Karl Kleinpaste
2002-07-23 18:33 ` Paul Jarc
2002-07-24 15:44 ` Kai Großjohann
2002-07-24 16:05 ` Paul Jarc
2002-07-26 12:51 ` Simon Josefsson [this message]
2002-07-26 14:50 ` Paul Jarc
2002-07-26 16:37 ` Simon Josefsson
2002-07-26 16:48 ` Paul Jarc
2002-07-26 18:33 ` Simon Josefsson
2002-07-23 21:23 ` Nevin Kapur
2002-07-23 21:43 ` Paul Jarc
2002-07-24 2:08 ` Nevin Kapur
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=iluznwer6tn.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).