unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: 35443@debbugs.gnu.org
Subject: bug#35443: 27.0.50; Gnus (nnimap) shows "ghost" messages in summary buffer
Date: Thu, 09 May 2019 10:27:07 -0700	[thread overview]
Message-ID: <871s1735ec.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87lfztiqu3.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sun, 28 Apr 2019 17:43:16 -0700")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

--8<---------------cut here---------------start------------->8---
> Ulrich Mueller <ulm@gentoo.org> writes:
>
>>>>>>> On Sat, 27 Apr 2019, Eric Abrahamsen wrote:
>>
>>> Huh. Can you show us the value of gnus-newsgroup-data and
>>> gnus-newsgroup-headers in this group?
>>
>> See below, for the current group, whose summary buffer shows your
>> article and a dummy article.
>>
>>> Does the dummy article always show up?
>>
>> It always shows up when new articles have been fetched. It doesn't
>> show up when entering a group that doesn't have new mail (i.e., if a
>> group previously had a dummy article, it will be gone when reentering
>> that group).
>>
>>> Only in this group?
>>
>> All groups for that particular IMAP server.
>>
>>> Is this a newly-added IMAP server, and did it display this problem
>>> right from the beginning?
>>
>> AFAICS, the problem appeared after dovecot on the server side was
>> upgraded from version 2.2.34 to 2.3.5.1. But I see it only with Gnus.
>> I don't have any issues with Mozilla Thunderbird (on GNU/Linux) nor with
>> K-9 Mail (on Android/Linux).
>
> Thanks, this should be enough to make some progress in tracking the
> problem down. Give me a couple of days...

Okay, here's what I was told on irc:

--8<---------------cut here---------------start------------->8---
<tss> looks like it's the new feature that adds $HasAttachment or
      $HasNoAttachment flags to mails. they're actually supposed to be added
      only during mail delivery, and there's a setting needed to enable them:
      mail_attachment_detection_options = add-flags-on-save
<tss> but .. there's an "unintentional feature" :) that they also get added
      during some FETCH commands if they're not already there
<tss> but even without this, imap protocol allows sending FETCH FLAGS updates
      (or any updates really) as a response to any command. and with
      concurrent imap access dovecot does this.
<tss> for example if another client adds a \Seen flag, that same thing could
      happen
<jkt> either way, a client should really be able to process these
      "unexpeceted" FETCH updates, that's what the standard is about
--8<---------------cut here---------------end--------------->8---

Ultimately, the "real" fix would be to teach Gnus to handle all possible
responses from IMAP servers, probably using a proper parser.

But if you have access to the dovecot config in your case, you might try
removing the mail_attachment_detection_options setting above, if it's
set. If it's not set, then you might be getting the "unintentional
feature".

I suppose in the interim I could mess with `nnimap-transform-headers'
and try to add some bookkeeping so that multiple FETCH responses for the
same article UID get merged together. On the other hand, this feature
only seems to relate to has/hasnoattachment flags, which Gnus doesn't
handle anyway -- we could safely drop those lines altogether.

(Though it sure would be nice to handle hasattachment flags, that's
something that users have requested in the past...)

Well, that's where we're at.

Eric





  reply	other threads:[~2019-05-09 17:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-27  6:23 bug#35443: 27.0.50; Gnus (nnimap) shows "ghost" messages in summary buffer Ulrich Mueller
2019-04-27 15:03 ` Eric Abrahamsen
2019-04-27 15:49   ` Ulrich Mueller
2019-04-27 20:47     ` Eric Abrahamsen
2019-04-28  3:53       ` Ulrich Mueller
2019-04-29  0:43         ` Eric Abrahamsen
2019-05-09 17:27           ` Eric Abrahamsen [this message]
2019-05-09 19:03             ` Ulrich Mueller
2019-05-09 20:15               ` Eric Abrahamsen
2019-06-22 12:26                 ` Lars Ingebrigtsen
2019-06-22 16:27                   ` Eric Abrahamsen
2019-06-23 12:13                     ` Lars Ingebrigtsen
2019-06-23 16:55                       ` Eric Abrahamsen
2019-06-23 16:58                         ` Lars Ingebrigtsen
2019-06-23 17:23                           ` Eric Abrahamsen
2019-06-22 21:36                   ` Eric Abrahamsen
2019-06-23 12:23                     ` Lars Ingebrigtsen
2019-07-11 17:38                       ` Eric Abrahamsen
2019-07-11 20:28                         ` Eric Abrahamsen
2019-07-12 14:18                           ` Lars Ingebrigtsen
2019-07-12 16:50                             ` Eric Abrahamsen
2019-07-12 16:58                               ` Eric Abrahamsen
2019-07-14 16:19                               ` Eric Abrahamsen
2019-07-12 15:02                         ` Lars Ingebrigtsen
2019-07-15 17:45                           ` Eric Abrahamsen
2019-07-15 18:16                             ` Lars Ingebrigtsen
2019-05-07 21:14         ` Eric Abrahamsen
2019-05-08  7:07           ` Ulrich Mueller
2019-05-07 20:34 ` Eric Abrahamsen
2019-05-08 15:18   ` Ulrich Mueller

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=871s1735ec.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=35443@debbugs.gnu.org \
    --cc=ulm@gentoo.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.
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).