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 <w...@lists.wlug.org> 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 <w...@lists.wlug.org>
>Sent: Feb 11, 2021 1:04 AM
>To: Worcester Linux Users' Group General Discussion <w...@lists.wlug.org>
>Cc: w...@lists.wlug.org, andre.lehov...@gmx.com, Keith Wright 
><kwri...@keithdiane.us>
>Subject: [WLUG] Re: WLUG Meeting Feb 11th 2021! Topic: Good question!
>
>Andre Lehovich via WLUG <w...@lists.wlug.org> 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.            IN    A
>> 
>> ;; AUTHORITY SECTION:
>> .            348191    IN    NS    c.root-servers.net.
>> .            348191    IN    NS    d.root-servers.net.
>> .            348191    IN    NS    e.root-servers.net.
>> .            348191    IN    NS    f.root-servers.net.
>> .            348191    IN    NS    g.root-servers.net.
>> .            348191    IN    NS    h.root-servers.net.
>> .            348191    IN    NS    i.root-servers.net.
>> .            348191    IN    NS    j.root-servers.net.
>> .            348191    IN    NS    k.root-servers.net.
>> .            348191    IN    NS    l.root-servers.net.
>> .            348191    IN    NS    m.root-servers.net.
>> .            348191    IN    NS    a.root-servers.net.
>> .            348191    IN    NS    b.root-servers.net.
>> 
>> ;; ADDITIONAL SECTION:
>> a.root-servers.net.    348191    IN    A    198.41.0.4
>> a.root-servers.net.    348191    IN    AAAA    2001:503:ba3e::2:30
>> b.root-servers.net.    348191    IN    A    199.9.14.201
>> b.root-servers.net.    348191    IN    AAAA    2001:500:200::b
>> c.root-servers.net.    348191    IN    A    192.33.4.12
>> c.root-servers.net.    348191    IN    AAAA    2001:500:2::c
>> d.root-servers.net.    348191    IN    A    199.7.91.13
>> d.root-servers.net.    348191    IN    AAAA    2001:500:2d::d
>> e.root-servers.net.    348191    IN    A    192.203.230.10
>> e.root-servers.net.    348191    IN    AAAA    2001:500:a8::e
>> f.root-servers.net.    348191    IN    A    192.5.5.241
>> f.root-servers.net.    348191    IN    AAAA    2001:500:2f::f
>> g.root-servers.net.    348191    IN    A    192.112.36.4
>> g.root-servers.net.    348191    IN    AAAA    2001:500:12::d0d
>> h.root-servers.net.    348191    IN    A    198.97.190.53
>> h.root-servers.net.    348191    IN    AAAA    2001:500:1::53
>> i.root-servers.net.    348191    IN    A    192.36.148.17
>> i.root-servers.net.    348191    IN    AAAA    2001:7fe::53
>> j.root-servers.net.    348191    IN    A    192.58.128.30
>> j.root-servers.net.    348191    IN    AAAA    2001:503:c27::2:30
>> k.root-servers.net.    348191    IN    A    193.0.14.129
>> k.root-servers.net.    348191    IN    AAAA    2001:7fd::1
>> l.root-servers.net.    348191    IN    A    199.7.83.42
>> l.root-servers.net.    348191    IN    AAAA    2001:500:9f::42
>> m.root-servers.net.    348191    IN    A    202.12.27.33
>> m.root-servers.net.    348191    IN    AAAA    2001:dc3::35
>> 
>> ;; Query time: 150 msec
>> ;; SERVER: 66.92.74.188#53(66.92.74.188)
>> ;; WHEN: Wed Feb 10 20:31:08 PST 2021
>> ;; MSG SIZE  rcvd: 819
>> 
>> _______________________________________________
>> 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/JBBKO54Y5NDAMFRLJ5WWJAPB7HCZ7SYL/
>_______________________________________________
>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/2A6P2GSW4TSW7CL6QYYUCQTX42LBZZIA/
_______________________________________________
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/5IPNKATQRHXQRZM4R3ATEUL6WNSLYUL7/

--- End Message ---
_______________________________________________
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

Reply via email to