From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-devel@gnu.org
Subject: Re: Synchronize Gnus and IMAP's notion of read mail
Date: Sat, 22 Jun 2024 09:59:02 +0300 [thread overview]
Message-ID: <86cyo9jweh.fsf@gnu.org> (raw)
In-Reply-To: <jwvle2yypaf.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 21 Jun 2024 17:21:38 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Fri, 21 Jun 2024 17:21:38 -0400
>
> Apparently there's a bug in Gnus which causes it to sometimes fail to
> tell IMAP that some messages are "read" (or maybe it causes some messages
> to be re-set to "unread"? I don't know).
>
> In any case, what I do know is that what my IMAP server considers as
> "read" is not the same as what Gnus thinks, even though I basically
> never access my IMAP server via anything else than Gnus.
>
> I have not yet figured out how/why this happens, but instead I'm
> wondering how I can fix the consequence of the bug by re-synchronize
> Gnus with IMAP.
>
> I know how to get Gnus to forget its own notion of "read" and (re)fetch
> all that info from IMAP. But I'd like to do the reverse: have Gnus tell
> IMAP which messages should be considered "read" and which not (of
> course, being careful not to affect those messages which Gnus hasn't
> seen yet).
> E.g. something like have Gnus go through all the messages that IMAP say
> are "unread" and mark them (in IMAP) as "read" if Gnus thinks they've
> already been "read".
>
> How can I do that?
Eric, can you help Stefan?
next prev parent reply other threads:[~2024-06-22 6:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 21:21 Synchronize Gnus and IMAP's notion of read mail Stefan Monnier
2024-06-22 6:59 ` Eli Zaretskii [this message]
2024-06-22 10:59 ` Andrew Cohen
2024-06-23 0:04 ` Björn Bidar
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86cyo9jweh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).