From: Mark Triggs <mst@dishevelled.net>
Subject: Re: Mail lost when going from Oort v0.08 to 5.9.0
Date: Wed, 11 Sep 2002 11:51:56 +1000 [thread overview]
Message-ID: <87u1kxmgxv.fsf@dishevelled.net> (raw)
In-Reply-To: <iluy9aakvxc.fsf@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> Then it looks like your group parameters are fubar. nnml:tim
> shouldn't have a expiry-wait of 60, shouldn't it? Your ascii art
> group buffer indicated otherwise.
>
> (It could also be a bug of course, but more checking why those
> functions return what they do would be needed before that is proven.)
I've just been doing some tests to ensure that functions are returning
what I expect. I've also realised that I made an error before when
showing what (gnus-group-find-parameter "nnml:tim" 'expiry-wait) etc
evaluated to.
I've actually got my gnus-select-method set to "nnml", so prefixing the
group with nnml: probably wasn't necessary. Without this, the lines
before evaluate to:
> (gnus-group-find-parameter "tim" 'expiry-wait)
nil
> (gnus-group-find-parameter "ding" 'expiry-wait)
60
> (gnus-group-find-parameter "tim" 'expiry-target)
nil
> (gnus-group-find-parameter "ding" 'expiry-target)
nil
Which is more consistent with my ascii diagram from before - groups such
as "tim" under the "People" topic don't get expired at all, whereas
groups under the "Discussion" topic get deleted after 60 days.
I might poke around with different configurations and see if I can
pinpoint the error a little more precisely. If I come up with anything
that looks like a bug, I'll let you know.
Thanks again for your help :o)
Mark
--
Mark Triggs
<mst@dishevelled.net>
prev parent reply other threads:[~2002-09-11 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r8gcrgn0.fsf@thweeble.telefunken.dyn.ml.org>
[not found] ` <iluk7m3g5im.fsf@latte.josefsson.org>
[not found] ` <87lm6hqe93.fsf@thweeble.telefunken.dyn.ml.org>
[not found] ` <iluvg5g4i8a.fsf@latte.josefsson.org>
2002-09-09 22:31 ` Mark Triggs
2002-09-10 9:58 ` Simon Josefsson
2002-09-11 1:51 ` Mark Triggs [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=87u1kxmgxv.fsf@dishevelled.net \
--to=mst@dishevelled.net \
/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).