Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Cc: Greg Troxel <gdt@lexort.com>,  Andrew Cohen <cohenandyg@gmail.com>
Subject: Re: Gnus sometimes fails to see a message that is actually in IMAP
Date: Fri, 24 May 2024 10:29:43 -0700	[thread overview]
Message-ID: <87le3z6rug.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87r0dr6w27.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Fri, 24 May 2024 08:58:40 -0700")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Greg Troxel <gdt@lexort.com> writes:
>>
>> Wow, this is a ton of information! Thanks for all the background. Kudos
>> on using TLS on your own machine, something I have never had the
>> patience to set up.
>>
>>> I have changed the subject, as I am not at all sure that my problem is
>>> the same as "reports new messages but not showing them on IMAP server".
>>> In my case, it seems to me as if there is a filter between gnus and the
>>> IMAP server that redacts a message.
>
> Brief update -- when I started looking further into this, I realized
> that I have the same issue with the INBOX of one of my main IMAP
> accounts. I'd just not noticed because I have 486 unread messages in
> that folder :( Well, 483 according to Gnus.
>
> This account includes a remote Dovecot on the server that actually
> receives mail, and two local machines that each have their own local
> Dovecot, and Emacs/Gnus. The remote and local Dovecots are synced with
> mbsync, and both remote and local report 486 unread messages when
> checked with doveadm.
>
> My other local machine is currently not booting, but I'll be very
> curious to see if Gnus on that machine is wrong in the same way
> (a deterministic bug) or not (space gremlins).
>
> Otherwise, the difference between "g" and "M-g", for IMAP servers that
> support qresync, is that "g" goes the qresync route:
>
> EXAMINE <group> (QRESYNC (<uidvalidity> <modseq>))
>
> while "M-g" does a full fetch of flags:
>
> "UID FETCH 1:* FLAGS"
>
> So that's a pretty strong indicator that there's a bug in the qresync
> branch of `nnimap-update-qresync-info'. Some have reported bugs that
> *weren't* resolved by "M-g", so there will likely be a few things to
> fix, but one thing at a time.

I'm currently looking with deep suspicion at the very beginning of that
function:

  ;; Add all the vanished articles to the list of read articles.
  (setf (gnus-info-read info)
        (range-add-list
         (range-add-list
          (range-concat (gnus-info-read info) vanished)
	  (cdr (assq '%Flagged flags)))
	 (cdr (assq '%Seen flags))))



  reply	other threads:[~2024-05-24 17:30 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12  0:57 Gnus sometimes reports new messages but not showing them on IMAP server Xiyue Deng
2024-04-17  0:03 ` Greg Troxel
2024-04-17  6:47   ` Xiyue Deng
2024-04-17 19:51 ` Dan Christensen
2024-04-18 12:13   ` Greg Troxel
2024-04-19 22:55     ` Dan Christensen
2024-04-21 12:08       ` Arash Esbati
2024-04-21 12:43         ` Dan Christensen
2024-04-21 13:14         ` Andreas Schwab
2024-04-21 16:18         ` Eric Abrahamsen
2024-04-21 18:16           ` Arash Esbati
2024-04-22  0:00             ` Greg Troxel
2024-04-22  2:35               ` Eric Abrahamsen
2024-04-27 19:46                 ` Xiyue Deng
2024-05-02  5:47                   ` Xiyue Deng
2024-05-02 15:08                     ` Eric Abrahamsen
2024-05-02 17:24                       ` Xiyue Deng
2024-05-02 17:41                         ` Dan Christensen
2024-05-02 18:41                           ` Xiyue Deng
2024-05-05 20:18                             ` Xiyue Deng
2024-05-05 21:01                               ` Dan Christensen
2024-05-05 22:10                                 ` Xiyue Deng
2024-05-08 18:36                                   ` Xiyue Deng
2024-05-08 18:41                                   ` Xiyue Deng
2024-05-09 23:11                                     ` Andrew Cohen
2024-05-10  7:45                                       ` Xiyue Deng
2024-05-10  8:16                                         ` Andrew Cohen
2024-05-10  8:26                                           ` Xiyue Deng
2024-05-10  9:13                                           ` Andreas Schwab
2024-05-10  0:43                   ` Greg Troxel
2024-05-10  1:20                     ` Xiyue Deng
2024-05-10 12:24                       ` Greg Troxel
2024-05-10 20:06                         ` Xiyue Deng
2024-05-11 19:08                           ` Greg Troxel
2024-05-11 22:33                             ` Eric Abrahamsen
2024-05-12 11:14                               ` Gnus sometimes fails to see a message that is actually in IMAP Greg Troxel
2024-05-13 14:39                                 ` Eric Abrahamsen
2024-05-24 15:58                                   ` Eric Abrahamsen
2024-05-24 17:29                                     ` Eric Abrahamsen [this message]
2024-04-24 15:23           ` Gnus sometimes reports new messages but not showing them on IMAP server James Thomas
2024-04-25  2:59             ` Eric Abrahamsen

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=87le3z6rug.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=cohenandyg@gmail.com \
    --cc=ding@gnus.org \
    --cc=gdt@lexort.com \
    /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).