From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Messages Expire Even in Non-Expiry Group
Date: Fri, 16 May 2003 08:18:35 +0200 [thread overview]
Message-ID: <84k7crxvlw.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <76wugsc7ea.fsf@newjersey.ppllc.com>
Jake Colman <colman@ppllc.com> writes:
> I have an email group that does not use expiry. I copied emails from a group
> that does use automatic expiration (the emails had the 'E' mark) into this
> non-expiry group. The messages happily stayed in this group and never
> expired even though they had the 'E' mark - which is as I expected. After
> upgrading to 5.10.1 all those mails were deleted! Is this supposed to have
> worked this way? I lost a whole LOT of mail this way!
Messages marked `E' are supposed to be expired, *except* if
nnmail-expiry-wait or nnmail-expiry-target say something else.
So, actually, Gnus seems to have had a bug before that was now
fixed...
It's a pity that you lost email, of course.
--
This line is not blank.
next prev parent reply other threads:[~2003-05-16 6:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 19:54 Jake Colman
2003-05-16 6:18 ` Kai Großjohann [this message]
2003-05-16 7:25 ` Katsumi Yamaoka
2003-05-16 14:34 ` Jake Colman
2003-05-16 16:01 ` Katsumi Yamaoka
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=84k7crxvlw.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.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).