<?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"
	>
<channel>
	<title>Comments on: E-Mail Etiquette</title>
	<atom:link href="http://thewritersbag.com/writing-strategies/e-mail-etiquette/feed" rel="self" type="application/rss+xml" />
	<link>http://thewritersbag.com/writing-strategies/e-mail-etiquette</link>
	<description>Writing tips for the real world.</description>
	<pubDate>Sun, 07 Sep 2008 21:56:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: The Writers&#8217; Block Carnival - writers from across the blogosphere &#171; The Writers&#8217; Block</title>
		<link>http://thewritersbag.com/writing-strategies/e-mail-etiquette#comment-62</link>
		<dc:creator>The Writers&#8217; Block Carnival - writers from across the blogosphere &#171; The Writers&#8217; Block</dc:creator>
		<pubDate>Thu, 28 Feb 2008 20:33:07 +0000</pubDate>
		<guid isPermaLink="false">http://thewritersbag.com/writing-strategies/e-mail-etiquette#comment-62</guid>
		<description>[...] Osborne presents E-Mail Etiquette posted at TheWritersBag.com, saying, &#8220;Steve Osborne, author of &#8220;Writing Tips for the [...]</description>
		<content:encoded><![CDATA[<p>[...] Osborne presents E-Mail Etiquette posted at TheWritersBag.com, saying, &#8220;Steve Osborne, author of &#8220;Writing Tips for the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Osborne</title>
		<link>http://thewritersbag.com/writing-strategies/e-mail-etiquette#comment-33</link>
		<dc:creator>Steve Osborne</dc:creator>
		<pubDate>Sat, 26 Jan 2008 15:35:43 +0000</pubDate>
		<guid isPermaLink="false">http://thewritersbag.com/writing-strategies/e-mail-etiquette#comment-33</guid>
		<description>Good point, Tip Diva. An e-mail without a subject line is less likely to be read. And if people do read it, they will likely do so with a certain amount of resentment. Even worse is a misleading subject line. That creates a trust issue. Thanks for your comment.</description>
		<content:encoded><![CDATA[<p>Good point, Tip Diva. An e-mail without a subject line is less likely to be read. And if people do read it, they will likely do so with a certain amount of resentment. Even worse is a misleading subject line. That creates a trust issue. Thanks for your comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tip Diva</title>
		<link>http://thewritersbag.com/writing-strategies/e-mail-etiquette#comment-32</link>
		<dc:creator>Tip Diva</dc:creator>
		<pubDate>Sat, 26 Jan 2008 05:29:44 +0000</pubDate>
		<guid isPermaLink="false">http://thewritersbag.com/writing-strategies/e-mail-etiquette#comment-32</guid>
		<description>I'd probably add that one should be clear in the subject line. I receive e-mails along the line of "The report is due today" often. Okay, the report is due today - good subject line.

But when I receive &lt;i&gt;(no subject)&lt;/i&gt; or a subject line that has absolutely nothing to do with the message body, I go absolutely bonkers.

I once was chewed out by a friend for not responding to an important e-mail promptly. The subject? "FWD: (no subject)" I automatically assumed it was a stupid forward with pictures of kittens or a YouTube video and didn't read it right away.</description>
		<content:encoded><![CDATA[<p>I&#8217;d probably add that one should be clear in the subject line. I receive e-mails along the line of &#8220;The report is due today&#8221; often. Okay, the report is due today - good subject line.</p>
<p>But when I receive <i>(no subject)</i> or a subject line that has absolutely nothing to do with the message body, I go absolutely bonkers.</p>
<p>I once was chewed out by a friend for not responding to an important e-mail promptly. The subject? &#8220;FWD: (no subject)&#8221; I automatically assumed it was a stupid forward with pictures of kittens or a YouTube video and didn&#8217;t read it right away.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Just Write BlogCarnival (edition nine) &#171; Aaron Crocco: Copious Notes</title>
		<link>http://thewritersbag.com/writing-strategies/e-mail-etiquette#comment-31</link>
		<dc:creator>Just Write BlogCarnival (edition nine) &#171; Aaron Crocco: Copious Notes</dc:creator>
		<pubDate>Fri, 25 Jan 2008 14:02:04 +0000</pubDate>
		<guid isPermaLink="false">http://thewritersbag.com/writing-strategies/e-mail-etiquette#comment-31</guid>
		<description>[...] Osborne presents E-Mail Etiquette posted at TheWritersBag.com, saying, &#8220;Steve Osborne, author of &#8220;Writing Tips for the [...]</description>
		<content:encoded><![CDATA[<p>[...] Osborne presents E-Mail Etiquette posted at TheWritersBag.com, saying, &#8220;Steve Osborne, author of &#8220;Writing Tips for the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Incurable Disease of Writing &#187; Blog Archive &#187; Just Write BlogCarnival (edition nine)</title>
		<link>http://thewritersbag.com/writing-strategies/e-mail-etiquette#comment-30</link>
		<dc:creator>Incurable Disease of Writing &#187; Blog Archive &#187; Just Write BlogCarnival (edition nine)</dc:creator>
		<pubDate>Fri, 25 Jan 2008 12:13:40 +0000</pubDate>
		<guid isPermaLink="false">http://thewritersbag.com/writing-strategies/e-mail-etiquette#comment-30</guid>
		<description>[...] Osborne presents E-Mail Etiquette posted at TheWritersBag.com, saying, &#8220;Steve Osborne, author of &#8220;Writing Tips for the [...]</description>
		<content:encoded><![CDATA[<p>[...] Osborne presents E-Mail Etiquette posted at TheWritersBag.com, saying, &#8220;Steve Osborne, author of &#8220;Writing Tips for the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Osborne</title>
		<link>http://thewritersbag.com/writing-strategies/e-mail-etiquette#comment-28</link>
		<dc:creator>Steve Osborne</dc:creator>
		<pubDate>Tue, 22 Jan 2008 18:05:29 +0000</pubDate>
		<guid isPermaLink="false">http://thewritersbag.com/writing-strategies/e-mail-etiquette#comment-28</guid>
		<description>Chris, you're absolutetly right. I would add that your comment applies to individual e-mails as well as to group e-mails. In spoken conversation, we typically let things drag on with comments like the one you mention and others such as "Great" or "Sounds good" and so on. We want to carry that habit over into our e-mail conversations, but we shouldn't unless it's meaningful to do so. It takes time to open and view an e-mail, so let's be sure that whenever we force someone to do that, it's worth their time. Thanks for your comment.</description>
		<content:encoded><![CDATA[<p>Chris, you&#8217;re absolutetly right. I would add that your comment applies to individual e-mails as well as to group e-mails. In spoken conversation, we typically let things drag on with comments like the one you mention and others such as &#8220;Great&#8221; or &#8220;Sounds good&#8221; and so on. We want to carry that habit over into our e-mail conversations, but we shouldn&#8217;t unless it&#8217;s meaningful to do so. It takes time to open and view an e-mail, so let&#8217;s be sure that whenever we force someone to do that, it&#8217;s worth their time. Thanks for your comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://thewritersbag.com/writing-strategies/e-mail-etiquette#comment-27</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Tue, 22 Jan 2008 15:46:32 +0000</pubDate>
		<guid isPermaLink="false">http://thewritersbag.com/writing-strategies/e-mail-etiquette#comment-27</guid>
		<description>Oh, and can I add, don't reply all to an email going out to a large group only to say something like, "Yes, I agree."  Drives me nuts.</description>
		<content:encoded><![CDATA[<p>Oh, and can I add, don&#8217;t reply all to an email going out to a large group only to say something like, &#8220;Yes, I agree.&#8221;  Drives me nuts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
