Re: Automatically marking Gcc's as SEEN in nnimap

[David Engster <deng@randomsample.de>]

Lloyd Zusman <ljz@asfast.com> writes:
>> Works for me. You can enable IMAP logging (by setting imap-log) and see
>> if catching up produces commands like
>>
>> 3365 UID STORE 5031 +FLAGS (\Seen)
>
> Yes, I do see this in the *imap-log* buffer after issuing a
> `gnus-group-catchup-current' command. Here are the entries that got
> written to *imap-log* during the course of an invocation of that
> command:
>
>   1236 NOOP
>   1236 OK NOOP completed.
>   1237 UID STORE 3892 +FLAGS (\Seen)
>   * 3296 FETCH (UID 3892 FLAGS (\Seen))
>   1237 OK Store completed.

Looks good.

> Furthermore, immediately after this command completes, the articles seem
> to be marked as SEEN (or at least they are not flagged as unread/unseen
> in the *Summary* buffer).  However, if I then run a
> `gnus-group-get-new-news', the unread/unseen mark returns, and I can
> only make it go away by actually reading the article.

I would guess this behavior comes from gaps in the article numbers. This
problem can't currently properly dealt with and also depends on the used
IMAP server. Does doing M-g on that group fix the number?

> Could it be that some sort of local marks (local to gnus) don't get
> properly changed from un-SEEN to SEEN when I do
> `gnus-group-catchup-current' on a primary nnimap group, and could these
> local marks somehow get re-propagated back to the IMAP server during
> `gnus-group-get-new-news'?

No, they don't get re-propagated to the IMAP server. Gnus simply doesn't
have all the necessary information for correctly calculating the number
of unread articles. When you do gnus-group-get-new-news, Gnus will try
to determine the number of unread articles purely based on the active
information (ie. lowest and highest article number in a group), and on
the group info, which contains the article numbers of already seen
articles. When you do M-g on a group, it will also re-scan the group on
the server, which can sometimes correct this problem.

> I added this hook and re-ran `gnus-group-catchup-current', and I indeed
> see the newsgroup name in the message buffer without any
> `nnimap+SERVER:' prefix.
>
> And I double-checked: this is definitely a group that is managed by my
> nnimap primary back end.
>
> For the secondary back end, this hook causes `nnimap+SERVER:groupname' to
> be written in the message buffer.

This is the correct behavior.

Regards,
David