[Mailman-Developers] Hyperkitty's ability to build a thread

[Stephen J. Turnbull]

Danil Smirnov writes:

 > As per my small investigation, a subscriber Robert N. Evans seems to have
 > "In-Reply-To" headers stripped from the messages that probably causes the
 > thread to break.
 > 
 > I wonder if Hyperkitty is able to leverage some other method to combine the
 > thread correctly in this case?

It's simply not possible to guarantee correct threading if neither
References nor In-Reply-To are present.

It is possible to place a message in an approximately appropriate
place by threading the threadable messages, grouping that message with
threads with "the same" subject, and inserting it (and any
descendants) after some message with an earlier date, but this is
inherently ambiguous as that message could be a reply to *any* such
message with an earlier date.

This would work well if there is a single linear thread.  But it is
unlikely to work at all well if several posters replied to a single
message in the recent past so that there are multiple subthreads
active at a given time.

Gmail has a big advantage, since they're reading your mail, indexing
it, and creating a fine-grained statistical profile.  That database
can probably be leveraged for better threading.  Or if your posters
consistently top-post, it's probably not too hard to match quoted
content against the top-level content of an earlier post -- if you
have both the development and the computational resources of Google.
(Come to think of it, for Gmail this would probably allow them to
compress their storage by 50%.)  Or maybe they just got lucky.

Steve
___
Mailman-Developers mailing list -- mailman-developers@python.org
To unsubscribe send an email to mailman-developers-le...@python.org
https://mail.python.org/mailman3/lists/mailman-developers.python.org/
Mailman FAQ: https://wiki.list.org/x/AgA3

Security Policy: https://wiki.list.org/x/QIA9

[Mailman-Developers] Hyperkitty's ability to build a thread

[Danil Smirnov]

Hi everyone and Abhilash in particular :)

I've faced a case when Hypirkitty is unable to chain messages into a thread:
https://wlug.mailman3.com/hyperkitty/list/w...@lists.wlug.org/

(See messages with the subject "WLUG Meeting Feb 11th 2021! Topic: Good
question!".)

It's a quite disappointment as GMail does show them correctly - as a
single thread.

As per my small investigation, a subscriber Robert N. Evans seems to have
"In-Reply-To" headers stripped from the messages that probably causes the
thread to break.

I wonder if Hyperkitty is able to leverage some other method to combine the
thread correctly in this case?

"Good" and "bad" message examples are in the attachment.

Best regards,
Danil Smirnov
--- Begin Message ---
John Stoffel via WLUG  writes:

> I recall, it's mostly the memory ordering around byte accesses that
> are the problem.  

Are you saying that the Big Endian vs Little Endian flame war
actually had consequences in the Real World?

Or something even more obscure?

   -- Keith
___
WLUG mailing list -- w...@lists.wlug.org
To unsubscribe send an email to wlug-le...@lists.wlug.org
Create Account: https://wlug.mailman3.com/accounts/signup/
Change Settings: https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/
Web Forum/Archive: 
https://wlug.mailman3.com/hyperkitty/list/w...@lists.wlug.org/message/3LQYE4JHDJ7YLZX6EST7S4D4Z3KXGE3T/
--- End Message ---
--- Begin Message ---
That is not what I see when I query one of the major name servers.  I would 
guess your server is configured differently...

rne@P5:~$ dig @1.1.1.1 isc.org

; <<>> DiG 9.16.1-Ubuntu <<>> @1.1.1.1 isc.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31866
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;isc.org.   IN  A

;; ANSWER SECTION:
isc.org.9   IN  A   149.20.1.66

;; Query time: 24 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Thu Feb 11 10:03:30 EST 2021
;; MSG SIZE  rcvd: 52


-BE

-Original Message-
>From: Keith Wright via WLUG 
>Sent: Feb 11, 2021 1:04 AM
>To: Worcester Linux Users' Group General Discussion 
>Cc: w...@lists.wlug.org, andre.lehov...@gmx.com, Keith Wright 
>
>Subject: [WLUG] Re: WLUG Meeting Feb 11th 2021! Topic: Good question!
>
>Andre Lehovich via WLUG  writes:
>
>>> dig @66.92.74.188 isc.org
>> 
>> Here you go, hope it's useful...
>
>Thank you.  That's a lot of information.
>
>> quetzal:~ al$ dig @66.92.74.188 isc.org
>> 
>> ; <<>> DiG 9.10.6 <<>> @66.92.74.188 isc.org
>> ; (1 server found)
>> ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11995
>> ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 27
>> ;; WARNING: recursion requested but not available
>  ^ ^ ^^^ ^^^ ^   
>That looks good.
>I don't want to be doing recursion for you (nothing personal).
>
>But where did all the rest of that come from?
>I've never seen anything like that!
>Did my server send all that?  Why??
>
>> ;; OPT PSEUDOSECTION:
>> ; EDNS: version: 0, flags:; udp: 4096
>> ;; QUESTION SECTION:
>> ;isc.org.INA
>> 
>> ;; AUTHORITY SECTION:
>> .348191INNSc.root-servers.net.
>> .348191INNSd.root-servers.net.
>> .348191INNSe.root-servers.net.
>> .348191INNSf.root-servers.net.
>> .348191INNSg.root-servers.net.
>> .348191INNSh.root-servers.net.
>> .348191INNSi.root-servers.net.
>> .348191INNSj.root-servers.net.
>> .348191INNSk.root-servers.net.
>> .348191INNSl.root-servers.net.
>> .348191INNSm.root-servers.net.
>> .348191INNSa.root-servers.net.
>> .348191INNSb.root-servers.net.
>> 
>> ;; ADDITIONAL SECTION:
>> a.root-servers.net.348191INA198.41.0.4
>> a.root-servers.net.348191IN2001:503:ba3e::2:30
>> b.root-servers.net.348191INA199.9.14.201
>> b.root-servers.net.348191IN2001:500:200::b
>> c.root-servers.net.348191INA192.33.4.12
>> c.root-servers.net.348191IN2001:500:2::c
>> d.root-servers.net.348191INA199.7.91.13
>> d.root-servers.net.348191IN2001:500:2d::d
>> e.root-servers.net.348191INA192.203.230.10
>> e.root-servers.net.348191IN2001:500:a8::e
>> f.root-servers.net.348191INA192.5.5.241
>> f.root-servers.net.348191IN2001:500:2f::f
>> g.root-servers.net.348191INA192.112.36.4
>>