Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Bob Newell <bobnewell@bobnewell.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: info-gnus-english@gnu.org
Subject: Re: Does Gnus read and sync the read with IMAP?
Date: Thu, 19 Oct 2023 16:58:37 -1000	[thread overview]
Message-ID: <87edhq80f6.qtuqpnw@ymvf.vhkf.net> (raw)
In-Reply-To: <87sf66m7pn.fsf@web.de> (Michael Heerdegen's message of "Fri, 20 Oct 2023 02:57:24 +0200")


Michael Heerdegen <michael_heerdegen@web.de> writes:

> Bob Newell <bobnewell@bobnewell.net> writes:
>
>> The thing is, your /client/ may show them as read but may or may not
>> have uploaded that "being read" information to the IMAP server.  Do
>> try deliberately closing the client on your phone and see if it helps.
>> You have to be sure (at least on Android) to actually exit the client
>> and not just switch to another app.
>
> Does Gnus update the "being read" information from the server also for
> messages it already knows (i.e., has seen in a prior session)?

This goes well beyond my very limited knowledge so I did an
experiment.  I went to the gmail web interface and found an
already-opened message in the All Mail folder (really a label)
that I knew for certain I had originally opened in gnus, so
therefore gnus would have known about the message.  I marked
it unread (on the web) and moved it back to INBOX.

Then I started up gnus and gnus saw the message as an unread
INBOX message.  Based on this it appears the answer is yes,
gnus did update the status of this previously seen email.
However I don't know how much if any status information gnus
actually keeps (and I don't use the registry) so this may or
may not be meaningless.  It certainly seems as if, when
reopening the group subsequent to shutting down gnus at some
point, gnus gets a fresh set of information.

-- 
Bob Newell
Honolulu, Hawai`i

- Via GNU/Linux/Emacs/Gnus/BBDB


  reply	other threads:[~2023-10-20  2:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <65316d26.050a0220.cf46d.a86aSMTPIN_ADDED_BROKEN@mx.google.com>
2023-10-19 20:10 ` Bob Newell
2023-10-19 22:06   ` Björn Bidar
     [not found]   ` <6531aa57.050a0220.a965a.55e5SMTPIN_ADDED_BROKEN@mx.google.com>
2023-10-19 22:45     ` Bob Newell
2023-10-20  0:57       ` Michael Heerdegen
2023-10-20  2:58         ` Bob Newell [this message]
2023-10-20  4:26           ` Michael Heerdegen
2023-10-20 14:04             ` Eric Abrahamsen
2023-10-20 19:09               ` Bob Newell
2023-10-20 19:28                 ` Bob Newell
2023-10-20 21:18                   ` Björn Bidar
2023-10-20 20:14                 ` Adam Sjøgren
2023-10-22 22:29             ` James Thomas
2023-11-05 22:31             ` Adam Sjøgren
2023-10-20 13:12       ` Björn Bidar
     [not found] <20416.4865355537$1697735647@news.gmane.org>
2023-10-20 13:28 ` Dan Christensen
2023-10-20 14:11   ` Eric Abrahamsen
2023-10-20 15:36     ` Dan Christensen
2023-10-20 21:23       ` Björn Bidar
     [not found]       ` <48102.5036818878$1697837027@news.gmane.org>
2023-10-20 22:46         ` Eric Abrahamsen
2023-10-19 17:13 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

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

  git send-email \
    --in-reply-to=87edhq80f6.qtuqpnw@ymvf.vhkf.net \
    --to=bobnewell@bobnewell.net \
    --cc=info-gnus-english@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).