[Users] Problem with sorting method inside threads with same Subject

[Slavko]

Ahoj,

Dňa Wed, 30 Sep 2015 19:40:01 +0100 Augustin Doury
<augustindoury at gmail.com> napísal:

> Hi,
> 
> Thanks for your quick answer.
> 
> 1) As you can see on this mailing list, I used a subject because it
> was useful. If sometimes I do not use a subject, I have my reasons
> and they are good for me, If you think about it, I'm sure you will
> find some good reasons for, sometimes, avoid a subject. So please no
> advice on good manners or etiquette :)

I love mails without subject, they are quickly solved by me - with the
DEL key ;-)

> 2) I expect a mail client which answer my need, I'm not going to put a
> subject where I did not put a subject before, just because Clawsmail
> need it to sort emails. I'v never seen a webmail or a mail client
> which absolutely need a subject to manage the threads.
> Thank you for the idea of using label/tags but I feel like it's too
> much work for me just to have my emails sorted, it should be native.

Your expectations are wrong. Try read the RFC about mail headers and
about relations between emails.

> 4) When I create a thread, I just write a new message and send it to
> somebody. I thought also that each thread has a thread number, but it
> does not seem to be used by clawsmail to sort emails (that's why I
> wrote that my emails were sorted just "by date/subject"). The problem
> is the same for sorting my old "no subject" emails, sent from my
> webmail in the past.

You cannot create thread, you can send message only, which is not
related to others. Thread is created by the first reply with relation,
but some clients doesn't properly sets the appropriate headers, then
there is threading by subject as addition.

regards

-- 
Slavko
http://slavino.sk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 455 bytes
Desc: Digitálny podpis OpenPGP
URL: <http://lists.claws-mail.org/pipermail/users/attachments/20150930/97e693a4/attachment.sig>