<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>

<channel>
	<title>willnorris.com &#187; email</title>
	<atom:link href="http://willnorris.com/tag/email/feed" rel="self" type="application/rss+xml" />
	<link>http://willnorris.com</link>
	<description>there&#039;s more to life than this</description>
	<lastBuildDate>Tue, 15 May 2012 21:57:32 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-beta3-20574</generator>
<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
		<item>
		<title>Email Etiquette: Replying to Mailing Lists</title>
		<link>http://willnorris.com/2008/12/email-etiquette-replying-to-mailing-lists</link>
		<comments>http://willnorris.com/2008/12/email-etiquette-replying-to-mailing-lists#comments</comments>
		<pubDate>Thu, 25 Dec 2008 22:23:44 +0000</pubDate>
		<dc:creator>Will Norris</dc:creator>
				<category><![CDATA[technology]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[mailing lists]]></category>
		<category><![CDATA[netiquette]]></category>

		<guid isPermaLink="false">http://willnorris.com/?p=467</guid>
		<description><![CDATA[Most email clients support the idea of &#8220;threaded messages&#8221;&#8230; that is, the client can group together individual email messages that are part of the same conversation, or &#8220;thread&#8221;. This is a particularly useful feature on mailing lists where multiple conversations are happening at the same time. For example, the following screenshot of the OpenID General [...]]]></description>
			<content:encoded><![CDATA[<p>Most email clients <a href="http://www.flickr.com/photos/wnorris/3135621059/in/photostream/">support the idea</a> of &#8220;threaded messages&#8221;&#8230; that is, the client can group together individual email messages that are part of the same conversation, or &#8220;thread&#8221;.  This is a particularly useful feature on mailing lists where multiple conversations are happening at the same time.  For example, the following screenshot of the <a href="http://openid.net/mailman/listinfo/general">OpenID General Discussion</a> list shows two distinct message threads in Apple&#8217;s Mail application:</p>

<p><img src="http://farm4.static.flickr.com/3227/3136438166_b8313d4de9_o.png" alt="Example of message threading" /></p>

<p>In order to match up messages that belong to the same conversation, email clients use two techniques.  First, they match emails with the same subject line, which is mostly accurate.  Occasionally this will result in &#8220;false positives&#8221; where unrelated emails are grouped together because the senders happened to use the same subject.  The second method is far more accurate and makes use of a hidden portion of the email message which most people never see.  Emails, just like web page requests include a number of hidden &#8220;headers&#8221; that carry extra information about the message.</p>

<p><img src="http://farm4.static.flickr.com/3102/3135669251_6d0428531b_o.png" alt="Email Headers" /></p>

<p>This includes information about the email client the sender used, the message priority, and the different servers that handled the message along the way.  Each email message also includes a unique identification string called the &#8220;Message-Id&#8221;.  This string is unique for every email message in the world&#8230; no two are ever identical.  In the screenshot above, the Message-Id is <code>&lt;49518270.7010405@degeneration.co.uk&gt;</code>.  If someone were to reply to that message, the Message-Id of the original email would be included in the reply email as another hidden header aptly named In-Reply-To:</p>

<p><img src="http://farm4.static.flickr.com/3096/3136500952_a2a5996464_o.png" alt="Email Reply" /></p>

<p>Any future replies would continue to include an In-Reply-To header with this value so that email clients can recognize that they all belong to together and group them accordingly.  This method of conversation tracking is far more accurate, but has one problem.  That problem occurs when some lazy person comes along and wants to send a message to the mailing list, but instead of clicking on &#8220;New Message&#8221; in their mail client, they pick a message at random from the list, click &#8220;Reply&#8221;, and then clear out the subject and body of the message.  While this <strong>looks</strong> like a new message about a new topic, because the person &#8220;replied&#8221; to a previous email instead of starting a new message, the previous Message-Id got attached.  Note the following reply to the same email above, but now the subject has been changed from talking about a Google sign-in button, to the BBC being an OpenID provider.  These are completely different discussions!</p>

<p><img src="http://farm4.static.flickr.com/3263/3136581064_faf84dec4b_o.png" alt="Incorrect Reply" /></p>

<p>If we go back to our first screenshot of the two message threads, we can see the this new message (as well as any of its replies) get lumped right together with the original discussion.</p>

<p><img src="http://farm4.static.flickr.com/3119/3135772283_3b54c129d2_o.png" alt="Merged Discussions" /></p>

<p>So today&#8217;s lesson in email etiquette: If you&#8217;re not actually replying to a particular email, <strong>DON&#8217;T CLICK &#8220;REPLY&#8221;</strong>.  Copy and paste the &#8220;To:&#8221; email address if you have to, but don&#8217;t click reply!  There might be some grace here for emails between individuals, but not on mailing lists, <strong>especially</strong> not on technical mailing lists.  (Not meaning to pick on Peter in the screenshots above&#8230; he is not the only offender on the OpenID mailing lists, that just happened to be the most recent occurrence).</p>

<p>Okay, that&#8217;s my rant for the day&#8230; I&#8217;m good now.  Oh, and Merry Christmas. :)</p>
]]></content:encoded>
			<wfw:commentRss>http://willnorris.com/2008/12/email-etiquette-replying-to-mailing-lists/feed</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>E-mail is not a platform for design</title>
		<link>http://willnorris.com/2007/06/e-mail-is-not-a-platform-for-design</link>
		<comments>http://willnorris.com/2007/06/e-mail-is-not-a-platform-for-design#comments</comments>
		<pubDate>Mon, 11 Jun 2007 04:51:55 +0000</pubDate>
		<dc:creator>Will Norris</dc:creator>
				<category><![CDATA[technology]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[netiquette]]></category>

		<guid isPermaLink="false">http://willnorris.com/2007/06/e-mail-is-not-a-platform-for-design</guid>
		<description><![CDATA[I&#8217;ve been away from my blog for quite a while due to some various medical problems, but I really do have a number of posts in the works. It&#8217;s a a little lame to return with just a link, but this one is near and dear to my heart: E-mail is not a platform for [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been away from my blog for quite a while due to some various medical problems, but I really do have a number of posts in the works.  It&#8217;s a a little lame to return with just a link, but this one is near and dear to my heart:</p>

<p><a href="http://www.zeldman.com/2007/06/08/e-mail-is-not-a-platform-for-design/">E-mail is not a platform for design</a></p>
]]></content:encoded>
			<wfw:commentRss>http://willnorris.com/2007/06/e-mail-is-not-a-platform-for-design/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

