<?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: How to Do a Great Weekly Email for Your Congregation</title>
	<atom:link href="http://www.faithandweb.com/2007/06/21/how-to-do-a-great-weekly-email-for-your-congregation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.faithandweb.com/2007/06/21/how-to-do-a-great-weekly-email-for-your-congregation/</link>
	<description>A Church Web Diva's Musings on Excellence in Religious Websites</description>
	<lastBuildDate>Sat, 03 Jul 2010 17:11:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Anna Belle</title>
		<link>http://www.faithandweb.com/2007/06/21/how-to-do-a-great-weekly-email-for-your-congregation/comment-page-1/#comment-323</link>
		<dc:creator>Anna Belle</dc:creator>
		<pubDate>Sat, 23 Jun 2007 19:26:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.faithandweb.com/2007/06/21/how-to-do-a-great-weekly-email-for-your-congregation/#comment-323</guid>
		<description>Great suggestions, Mark.  You are so right about using another service provider when double checking.  

Poor Nigeria. My daughter briefly lived in Mali, right next door on the River Niger.  Back then, email from that part of the world was my top priority.</description>
		<content:encoded><![CDATA[<p>Great suggestions, Mark.  You are so right about using another service provider when double checking.  </p>
<p>Poor Nigeria. My daughter briefly lived in Mali, right next door on the River Niger.  Back then, email from that part of the world was my top priority.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Alves</title>
		<link>http://www.faithandweb.com/2007/06/21/how-to-do-a-great-weekly-email-for-your-congregation/comment-page-1/#comment-320</link>
		<dc:creator>Mark Alves</dc:creator>
		<pubDate>Fri, 22 Jun 2007 02:50:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.faithandweb.com/2007/06/21/how-to-do-a-great-weekly-email-for-your-congregation/#comment-320</guid>
		<description>Good tips. A couple more:
- Include fresh content in the subject line. In your case, that might include the title of the Wed. class.
- When double checking to see if the message was received, include accounts at Yahoo, Gmail, AOL and any popular local providers. Your checkers shouldn&#039;t have the sender&#039;s email address in their address books so that you can confirm the messages aren&#039;t getting blocked at the provider level. Church messages can inadvertently sound spammy -- sign up now, free offer, requests for donations. And if you have a sister organization in Nigeria, look out...

After the email goes out, the content sounds like it would also make a great RSS feed.</description>
		<content:encoded><![CDATA[<p>Good tips. A couple more:<br />
- Include fresh content in the subject line. In your case, that might include the title of the Wed. class.<br />
- When double checking to see if the message was received, include accounts at Yahoo, Gmail, AOL and any popular local providers. Your checkers shouldn&#8217;t have the sender&#8217;s email address in their address books so that you can confirm the messages aren&#8217;t getting blocked at the provider level. Church messages can inadvertently sound spammy &#8212; sign up now, free offer, requests for donations. And if you have a sister organization in Nigeria, look out&#8230;</p>
<p>After the email goes out, the content sounds like it would also make a great RSS feed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anna Belle</title>
		<link>http://www.faithandweb.com/2007/06/21/how-to-do-a-great-weekly-email-for-your-congregation/comment-page-1/#comment-318</link>
		<dc:creator>Anna Belle</dc:creator>
		<pubDate>Fri, 22 Jun 2007 00:26:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.faithandweb.com/2007/06/21/how-to-do-a-great-weekly-email-for-your-congregation/#comment-318</guid>
		<description>Steve -- You are in good company being anti-HTML email.  Zeldman, one of my web mentors, rails against it quite regularly.  To quote him: &lt;a href=&quot;http://zeldman.com/2007/06/08/e-mail-is-not-a-platform-for-design/&quot; rel=&quot;nofollow&quot;&gt;&quot;ASCII means never having to say you’re sorry.&quot;&lt;/a&gt;  

Ms. Theologian -- yes, yes.  We had one jinxed email where I swear there were 12 of us involved (1 to write, 1 to produce and 10 to troubleshoot).  I morphed into the chief cat herder.  It wasn&#039;t pretty.</description>
		<content:encoded><![CDATA[<p>Steve &#8212; You are in good company being anti-HTML email.  Zeldman, one of my web mentors, rails against it quite regularly.  To quote him: <a href="http://zeldman.com/2007/06/08/e-mail-is-not-a-platform-for-design/" rel="nofollow">&#8220;ASCII means never having to say you’re sorry.&#8221;</a>  </p>
<p>Ms. Theologian &#8212; yes, yes.  We had one jinxed email where I swear there were 12 of us involved (1 to write, 1 to produce and 10 to troubleshoot).  I morphed into the chief cat herder.  It wasn&#8217;t pretty.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ms. Theologian</title>
		<link>http://www.faithandweb.com/2007/06/21/how-to-do-a-great-weekly-email-for-your-congregation/comment-page-1/#comment-315</link>
		<dc:creator>Ms. Theologian</dc:creator>
		<pubDate>Thu, 21 Jun 2007 22:28:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.faithandweb.com/2007/06/21/how-to-do-a-great-weekly-email-for-your-congregation/#comment-315</guid>
		<description>You&#039;re so right about minimizing the cooks in the kitchen. I am the editor of a little community newsletter for our water company and everyone wants to be involved, but when two people write the education component, one person contributes the well measurement, I edit everything, and then it gets approved by three board members....it never gets done.</description>
		<content:encoded><![CDATA[<p>You&#8217;re so right about minimizing the cooks in the kitchen. I am the editor of a little community newsletter for our water company and everyone wants to be involved, but when two people write the education component, one person contributes the well measurement, I edit everything, and then it gets approved by three board members&#8230;.it never gets done.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Caldwell</title>
		<link>http://www.faithandweb.com/2007/06/21/how-to-do-a-great-weekly-email-for-your-congregation/comment-page-1/#comment-312</link>
		<dc:creator>Steve Caldwell</dc:creator>
		<pubDate>Thu, 21 Jun 2007 13:02:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.faithandweb.com/2007/06/21/how-to-do-a-great-weekly-email-for-your-congregation/#comment-312</guid>
		<description>One possible addition to your list might be using plain-text instead of HTML and other fancy formatting in your weekly emails.

Many corporate and government organizations are restricting the use of HTML-formatted emails due to security issues.  For example, I just received an email at my office telling us that the Air Force email system would start rejecting HTML-formatted emails due to security issues.

There&#039;s a good article on the problems with HTML email that is available as a link from the UUA web site:

&quot;What is wrong with sending HTML or MIME messages?&quot;
http://www.expita.com/nomime.html#intro

This article gives background on the computer security issues.</description>
		<content:encoded><![CDATA[<p>One possible addition to your list might be using plain-text instead of HTML and other fancy formatting in your weekly emails.</p>
<p>Many corporate and government organizations are restricting the use of HTML-formatted emails due to security issues.  For example, I just received an email at my office telling us that the Air Force email system would start rejecting HTML-formatted emails due to security issues.</p>
<p>There&#8217;s a good article on the problems with HTML email that is available as a link from the UUA web site:</p>
<p>&#8220;What is wrong with sending HTML or MIME messages?&#8221;<br />
<a href="http://www.expita.com/nomime.html#intro" rel="nofollow">http://www.expita.com/nomime.html#intro</a></p>
<p>This article gives background on the computer security issues.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.327 seconds -->
