Solved! (was: Looking for the variable that controls newsgroup scanning)

[Lloyd Zusman <ljz@asfast.com>]

Lloyd Zusman <ljz@asfast.com> writes:

> I'm making use of several nnimap groups, each of which being defined
> within `gnus-secondary-select-methods'.  As far as I can tell, each one
> is defined identically, the only difference being their names.
>
> However, only the first of these three gets updated during
> `gnus-group-get-new-news'.  I need to enter the other two and
> specifically invoke `gnus-summary-rescan-group' in order for them to
> notice any new mail that might have arrived.
>
> I suspect that ages ago, I might have set some sort of variable which
> prevents all but the first nnimap group from being scanned during
> `gnus-group-get-new-news', but I can't for the life of me recall what I
> might have done, nor have I been able to find anything within my setup
> that seems to affect this behavior.
>
> Could any of you suggest some possible variables or settings that might
> control this?

I found it: I need to set `nnimap-need-unselect-to-notice-new-mail' in
the select methods for each of my nnimap servers.  It doesn't seem to be
needed with a single nnimap server, but it has to be there for the sake
of the 2nd through nth servers.  I put it on all three select methods,
although perhaps it isn't needed on the first one.  But it doesn't seem
to hurt being there, so I'll leave it.

I'm using Courier IMAP, which the documentation states is a server that
probably needs this setting.

Thanks to all for your help when I was trying to diagnose this.

-- 
 Lloyd Zusman
 ljz@asfast.com