[sylpheed:37241] Re: Manually grouping unthreaded messages

Steve O'Hara-Smith to Anton Shepelev:

> > Another solution is to forward the relevant preceding
> > e-mails to the new participant.  Sylpheed has two
> > context-menu items to automate this:
>
> I'm not sure that nested attachments is a better solution,
> but yes it is an option.

Nor need the context be provided as attachments -- the
/Forward/ command inserts all the selected messages as text
(see below).

> If you mean only when adding a new recipient

Yes.

> the discipline is tricky.

Yes, but my policy is to optimise for the reader at the
expense of the writer.

> You'd have to keep a folder for each thread or have some
> way of finding them all.

No, I simply select the messages upthread in the message
threaded view.

> Top post, full quote really is the easy way and a time
> honoured convention in corporate settings. It's easier to
> go with the flow.

This method is mechanically the simplest, and visually the
ugliest.

---------------- Forwarded Message -----------------
Date: Sat, 13 Jan 2024 09:21:25 -0800
From: Ben Hancock <[email protected]>
To: Sylpheed-List <[email protected]>
Newsgroups: gmane.mail.sylpheed.general
Subject: [sylpheed:37224] Manually grouping unthreaded messages


Hi Sylpheed users,

I sometimes receive messages from correspondents which have the same
subject line and are part of the same chain, but for whatever reason
(perhaps the other user's mail client configuration) are not treated as
belonging to the same thread by Sylpheed on my end. I have "Thread
View" enabled, and other messages are threading fine, so it does seem
that this is particular issue with only certain mails.

For easier viewing, I would like to link these messages so that they
belong to the same thread. Is there a way that I can manually do this?

Many thanks.

    - Ben



---------------- Forwarded Message -----------------
Date: Fri, 26 Jan 2024 11:33:35 +0300
From: Anton Shepelev <[email protected]>
To: [email protected]
Newsgroups: gmane.mail.sylpheed.general
Subject: [sylpheed:37227] Re: Manually grouping unthreaded messages


Ben Hancock:

> I sometimes receive messages from correspondents which
> have the same subject line and are part of the same chain,
> but for whatever reason (perhaps the other user's mail
> client configuration) are not treated as belonging to the
> same thread by Sylpheed on my end.

Yes, many modern e-mail clients break chaining, and no one
cares, because those clients are written for typical
corporate users who are accustomed to the default Outlook
configuation, in which outgoing and incoming mail is stored
in different folders so that no threading is possible at
all. To keep the context, the entire thread provided at the
bottom of each e-mail with headers and signatures eating up
a considerable portion of space and killing the signal-to-
noise ratio.

> I have "Thread View" enabled, and other messages are
> threading fine, so it does seem that this is particular
> issue with only certain mails.

Sylpheed, as any decent client, threads e-mails by the
References: header:

  https://jdebp.uk/Proposals/gnksoa-mua.html#Display

You can check whether the broken e-mails have that header
poining the the Message-Id: of the previous
e-mail -- pressing Ctrl+H will cause Sylpheed to display all
headers.

> For easier viewing, I would like to link these messages so
> that they belong to the same thread. Is there a way that I
> can manually do this?

No easy way that I know of, but I believe you can /manually/
edit a broken message, inserting the desired References:
header via a text editor.  Sylpheed conveniently stores
e-mails one per file on your HDD.

Apart from that -- complain about the problem in the user
community of the faulty e-mail client, contact their
support, and ask the correspondent to ditch the defective
software...




---------------- Forwarded Message -----------------
Date: Sat, 27 Jan 2024 15:24:34 +0000
From: Steve O'Hara-Smith <[email protected]>
To: [email protected]
Newsgroups: gmane.mail.sylpheed.general
Subject: [sylpheed:37231] Re: Manually grouping unthreaded messages


On Fri, 26 Jan 2024 11:33:35 +0300
Anton Shepelev <[email protected]> wrote:

> all. To keep the context, the entire thread provided at the
> bottom of each e-mail 

	There is good reason for this in corporate settings. It is not
unusual to find a thread appear in the inbox that has been running for
months gathering people, opinions, ideas, experiment results all along.
When there's no mailing list or USENET group the *only* place the context
can be found is in the ever growing email thread. It's a PITA reading it
from bottom to top when it arrives but after that you usually only have to
read the top bit.

	It's not great but in that setting it's the only thing that works.
Anyone who dives in with interleaved responses and trimming really messes
things up for newcomers by destroying the context.

-- 
Steve O'Hara-Smith <[email protected]>



---------------- Forwarded Message -----------------
Date: Mon, 29 Jan 2024 14:57:38 +0300
From: Anton Shepelev <[email protected]>
To: [email protected]
Newsgroups: gmane.mail.sylpheed.general
Subject: [sylpheed:37237] Re: Manually grouping unthreaded messages


Steve O'Hara-Smith:

> There is good reason for this in corporate settings. It is
> not unusual to find a thread appear in the inbox that has
> been running for months gathering people, opinions, ideas,
> experiment results all along.  When there's no mailing
> list or USENET group the *only* place the context can be
> found is in the ever growing email thread.

Another solution is to forward the relevant preceding
e-mails to the new participant.  Sylpheed has two context-
menu items to automate this:

1. Forward
2. Forward as attachment

> It's a PITA reading it from bottom to top when it arrives
> but after that you usually only have to read the top bit.

Yeah, plus the noise of repetivive headers and signatures,
and no convinient way to respond point-by-point.