From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/68062 Path: news.gmane.org!not-for-mail From: David Engster Newsgroups: gmane.emacs.gnus.general Subject: Re: Automatically marking Gcc's as SEEN in nnimap Date: Mon, 05 Jan 2009 00:57:46 +0100 Message-ID: <874p0epqth.fsf@randomsample.de> References: <877i5zyw2o.fsf@gmail.com> <84ljuecjdi.fsf@incoming.verizon.net> <87prj49ugi.fsf@randomsample.de> <87mye8t1zr.fsf@engster.org> <87d4f2py1o.fsf@randomsample.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1231113514 15913 80.91.229.12 (4 Jan 2009 23:58:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 4 Jan 2009 23:58:34 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M16507@lists.math.uh.edu Mon Jan 05 00:59:45 2009 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1LJcse-0002Cl-52 for ding-account@gmane.org; Mon, 05 Jan 2009 00:59:40 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1LJcr1-0001dg-ES; Sun, 04 Jan 2009 17:57:59 -0600 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1LJcqy-0001dC-DT for ding@lists.math.uh.edu; Sun, 04 Jan 2009 17:57:56 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtp (Exim 4.69) (envelope-from ) id 1LJcqv-0008RZ-Hw for ding@lists.math.uh.edu; Sun, 04 Jan 2009 17:57:56 -0600 Original-Received: from m61s02.vlinux.de ([83.151.21.164]) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1LJcrB-0000iE-00 for ; Mon, 05 Jan 2009 00:58:09 +0100 Original-Received: from dslc-082-082-171-221.pools.arcor-ip.net ([82.82.171.221] helo=void) by m61s02.vlinux.de with esmtpsa (TLS-1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.63) (envelope-from ) id 1LJcqw-00012q-Ex for ding@gnus.org; Mon, 05 Jan 2009 00:57:54 +0100 Mail-Copies-To: never Mail-Followup-To: ding@gnus.org In-Reply-To: (Lloyd Zusman's message of "Sun, 04 Jan 2009 17:30:07 -0500") User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (gnu/linux) X-Spam-Score: -1.0 (-) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:68062 Archived-At: Lloyd Zusman 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