Am 26.01.2010 um 18:03 schrieb Tim Gray:
Or make it default to remove the header when you change the
subject. You could also have a pop up warning or similar mechanism
(with the option to turn it off) that warns when you have replied,
changed the subject, and haven't deleted the In-Reply-To header.
There are many ways that this could be configured. Of course, you
wouldn't have to mention the In-Reply-To header, but instead just
have a button marked "Break thread" or something similar.
This is correct threading:
blueberries
Re: blackberries (was: blueberries)
Re: blackberries
changing the subject while staying in the thread means that the
(sub-)thread *evolved* into something different.
This is incorrect threading (thread hijacking)
blueberries
Re: blueberries
red roses
...
New proposal: Have a "Keep in thread" button
1) User wants to reply to a mail subject "blueberries"
2) Letters prepares an email with In-Reply-To header and subject "Re:
blueberries", and disables the "Keep in thread" button
3) User klicks in the subject line and changes the subject to
"blackberries"
4) Letters enables the "Keep in thread" button (which shows the user,
that this mail is no longer considered being in the thread)
5) User either sends the mail
-> Letters removes the In-Reply-To header, thus the email will start
a new thread
or
6) User klicks on the "Keep in thread" button
7) Letters adds the parentheses, "was: " and the old subject: "Re:
blackberries (was: blueberries)"
8) User sends the thread reply
9) Letters keeps the In-Reply-To header, thus the email will stay in
the thread
Thus you cannot hijack a thread unintentionally.
Still Letters should remove any parentheses and their content if the
content starts with "was: " from the subject when replying - see the
second reply in the correct threading example above.
--
Marc
_______________________________________________
[email protected] mailing list
List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com
