<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Alex King on email signatures</title>
	<atom:link href="http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/</link>
	<description>Tips and add-ons to make Apple Mail / Mail.app even better</description>
	<lastBuildDate>Mon, 21 Nov 2011 18:23:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: alexking.org: Blog &#62; Around the web</title>
		<link>http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/comment-page-1/#comment-1094</link>
		<dc:creator>alexking.org: Blog &#62; Around the web</dc:creator>
		<pubDate>Sun, 29 Jan 2006 20:08:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/#comment-1094</guid>
		<description>[...] Hawk Wings - Alex King on email signatures [...]</description>
		<content:encoded><![CDATA[<p>[...] Hawk Wings &#8211; Alex King on email signatures [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sjk</title>
		<link>http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/comment-page-1/#comment-1082</link>
		<dc:creator>sjk</dc:creator>
		<pubDate>Sun, 29 Jan 2006 03:54:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/#comment-1082</guid>
		<description>Mulberry has a useful feature called identities for setting various sender-address settings, including signatures.  A default identity is usually associated with your primary mail address.  Other identities inherit settings from any identity (typically the default) and can override specific ones.   Also, incoming accounts (IMAP, POP) are distinct and managed separately from outgoing accounts (SMTP), with each identity setting or inheriting only the latter.  It makes sense because IMAP/POP accounts are unnecessary when you&#039;re just &lt;i&gt;sending&lt;/i&gt; mail.

Anyway, Mulberry identities provide a more flexible mechanism for processing certain sender-centric mail actions than the all-too-common method of configuring &quot;dummy&quot; accounts.</description>
		<content:encoded><![CDATA[<p>Mulberry has a useful feature called identities for setting various sender-address settings, including signatures.  A default identity is usually associated with your primary mail address.  Other identities inherit settings from any identity (typically the default) and can override specific ones.   Also, incoming accounts (IMAP, POP) are distinct and managed separately from outgoing accounts (SMTP), with each identity setting or inheriting only the latter.  It makes sense because IMAP/POP accounts are unnecessary when you&#8217;re just <i>sending</i> mail.</p>
<p>Anyway, Mulberry identities provide a more flexible mechanism for processing certain sender-centric mail actions than the all-too-common method of configuring &#8220;dummy&#8221; accounts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Meyer</title>
		<link>http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/comment-page-1/#comment-1043</link>
		<dc:creator>Tony Meyer</dc:creator>
		<pubDate>Thu, 26 Jan 2006 21:13:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/#comment-1043</guid>
		<description>I like the &#039;just select the one you want&#039; solution.  A lot of the time (e.g. corresponding with people you deal with all the time) the sig really just isn&#039;t necessary (unless there&#039;s some stupid corporate policy about it being required) and so it can be left out in that case.</description>
		<content:encoded><![CDATA[<p>I like the &#8216;just select the one you want&#8217; solution.  A lot of the time (e.g. corresponding with people you deal with all the time) the sig really just isn&#8217;t necessary (unless there&#8217;s some stupid corporate policy about it being required) and so it can be left out in that case.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brady J. Frey</title>
		<link>http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/comment-page-1/#comment-1041</link>
		<dc:creator>Brady J. Frey</dc:creator>
		<pubDate>Thu, 26 Jan 2006 20:53:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/#comment-1041</guid>
		<description>I was thinking the other day too -- for each company, I would just setup individual imap (or pop if that&#039;s your flavor) account, and then in the signatures area, just create a new one for each, and have it default that signature if you select compose with that email.

But your right, just selecting the one you want in the top right works too!</description>
		<content:encoded><![CDATA[<p>I was thinking the other day too &#8212; for each company, I would just setup individual imap (or pop if that&#8217;s your flavor) account, and then in the signatures area, just create a new one for each, and have it default that signature if you select compose with that email.</p>
<p>But your right, just selecting the one you want in the top right works too!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/comment-page-1/#comment-1040</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Thu, 26 Jan 2006 20:40:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/#comment-1040</guid>
		<description>I was hoping you might comment here.

Having whizzed by http://www.dotfive.com/ the other day, I knew that you would know about branding ;-)

I solve this &quot;signature for identity&quot; problem within the one account by manually chosing the right sig for one of three aliases from the drop down box in the Compose window.

It&#039;s not a huge hassle. Not many of my emails require a signature. And, doing this way, the ones that do, get just the sig they need.</description>
		<content:encoded><![CDATA[<p>I was hoping you might comment here.</p>
<p>Having whizzed by <a href="http://www.dotfive.com/" rel="nofollow">http://www.dotfive.com/</a> the other day, I knew that you would know about branding ;-)</p>
<p>I solve this &#8220;signature for identity&#8221; problem within the one account by manually chosing the right sig for one of three aliases from the drop down box in the Compose window.</p>
<p>It&#8217;s not a huge hassle. Not many of my emails require a signature. And, doing this way, the ones that do, get just the sig they need.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brady J. Frey</title>
		<link>http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/comment-page-1/#comment-1030</link>
		<dc:creator>Brady J. Frey</dc:creator>
		<pubDate>Thu, 26 Jan 2006 17:23:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/#comment-1030</guid>
		<description>I would second the branding argument -- in theory, I would not want to mesh any number of identities I have, may they be url&#039;s or general tag lines and terms. 

However, in your case, your sites seem to be a mesh of personal and business, so you may be looking to do a &#039;9rules/whitespace&#039; interaction. The majority of businesses and professionals would not want that comparison. 

The example without graphical dividers is an unattractive example, from a typography point of view. Placing spacer characters in between can also be an annoyance, especially on screen readers who don&#039;t take to sounding them off nicely.</description>
		<content:encoded><![CDATA[<p>I would second the branding argument &#8212; in theory, I would not want to mesh any number of identities I have, may they be url&#8217;s or general tag lines and terms. </p>
<p>However, in your case, your sites seem to be a mesh of personal and business, so you may be looking to do a &#8217;9rules/whitespace&#8217; interaction. The majority of businesses and professionals would not want that comparison. </p>
<p>The example without graphical dividers is an unattractive example, from a typography point of view. Placing spacer characters in between can also be an annoyance, especially on screen readers who don&#8217;t take to sounding them off nicely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Meyer</title>
		<link>http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/comment-page-1/#comment-1025</link>
		<dc:creator>Tony Meyer</dc:creator>
		<pubDate>Thu, 26 Jan 2006 01:44:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/#comment-1025</guid>
		<description>&lt;blockquote&gt;
?¢‚Ç¨‚Äú
Alex King

www.alexking.org www.kingdesign.net www.feedlounge.com
&lt;/blockquote&gt;

If it were my signature, then having the reader recognise it as a URL would be sufficient, even if the mail client didn&#039;t (especially since I&#039;m unlikely to know what capabilities the reader&#039;s mail client has).  &quot;www&quot; is shorter than &quot;http://&quot;, however (as above).

Don&#039;t people need to know what FeedLounge/KingDesign are with any of the variants?  (except for the original non-combined version of FeedLounge).  A good branding tool needs to be tailored to the audience, which is completely opposite to the whole combining concept (he&#039;d be better off getting in the habit of inserting the correct sig manually, perhaps using some sort of auto-insert utility).</description>
		<content:encoded><![CDATA[<blockquote><p>
?¢‚Ç¨‚Äú<br />
Alex King</p>
<p><a href="http://www.alexking.org" rel="nofollow">http://www.alexking.org</a> <a href="http://www.kingdesign.net" rel="nofollow">http://www.kingdesign.net</a> <a href="http://www.feedlounge.com" rel="nofollow">http://www.feedlounge.com</a>
</p></blockquote>
<p>If it were my signature, then having the reader recognise it as a URL would be sufficient, even if the mail client didn&#8217;t (especially since I&#8217;m unlikely to know what capabilities the reader&#8217;s mail client has).  &#8220;www&#8221; is shorter than &#8220;http://&#8221;, however (as above).</p>
<p>Don&#8217;t people need to know what FeedLounge/KingDesign are with any of the variants?  (except for the original non-combined version of FeedLounge).  A good branding tool needs to be tailored to the audience, which is completely opposite to the whole combining concept (he&#8217;d be better off getting in the habit of inserting the correct sig manually, perhaps using some sort of auto-insert utility).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/comment-page-1/#comment-1024</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Thu, 26 Jan 2006 00:21:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/#comment-1024</guid>
		<description>Tony wrote:
&lt;blockquote&gt;There really is little point in the ?¢‚Ç¨?ìhttp:?¢‚Ç¨¬ù - what protocol do people really expect?&lt;/blockquote&gt;But you would need to include the www in order for Mail.app to recognise it as a URL and render it as clickable (which is the point of including it, isn&#039;t it?)

I see the virtue of the minimalist wide version, but is it a good branding tool? People need to know what feedlounge and kingdesign are already.</description>
		<content:encoded><![CDATA[<p>Tony wrote:</p>
<blockquote><p>There really is little point in the ?¢‚Ç¨?ìhttp:?¢‚Ç¨¬ù &#8211; what protocol do people really expect?</p></blockquote>
<p>But you would need to include the www in order for Mail.app to recognise it as a URL and render it as clickable (which is the point of including it, isn&#8217;t it?)</p>
<p>I see the virtue of the minimalist wide version, but is it a good branding tool? People need to know what feedlounge and kingdesign are already.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Meyer</title>
		<link>http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/comment-page-1/#comment-1023</link>
		<dc:creator>Tony Meyer</dc:creator>
		<pubDate>Wed, 25 Jan 2006 23:15:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/#comment-1023</guid>
		<description>There&#039;s very little utility to the &#039;headings&#039; describing each URL, since two of the three are simply the domain.  Wide looks a lot better than tall, IMO.  A simpler version would avoid problems for those people that don&#039;t read email properly in a monospaced font:

&quot;&quot;&quot;
-- 
Alex King
	
alexking.org     kingdesign.net    feedlounge.com
&quot;&quot;&quot;

(There really is little point in the &quot;http:&quot; - what protocol do people really expect?).  Even if the font reduces the four spaces to a very small gap, it&#039;ll still be obvious (a semi-colon could be used instead of the spaces, which looks equally good).

Note that a signature should start with two dashes, then a space, then start the actual sig on the next line.</description>
		<content:encoded><![CDATA[<p>There&#8217;s very little utility to the &#8216;headings&#8217; describing each URL, since two of the three are simply the domain.  Wide looks a lot better than tall, IMO.  A simpler version would avoid problems for those people that don&#8217;t read email properly in a monospaced font:</p>
<p>&#8220;&#8221;"<br />
&#8211;<br />
Alex King</p>
<p>alexking.org     kingdesign.net    feedlounge.com<br />
&#8220;&#8221;"</p>
<p>(There really is little point in the &#8220;http:&#8221; &#8211; what protocol do people really expect?).  Even if the font reduces the four spaces to a very small gap, it&#8217;ll still be obvious (a semi-colon could be used instead of the spaces, which looks equally good).</p>
<p>Note that a signature should start with two dashes, then a space, then start the actual sig on the next line.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/comment-page-1/#comment-1021</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Wed, 25 Jan 2006 21:01:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/01/26/alex-king-on-email-signatures/#comment-1021</guid>
		<description>Exactly! That&#039;s my concern too. 

Those pipe characters, which look so lovely in a monospaced font, will end up ragged and hard to read in many proportionational fonts.

Go tall!</description>
		<content:encoded><![CDATA[<p>Exactly! That&#8217;s my concern too. </p>
<p>Those pipe characters, which look so lovely in a monospaced font, will end up ragged and hard to read in many proportionational fonts.</p>
<p>Go tall!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

