Gnus development mailing list
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: Automatically marking Gcc's as SEEN in nnimap
Date: Sun, 04 Jan 2009 00:15:52 +0100	[thread overview]
Message-ID: <87mye8t1zr.fsf@engster.org> (raw)
In-Reply-To: <m2ocyo16sm.fsf@asfast.com>

[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]

Lloyd Zusman <ljz@asfast.com> writes:
> David Engster <deng@randomsample.de> writes:
>
>> Lloyd Zusman <ljz@asfast.com> writes:
>>>
>>> [ ... ]
>>>
>>> Does anyone have any thoughts about this? Is there a way to get messages
>>> that are marked as "read" in nnimap to also get marked as "seen" on the
>>> IMAP server?
>>
>> Do you use nnimap as your primary select method? If so, manually edit
>> your GCC header
>>
>>   Gcc: nnimap+imap.server.tld:INBOX.archive.whatever
>>
>> so that it just reads
>>
>>   Gcc: INBOX.archive.whatever
>>
>> Does it work now?
>>
>> -David
>
> Aha! Well, I have three nnimap select methods: one as my primary, and
> two others which are secondary. When I refer to archives on the primary
> server in the way you describe above, they are now indeed getting marked
> as SEEN at the same time they're getting marked as "read".

It seems there is a bug in gnus-msg.el when the gcc is going to the
primary back end. Without changing the GCC manually, does the following
patch fix this for you?


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: gnus-msg-patch.diff --]
[-- Type: text/x-diff, Size: 487 bytes --]

diff --git a/lisp/gnus-msg.el b/lisp/gnus-msg.el
index 555b6a0..ce6fd3d 100644
--- a/lisp/gnus-msg.el
+++ b/lisp/gnus-msg.el
@@ -1624,6 +1624,8 @@ this is a reply."
 		  group (mm-encode-coding-string
 			 group
 			 (gnus-group-name-charset method group)))
+	    (when (gnus-native-method-p method)
+	      (setq group (gnus-group-short-name group)))
 	    (unless (gnus-check-server method)
 	      (error "Can't open server %s" (if (stringp method) method
 					      (car method))))

[-- Attachment #3: Type: text/plain, Size: 498 bytes --]


> However, what can I do about the secondaries? Anything?

Secondary or foreign servers should work if you give a fully qualified
group name; at least it works for me with a nnimap server in the
secondary select methods. Also, 'read' marks in Gnus should directly
correspond to the SEEN flags on the IMAP server. If you activate the
IMAP logging, you should see stuff like

595 UID STORE 2987 +FLAGS (\Seen)

when you mark message as read (and -FLAGS if you remove the marks on a
message)

-David

  reply	other threads:[~2009-01-03 23:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17  2:29 Lloyd Zusman
2008-12-17  9:45 ` Paul R
2008-12-18  0:57   ` Lloyd Zusman
2008-12-18  2:22     ` Dave Goldberg
2008-12-18  3:20       ` Lloyd Zusman
2008-12-26 19:27         ` Lloyd Zusman
2009-01-03 17:21           ` David Engster
2009-01-03 20:19             ` Lloyd Zusman
2009-01-03 23:15               ` David Engster [this message]
2009-01-04 20:14                 ` Lloyd Zusman
2009-01-04 21:21                   ` David Engster
2009-01-04 22:30                     ` Lloyd Zusman
2009-01-04 23:57                       ` David Engster
2009-01-05  1:40                         ` Lloyd Zusman
2009-01-05 11:25                           ` David Engster
2009-01-06  2:32                             ` Lloyd Zusman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mye8t1zr.fsf@engster.org \
    --to=deng@randomsample.de \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).