>>>>> In <87ejjukg6s.fsf@florent.maison> Florent Rougon wrote:

> With your recipe and without the patch, I can reproduce the bug. Again
> with the same recipe but with the patch applied, the bug doesn't happen.
> I'll now start reading again some nntp newsgroups and tell you if
> anything wrong happens, but I think you did spot and fix the problem I
> was experiencing.

Thanks for verifying the patch.  However, what I did might be
a kludge.  That is, making nnagent handle marks of the specific
back ends looks ill-mannered, since to abstract the actual back
ends seems to be one of the aims of nnagent.  The reason I changed
my idea is because I found the variable:

gnus-agent-synchronize-flags

The default value is nil.  See (info "(gnus)Agent and flags").
Does setting it to t solve the problem that you all are troubled
with?  Could someone, who uses Gnus v5.11, try it?  (I couldn't
reproduce the problem with Gnus v5.11 so far, though.)

But, for all that, updating at least the nntp marks when unplugged
is absolutely necessary.  Because the nntp marks can be copied to
another nntp client that connects to the same nntp server.

The patch I posted is probably harmful to some back end(s) that
keeps marks in the server, not the local system, and is unable
to set marks when unplugged.  I'm not quite sure of it but at
least the nnimap back end seems to be applied to.  Therefore, I
installed the code that I modified so that it may work with only
the nntp back end, in the Gnus CVS trunk.

Here is a revised patch for the released No Gnus v0.6: