bug#70054: 30.0.50; Unknown ids in References: break threading

[Eric Abrahamsen]

Jose A Ortega Ruiz <jao@gnu.org> writes:

> On Sun, Apr 21 2024, Eric Abrahamsen wrote:
>
> [...]
>
>>>> Eric, any comments?
>>
>> This certainly does sound like a bug. This is a pretty complex part of
>> Gnus, and it might take a while to track down. Jose, can you tell me
>> your value of `gnus-build-sparse-threads'? I would think that, if Gnus
>> *isn't* trying to build sparse threads, these unknown Message-IDs would
>> simply be treated like messages that haven't been loaded into the
>> Summary buffer, and ignored. Can you tell me your current value for that
>> variable, and also if/how changing the value (particularly between 'more
>> and 't) changes the behavior here?
>
> Currently, I've got it set to nil. Setting it to t seems to almost
> totally break the listing: there's some threading but it's displayed as
> every single message being indented respect to the previous one most of
> the time (i know from displaying those threads using notmuch that that's
> not the case at all), and most messages have wrong dates and are marked
> as cancelled or deleted when i try to access them the usual way
> (e.g. with RET in the summary buffer). Maybe there's some conflict with
> something cached, but it really seems to break hell loose :)

Gruesome! I experimented with nnmaildir in gnus-mock, adding spurious
message-ids to the References header, and nothing happened; they were
just ignored.

You mentioned the Proton bridge, I assume that's nnimap from Gnus' point
of view? I tried the same, editing a message in Dovecot's maildir store,
but it really didn't like that -- every time I tried to enter the group
the imap process died.

Can you tell me a little more about how you're accessing these messages,
inside Gnus?

Thanks,
Eric