diff options
| author | Luke T. Shumaker <lukeshu@lukeshu.com> | 2024-06-08 22:36:52 -0600 |
|---|---|---|
| committer | Luke T. Shumaker <lukeshu@lukeshu.com> | 2024-06-08 22:37:11 -0600 |
| commit | 09eab3442e382f082501965f2e9a8caf04fba5b8 (patch) | |
| tree | a228ca166f8206a60969f1f6551e4eb85db43973 /public/message-threading.html | |
| parent | 140e1538fb1472f310afc9e4fd35e66bca116249 (diff) | |
| parent | e480d172a38df962b8b0a5b051c0bb520f7f618b (diff) | |
make: Write a post about my email to jwz
Diffstat (limited to 'public/message-threading.html')
| -rw-r--r-- | public/message-threading.html | 88 |
1 files changed, 88 insertions, 0 deletions
diff --git a/public/message-threading.html b/public/message-threading.html new file mode 100644 index 0000000..f829ade --- /dev/null +++ b/public/message-threading.html @@ -0,0 +1,88 @@ +<!DOCTYPE html> +<html lang="en"> +<head> + <meta charset="utf-8"> + <title>Notes on email message threading — Luke T. Shumaker</title> + <meta name="viewport" content="width=device-width, initial-scale=1"> + <link rel="stylesheet" href="assets/style.css"> + <link rel="alternate" type="application/atom+xml" href="./index.atom" name="web log entries"/> +</head> +<body> +<header><a href="/">Luke T. Shumaker</a> » <a href=/blog>blog</a> » message-threading</header> +<article> +<h1 id="notes-on-email-message-threading">Notes on email message +threading</h1> +<blockquote> +<p>I sent an email to Jamie Zawinski with feedback on his venerable +email threading algorithm. Perhaps my commentary will be a useful +reference to others implementing email threading.</p> +<p>You can see my implementation of his algorithm at <a +href="https://git.lukeshu.com/www/tree/cmd/generate/mailstuff/thread_alg.go" +class="uri">https://git.lukeshu.com/www/tree/cmd/generate/mailstuff/thread_alg.go</a> +(and a use of it at <a +href="https://git.lukeshu.com/www/tree/cmd/generate/mailstuff/thread.go" +class="uri">https://git.lukeshu.com/www/tree/cmd/generate/mailstuff/thread.go</a>).</p> +</blockquote> +<div style="font-family: monospace"> +<p>To: <a href="https://www.jwz.org/">Jamie Zawinski</a> <a +href="https://www.jwz.org/about.html"><jwz@jwz.org></a><br/> +Subject: message threading<br/> Date: Sat, 08 Jun 2024 22:34:41 -0600 +Message-ID: <87tti2ybry.wl-lukeshu@lukeshu.com></p> +</div> +<p>Hi,</p> +<p>I'm implementing message threading, and have been referencing both +your document <a +href="https://www.jwz.org/doc/threading.html"><https://www.jwz.org/doc/threading.html></a>; +and <a href="https://datatracker.ietf.org/doc/html/rfc5256">RFC +5256</a>. I'm not sure whether you're interested in updating a document +that's more than 25 years old, but if you are: I hope you find the +following feedback valuable.</p> +<p>You write that the algorithm in RFC 5256 is merely a <q>restating</q> +of your algorithm, but I noticed 3 (minor) differences:</p> +<ol type="1"> +<li><p>In your step 1.C, the RFC says to check whether this would create +a loop, and if it would to skip creating the link; your version only +says to perform this check in step 1.B.</p></li> +<li><p>The RFC says to sort the messages by date between your steps 4 +and 5; that is: when grouping by subject, containers in the root set +should be processed in date-order (you do not specify an order), and +that if container in the root set is empty then the subject should be +taken from the earliest-date child (you say to use an arbitrary +child).</p></li> +<li><p>The RFC precisely states how to trim a subject down to a "base +subject," rather than simply saying <q>Strip ``Re:'', ``RE:'', +``RE[5]:'', ``Re: Re[4]: Re:'' and so on.</q></p></li> +</ol> +<p>Additionally, there are two minor points on which I found their +version to be clearer:</p> +<ol type="1"> +<li><p>The RFC specifies how to handle messages without a Message-Id or +with a duplicate Message-Id (on <a +href="https://datatracker.ietf.org/doc/html/rfc5256#page-9">page 9</a>), +as well as how to normalize a Message-Id (by referring to <a +href="https://datatracker.ietf.org/doc/html/rfc2822">RFC 2822</a>). This +is perhaps out-of-scope of your algorithm document, but I feel that it +would be worth mentioning in your background or definitions +section.</p></li> +<li><p>In your step 1.B, I did not understand what <q>If they are +already linked, don't change the existing links</q> meant until I read +the RFC, which words it as <q>If a message already has a parent, don't +change the existing link.</q> It was unclear to me what <q>they</q> was +referring to in your version.</p></li> +</ol> +<div style="font-family: monospace"> +<p>-- <br/> Happy hacking,<br/> ~ Luke T. Shumaker<br/></p> +</div> + +</article> +<footer> + <aside class="sponsor"><p>I'd love it if you <a class="em" + href="/sponsor/">sponsored me</a>. It will allow me to continue + <a class="em" href="/imworkingon/">my work</a> on the GNU/Linux + ecosystem. Thanks!</p></aside> + +<p>The content of this page is Copyright © 2024 <a href="mailto:lukeshu@lukeshu.com">Luke T. Shumaker</a>.</p> +<p>This page is licensed under the <a href="https://creativecommons.org/licenses/by-sa/4.0/">CC BY-SA 4.0</a> license.</p> +</footer> +</body> +</html> |