Re: ahh... it's the problem noted a few months back

[dsg@mitre.org (David S. Goldberg)]

Yes, this is the one thing I really dislike about the new mail-source
stuff.  I guess it works OK for people who use gnus' internal
splitting since the only people I see complaining use something
external (e.g. procmail or whatever).  The only workaround I know of
is to set those nnml groups that actually expect to receive new mail
to a lower level and then call 'g' with that level.  This works, but
I've found other reasons for it to be less than satisfying; in
particular the only way I can find to activate all the other groups
(so I can get completion on their names, if nothing else) is to call
'g' with the higher level and that takes a long time due to the
attempt to fetch new mail that is guaranteed not to be there.  It also
means that I've got a difficult choice of whether to put those groups
at a level higher or lower than nntp groups.  I've chosen lower which
means when I want to read nntp groups (via 4 g in my case) I have to
wait for nnml to try to fetch new mail for all the higher level
groups.  I live with this because I don't read nntp groups all that
often.  I think someone once suggested creating a separate nnml server
for the non-mail-receiving groups, but that just seems like too much
of a hassle.
-- 
Dave Goldberg
Post: The Mitre Corporation\MS B325\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org