Re: nnimap problem solved by removing .agentview and .overview

[Simon Josefsson <jas@extundo.com>]

"Steven E. Harris" <seh@panix.com> writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> The unread article count in group buffer is only an estimate.  In
>> situations like this, it will be wrong.  But I thought there was
>> some workaround for this.  What's the value of
>> `gnus-after-getting-new-news-hook' for you?  It should include
>> `gnus-fixup-nnimap-unread-after-getting-new-news'.
>
> ,----[ gnus-after-getting-new-news-hook ]
> | `gnus-after-getting-new-news-hook' is a variable declared in Lisp.
> |   -- loaded from "gnus-start"
> | 
> | Value: (gnus-display-time-event-handler gnus-fixup-nnimap-unread-after-getting-new-news)
> | 
> | Documentation:
> | *A hook run after Gnus checks for new news when Gnus is already running.
> `----
>
> The fixup hook is in there, but it's not doing its job. I did note
> that hitting M-g on the group before entering it fixes the
> count. Perhaps this hook is not getting run upon initial connection.

If someone could debug this, that would be good.  One would have to
verify that the IMAP data returned from the server is actually
accurate, first, and then check that the hook does the right thing.
I'm not sure I can assist with this via email...

>> They are supposed to be stored on the server, if the server support
>> client-specific flags.  Do (setq imap-log t) and look in *imap-log*
>> buffer for the PERMANENTFLAGS value for the mailbox, e.g.:
>>
>> * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen NonJunk \*)]  
>>
>> The \* is the critical value.  If it is absent, Gnus cannot store
>> non-standard flags on the server.
>
> ,----
> | 187 EXAMINE "INBOX.lists.gnus-ding"
> | * FLAGS (\Draft \Answered \Flagged \Deleted \Seen \Recent)
> | * OK [PERMANENTFLAGS ()] No permanent flags permitted
> | * 29 EXISTS
> | * 0 RECENT
> | * OK [UIDVALIDITY 1067647543] Ok
> | * OK [MYRIGHTS "acdilrsw"] ACL
> | 187 OK [READ-ONLY] Ok
> `----
>
> Lovely. Is this something that I can appeal to my ISP's administrators
> to enable, or is it an inherent feature lack in a given IMAP
> implementation (in this case, Courier)?

Most likely the latter, alas.

> Just to reiterate, though, .newsrc.eld is in fact quite necessary for
> maintaining proper IMAP state if the server isn't as complicit as Gnus
> would prefer. Perhaps we can move these nnimap marks out of
> .newsrc.eld, or at least echo them into marks files like the NNTP
> backends do.

Yes, that would be possible.  Nnimap could decide which marks the
server doesn't support, and write those in ~/News/marks/nnimap:foo/ or
somewhere, which then could be synced.