From: dsg@mitre.org (David S. Goldberg)
Subject: Re: has "incorporating new mail" bug been fixed yet?
Date: 23 Dec 1999 15:39:21 -0500 [thread overview]
Message-ID: <m1b7li55r46.fsf@blackbird.mitre.org> (raw)
In-Reply-To: merlyn@stonehenge.com's message of "23 Dec 1999 12:18:00 -0800"
> Do you have a directory source? I use procmail-like software to
> presort my mail, so I have (mumble) 50-some .spool files in my
> ..incoming directory. And I see 50-some "new messages" messages
> each time. It probably would be OK if GNUS deleted the files, but I
> think we'd have a locking staredown problem at that point.
Even if GNUS did delete the empty files, it wouldn't make a
difference.
As you note, the problem is due to using a directory source, but it's
not the case that the existence of 50-some .spool files causes the
problem. The problem is that you've got 50-some nnml groups at levels
1 and 2 and the directory is being searched for a file for each one,
whether or not such a file exists. This is apparently (to me, based
on the explanation I only vaguely recall from Simon) due to nnml not
having a particular feature in the nnml-request-scan function. I've
tried to look at what Simon did with nnimap-request-scan, but I just
plain don't get the code. This is, in my opinion, a side effect of
the design of mail-source versus the old procmail specific code. I am
quite certain that Lars is aware of this, I'm not so certain he
considers it a bug.
--
Dave Goldberg
Post: The Mitre Corporation\MS B325\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org
next prev parent reply other threads:[~1999-12-23 20:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-23 17:51 Randal L. Schwartz
1999-12-23 18:23 ` David S. Goldberg
1999-12-23 20:16 ` Randal L. Schwartz
1999-12-23 18:39 ` Bud Rogers
1999-12-23 20:18 ` Randal L. Schwartz
1999-12-23 20:39 ` Bud Rogers
1999-12-23 20:39 ` David S. Goldberg [this message]
1999-12-24 6:15 ` Randal L. Schwartz
1999-12-24 23:46 ` Simon Josefsson
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=m1b7li55r46.fsf@blackbird.mitre.org \
--to=dsg@mitre.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).