From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/3724 Path: news.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.user Subject: Re: Syncing nnimap more aggressively? Date: Sun, 18 Apr 2004 13:19:55 +0200 Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138669744 20058 80.91.229.2 (31 Jan 2006 01:09:04 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 01:09:04 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:32:39 2006 Original-Path: quimby.gnus.org!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: fnatte.nada.kth.se Original-X-Trace: quimby.gnus.org 1082287201 722 130.237.226.103 (18 Apr 2004 11:20:01 GMT) Original-X-Complaints-To: usenet@quimby.gnus.org Original-NNTP-Posting-Date: Sun, 18 Apr 2004 11:20:01 +0000 (UTC) User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3.50 (gnu/linux) Cancel-Lock: sha1:ipjQvkdWi4vbYW0r0j9IAmEdsik= Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:3865 Original-Lines: 31 X-Gnus-Article-Number: 3865 Tue Jan 17 17:32:39 2006 Xref: news.gmane.org gmane.emacs.gnus.user:3724 Archived-At: Kinkie writes: > Simon Josefsson writes: > >> Kinkie writes: >> >>> Hi all. >>> I would like to be able to use a few mailboxes from different >>> client systems. I've noticed that nnimap doesn't really sync its state >>> with the remote system, but apparently keeps a lot of state in >>> .gnus.eld. >>> >>> Is it possible to instruct nnimap to just store message state on the >>> imap server? >> >> Nnimap should do this. At least if "message state" includes flags. >> What is it that nnimap doesn't sync from the server, for you? > > When I access the same mailboxes from another client, I see that only > some of the read messages have been marked as such, and not all > expired messages have been expunged. The latter I can live with, but > the former is annoying. Right, and at least the former shouldn't happen. If you (setq imap-log t) and show us the output generated into the buffer *imap-log* by entering a group that exhibit this, this might help. There should be a UID SEARCH SEEN command there, which return a list of article numbers. Verify if this list is correct or not. If the list is incorrect, it is the server that has a problem (unless Gnus somehow actually marked some of you seen articles as unseen, before that, of course).