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:
>
>>> So it does seem that if NNTP can be synced with the .marks files, and
>>> IMAP groups don't need .newsrc.eld, then I can stop syncing .newsrc
>>> and .newsrc.eld -- topic changes notwithstanding.
>>
>> Yup.
>
> Nope, it turns out IMAP does not work properly without syncing
> .newsrc. Today I sent all my marks files home, but did not send
> .newsrc.eld along with them. When I connected to my nnimap servers at
> home, the message counts in the Group buffer are all wrong. Well, sort
> of; they count how many messages Gnus has not seen at home, not how
> many of my IMAP messages are unread. My INBOX, for example, noted 8
> new messages, but upon entering the group there were no new ones
> there. I had read them all at work already.

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'.

> Also, it looks like the expire mark is not synchronized. All of the
> IMAP messages that arrived in my INBOX today at work were marked as
> expirable (manually with 'E'), but none of those messages are marked
> as expirable now at home. Is the expirable mark supposedly stored on
> the server? If not, is .newsrc.eld the only place where expire marks
> are stored?

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.