Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Bob Newell <bobnewell@bobnewell.net>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: info-gnus-english@gnu.org
Subject: Re: Does Gnus read and sync the read with IMAP?
Date: Thu, 19 Oct 2023 12:45:16 -1000	[thread overview]
Message-ID: <CAP7oW5L769O45Ga+6stEEX20rLKF0OGGPsVtqpMv+zspHuWkzg@mail.gmail.com> (raw)
In-Reply-To: <6531aa57.050a0220.a965a.55e5SMTPIN_ADDED_BROKEN@mx.google.com>

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

On Thu, Oct 19, 2023 at 12:14 PM Björn Bidar <bjorn.bidar@thaodan.de> wrote:

> Bob Newell <bobnewell@bobnewell.net> writes:
>
> >> I noticed that when I read a mail on my phone the read statusis
> >> still unread when I fetch my mails from my imap server is still
> >> unread in
> >> Gnus.
> >> How can I make Gnus to fetch the read status from Imap?
> >
> > This could depend on your email client on your phone.  At what
> > point does it sync back to the IMAP server to say that you've
> > read the mail?  When the client closes?  At certain intervals?
> > You might try closing the client and see if that helps.
>
> The mails that were marked as new in Gnus were in the cur folder of the
> imap folder there were from so yes my email client marked them as read.
>

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.

I closed the client in between I think. I will look how Gnus marks them
> as read on my imap server.
>


-- 
Bob Newell
Honolulu, Hawai`i

[-- Attachment #2: Type: text/html, Size: 2233 bytes --]

  parent reply	other threads:[~2023-10-19 22:45 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 [this message]
2023-10-20  0:57       ` Michael Heerdegen
2023-10-20  2:58         ` Bob Newell
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=CAP7oW5L769O45Ga+6stEEX20rLKF0OGGPsVtqpMv+zspHuWkzg@mail.gmail.com \
    --to=bobnewell@bobnewell.net \
    --cc=bjorn.bidar@thaodan.de \
    --cc=info-gnus-english@gnu.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).