From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Problem with immediate expiration of messages
Date: Sat, 18 Oct 2003 00:22:41 +0200 [thread overview]
Message-ID: <m3u1674i8e.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <u4r26wlfq.fsf@axis.com>
Niklas Morberg <niklas.morberg@axis.com> writes:
> If I set the group parameter `expiry-wait' to `immediate' I
> can't expire messages in that group. I have:
[...]
> Setting `expiry-wait' to 1.0 shows the more sane behaviour:
Hm... `immediate' shouldn't affect, er, what happens elsewhere. I
mean, it's just the predicate used for selecting messages to expire.
Is the bug reproducible?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2003-10-17 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 11:11 Niklas Morberg
2003-10-17 22:22 ` Lars Magne Ingebrigtsen [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=m3u1674i8e.fsf@quimbies.gnus.org \
--to=larsi@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).