From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/68058 Path: news.gmane.org!not-for-mail From: Lloyd Zusman Newsgroups: gmane.emacs.gnus.general Subject: Re: Automatically marking Gcc's as SEEN in nnimap Date: Sun, 04 Jan 2009 17:30:07 -0500 Organization: Take a hippopotamus to lunch today. Message-ID: 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 1231108237 2155 80.91.229.12 (4 Jan 2009 22:30:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 4 Jan 2009 22:30:37 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M16504@lists.math.uh.edu Sun Jan 04 23:31:48 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 1LJbVU-0004XZ-JA for ding-account@gmane.org; Sun, 04 Jan 2009 23:31: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 1LJbUE-0001A0-DK; Sun, 04 Jan 2009 16:30:22 -0600 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1LJbUC-00019e-SU for ding@lists.math.uh.edu; Sun, 04 Jan 2009 16:30:20 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtp (Exim 4.69) (envelope-from ) id 1LJbUA-0005PQ-Ez for ding@lists.math.uh.edu; Sun, 04 Jan 2009 16:30:20 -0600 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1LJbUQ-0007oI-00 for ; Sun, 04 Jan 2009 23:30:34 +0100 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LJbU8-0000LS-CJ for ding@gnus.org; Sun, 04 Jan 2009 22:30:16 +0000 Original-Received: from 209.59.210.144 ([209.59.210.144]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 04 Jan 2009 22:30:16 +0000 Original-Received: from ljz by 209.59.210.144 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 04 Jan 2009 22:30:16 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 89 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 209.59.210.144 User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (darwin) Cancel-Lock: sha1:92bfNai3BBZJxBOPhQGuvLai0uQ= Cache-Post-Path: purity-of-essence.net!unknown@nadie.us X-Cache: nntpcache 3.0.2 (see http://www.nntpcache.com/) X-Spam-Score: -1.4 (-) List-ID: Precedence: bulk X-Spam-Report: 5.7 points; * 1.7 SUBJ_AS_SEEN Subject contains "As Seen" * 0.0 RCVD_BY_IP Received by mail server with no name * 4.0 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO Xref: news.gmane.org gmane.emacs.gnus.general:68058 Archived-At: David Engster writes: > Lloyd Zusman writes: >> >> [ ... ] >> > Thanks for testing. If no one objects, I'll commit this patch. Well, I certainly don't object! :) Thanks. >> There's another related issue, however. When I do a >> `gnus-group-catchup-current' on any nnimap-based group that is accessed >> via my primary server, none of the un-SEEN articles get marked as SEEN. >> This works fine for my nnimap-based groups accessed through one of my >> secondary servers. >> >> [ ... ] > > 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. 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. This only occurs for my primary nnimap back end. For the secondaries, the same sort of stuff gets written into *imap-log* (see below), but the unread/unseen mark doesn't return after `gnus-group-get-new-news'. Here's what got stored during `gnus-group-catchup-current' on a secondary nnimap group: 1780 NOOP 1780 OK NOOP completed. 1781 UID STORE 1874 +FLAGS (\Seen) * 37 FETCH (UID 1874 FLAGS (\Seen)) 1781 OK Store completed. 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'? That's just a shot in the dark, however. > If not, eval the following > > (add-hook 'gnus-group-catchup-group-hook > (lambda () (message "catch up: %s" gnus-newsgroup-name))) > > and look at the group name in the message buffer after you have catched > up. For groups from the primary back end, you should just see the group > name without any prefix like "nnimap+SERVER:". 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. -- Lloyd Zusman ljz@asfast.com God bless you.