<?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: More Effective Email Tip #2 RE: e-newsletters</title>
	<atom:link href="http://missioncommunicate.com/blog/2006/06/30/more-effective-email-tip-2-re-e-newsletters/feed/" rel="self" type="application/rss+xml" />
	<link>http://missioncommunicate.com/blog/2006/06/30/more-effective-email-tip-2-re-e-newsletters/</link>
	<description>strategies and tools that work</description>
	<pubDate>Fri, 05 Sep 2008 20:19:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Nick Ciske</title>
		<link>http://missioncommunicate.com/blog/2006/06/30/more-effective-email-tip-2-re-e-newsletters/#comment-1124</link>
		<dc:creator>Nick Ciske</dc:creator>
		<pubDate>Fri, 14 Jul 2006 16:13:13 +0000</pubDate>
		<guid isPermaLink="false">http://missioncommunicate.com/2006/06/30/more-effective-email-tip-2-re-e-newsletters/#comment-1124</guid>
		<description>#1: It doesn't hurt to remind people of the relationship- "You're recieveing this email beacuse you signed up to recieve email updates on our web site."
#2: Never. Ever. EVER. If it's a file (PDF, DOC, etc.), send it as an attachment. (Link to it if necessary and so allow people to download it if they want it.)
#3: It's also the law in the USA (CAN-SPAM Act). Don't forget to include the mailing address of your origanization too.
#4: If you can, have someone else (or a few others) proof read it.
#5: Corrollary: keep it short and sweet. If it's too long people won;t bother to even start reading it... and the chances they'll go back and read it? Slim to none.</description>
		<content:encoded><![CDATA[<p>#1: It doesn&#8217;t hurt to remind people of the relationship- &#8220;You&#8217;re recieveing this email beacuse you signed up to recieve email updates on our web site.&#8221;<br />
#2: Never. Ever. EVER. If it&#8217;s a file (PDF, DOC, etc.), send it as an attachment. (Link to it if necessary and so allow people to download it if they want it.)<br />
#3: It&#8217;s also the law in the USA (CAN-SPAM Act). Don&#8217;t forget to include the mailing address of your origanization too.<br />
#4: If you can, have someone else (or a few others) proof read it.<br />
#5: Corrollary: keep it short and sweet. If it&#8217;s too long people won;t bother to even start reading it&#8230; and the chances they&#8217;ll go back and read it? Slim to none.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Send Photos Email and spare your friends&#8217; the extra weight at Mission: Communicate Blog</title>
		<link>http://missioncommunicate.com/blog/2006/06/30/more-effective-email-tip-2-re-e-newsletters/#comment-1123</link>
		<dc:creator>Send Photos Email and spare your friends&#8217; the extra weight at Mission: Communicate Blog</dc:creator>
		<pubDate>Fri, 30 Jun 2006 17:50:30 +0000</pubDate>
		<guid isPermaLink="false">http://missioncommunicate.com/2006/06/30/more-effective-email-tip-2-re-e-newsletters/#comment-1123</guid>
		<description>[...] Further thoughts to come…. How to create a nice e-mail newsletter - text, photos and more…  Tags: communication, email, graphics, tips ~n~ tricks, tools communication, email, graphics, tips ~n~ tricks, tools   Filed under: tips ~n~ tricks  &#160;&#160;&#124;&#160;&#160; Tags: communication, email, graphics, tips ~n~ tricks, tools. [...]</description>
		<content:encoded><![CDATA[<p>[...] Further thoughts to come…. How to create a nice e-mail newsletter - text, photos and more…  Tags: communication, email, graphics, tips ~n~ tricks, tools communication, email, graphics, tips ~n~ tricks, tools   Filed under: tips ~n~ tricks  &nbsp;&nbsp;|&nbsp;&nbsp; Tags: communication, email, graphics, tips ~n~ tricks, tools. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
