From: Lloyd Zusman <ljz@asfast.com>
To: ding@gnus.org
Subject: Re: Automatically marking Gcc's as SEEN in nnimap
Date: Sun, 04 Jan 2009 15:14:36 -0500 [thread overview]
Message-ID: <m2tz8eygk3.fsf@asfast.com> (raw)
In-Reply-To: <87mye8t1zr.fsf@engster.org>
David Engster <deng@randomsample.de> writes:
> Lloyd Zusman <ljz@asfast.com> writes:
>>
>> [ ... ]
>>
> 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?
>
> [ ... etc. ... ]
Yes, this does indeed work. Thank you!
>> 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. [ ... etc. ... ]
I'm sorry, but I misreported that Gcc's weren't being marked as SEEN for
the secondaries. They are indeed being marked correctly. The test that I
run on a "secondary" before writing that earlier message was actually
being incorrectly performed on a primary group.
So all is well now with the primaries and secondaries w/r/t Gcc.
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.
Any thoughts?
Thanks again for all your help.
--
Lloyd Zusman
ljz@asfast.com
God bless you.
next prev parent reply other threads:[~2009-01-04 20:14 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
2009-01-04 20:14 ` Lloyd Zusman [this message]
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=m2tz8eygk3.fsf@asfast.com \
--to=ljz@asfast.com \
--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).