From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: losing mail with nnml in 0.18
Date: 10 Dec 1995 16:16:05 +0100 [thread overview]
Message-ID: <w8sd99xkkzu.fsf@surt.ifi.uio.no> (raw)
In-Reply-To: raeburn@cygnus.com's message of 08 Dec 1995 18:32:09 -0800
raeburn@cygnus.com (Ken Raeburn) writes:
> A couple days ago I partially finished an rdist of my nnml hierarchy
> to another machine. This directory may not have been done, but the
> active file was. It had no entry for list.mit.zephyr at all. So my
> guess is that nnml-generate... omits empty (but existing) directories,
> confusing the code for filing new messages.
>
> If this is a problem caused by an earlier version, sinced fixed, and
> I'm only just noticing it now, feel free to ignore me. Well,
> actually, please tell me, so I'll stop worrying about losing more mail
> in the future...
It's a bug that hasn't been fixed yet. I've been wringing my brain
for a few weeks trying to remember just what was wrong with
`nnml-generate-nov-databases', but I just couldn't recall what it
was.
It's annoying being a total amnesiac.
--
Home is where the cat is.
prev parent reply other threads:[~1995-12-10 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-12-09 2:32 Ken Raeburn
1995-12-10 15:16 ` 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=w8sd99xkkzu.fsf@surt.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).