From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: irritated by all those "no new mail" messages
Date: 11 Nov 1999 14:18:40 +0100 [thread overview]
Message-ID: <m3g0yd180f.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m1so2hgf5s.fsf@halfdome.holdit.com>
merlyn@stonehenge.com (Randal L. Schwartz) writes:
> For more data, also consider that: M-x gnus works fine (correct looking
> entry messages), but M-x gnus-no-server, which pulls in only the
> 1,2 level groups for me (all nnml) displays the correct incorporating
> messages but a HUGE SLEW of bad messages as well.
Hm. There is code in nnmail to avoid scanning for new mail more than
once...
Could you `M-x debug-on-entry nnmail-get-new-mail RET', hit `2 g'
and see what the value of `nnmail-fetched-sources' is for each of the
calls? (Well; for five or six of the calls, anyway.)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-11-11 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-02 15:39 Randal L. Schwartz
1999-11-02 16:33 ` Stephen Zander
1999-11-02 18:36 ` Randal L. Schwartz
1999-11-07 0:40 ` Lars Magne Ingebrigtsen
1999-11-08 15:46 ` Randal L. Schwartz
1999-11-11 13:18 ` 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=m3g0yd180f.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).