Re: Occasional threading related need

Peter Bloomfield <[email protected]> Thu, 27 Feb 2020 20:49:59 -0500
Newsgroups gmane.comp.gnome.apps.balsa
Message-ID <[email protected]>
Hi Jack,

Have you tried Mailbox:Properties:Merge threads with the same subject? It enables the subject-merge phase of JWZ threading.

The option is a little misleading; if there's a message with a given subject "stuff", any message with subject "Re: stuff" is threaded beneath it. But other messages with subject "stuff" are not. At least, that's the way I read the code :-)

Peter

On 02/27/2020 06:55:34 PM Thu, Jack via balsa-list wrote:
> Hello everyone,
> 
> Not surprisingly, I'm on several mailing lists, and because of the variety of email software out there, I often get a reply to a previous message, which does not thread.   The last few I've looked at turned out to be that way because the person replied to a digest.  He did a great job of editing down to only what he was replying to - but obviously the References: and In-reply-to: headers referenced the digest email, not the actual message he was replying to.
> 
> In the past, I have actually manually edited the email file to insert appropriate References: and In-reply-to: headers, but that is obviously subject to error.  Oddly, if I look at the list archives, all messages are correctly threaded.
> 
> Has anyone else noticed this, and are there any ideas on getting the threading "correct" in Balsa?  I don't think Balsa is doing anything wrong, I think the proper headers are not present, although the mailing list (pipermail, in this case?) seems to recognize the "References:" header as the digest, and so perhaps just threads by Subject?
> 
> Thanks for any suggestions.
> 
> Jack
> _______________________________________________
> balsa-list mailing list
> [email protected]
> https://mail.gnome.org/mailman/listinfo/balsa-list

_______________________________________________
balsa-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/balsa-list
signature.asc (application/pgp-signature, 195 B)
-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQS030wPRfNNA5alz3MfX9S1uSp09QUCXlhxxwAKCRAfX9S1uSp0
9VpxAJwPLQ7mCU1PwQw/Z1odHADq3NsHYgCfeo9eq1m51GrklEgNln7vYWb3guM=
=rBWC
-----END PGP SIGNATURE-----