<?xml version="1.0" encoding="ISO-8859-1"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: SpamAssassin&#8217;s Tips on Deliverability</title>
	<link>http://www.aweber.com/blog/email-deliverability/spamassassin-deliverability-tips.htm</link>
	<description>Email Marketing Tips on the AWeber Blog</description>
	<pubDate>Fri, 16 May 2008 22:50:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Jim Liddane</title>
		<link>http://www.aweber.com/blog/email-deliverability/spamassassin-deliverability-tips.htm#comment-17010</link>
		<dc:creator>Jim Liddane</dc:creator>
		<pubDate>Tue, 06 Nov 2007 23:38:44 +0000</pubDate>
		<guid>http://www.aweber.com/blog/email-deliverability/spamassassin-deliverability-tips.htm#comment-17010</guid>
		<description>Thanks John - I think you have hit the nail on the head, and you are also right in saying that the longer the message - the less likely it is that Spam Assassin will highlight the problem.

Since starting this thread, I have isolated the newsletters that brought up a warning, and by laboriously removing one link at a time (I kow - I lead a sad life!) and re-checking the score, I have managed to work out which domain is causing the spam-assassin warning.

Unfortunately, it is a domain used by more than a few musicians!

Still, at least now I know.</description>
		<content:encoded><![CDATA[<p>Thanks John - I think you have hit the nail on the head, and you are also right in saying that the longer the message - the less likely it is that Spam Assassin will highlight the problem.</p>
<p>Since starting this thread, I have isolated the newsletters that brought up a warning, and by laboriously removing one link at a time (I kow - I lead a sad life!) and re-checking the score, I have managed to work out which domain is causing the spam-assassin warning.</p>
<p>Unfortunately, it is a domain used by more than a few musicians!</p>
<p>Still, at least now I know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John W. Furst</title>
		<link>http://www.aweber.com/blog/email-deliverability/spamassassin-deliverability-tips.htm#comment-17006</link>
		<dc:creator>John W. Furst</dc:creator>
		<pubDate>Tue, 06 Nov 2007 22:55:59 +0000</pubDate>
		<guid>http://www.aweber.com/blog/email-deliverability/spamassassin-deliverability-tips.htm#comment-17006</guid>
		<description>About Spamassassin score: It happens that I use a Top Level Domain (TLD) &#34;.BIZ&#34; that is associated with much spam. I discover that the Spamassassin Score goes down, as the message is longer (=more valuable). I think, it is said that some TLDs get penalized that way. But it seems like one can live with it.

About HTML Emails: I admit I preferred to write plain text only emails until recently. It was AWeber, that made me investigate the HTML issue with emails further. Now I use a simple HTML Template with a graphics header and some text formatting and send combined HTML/Plain text messages. I don't limit this to the newsletter, but also write more HTML/Plain text mails on an individual basis. It looks very professional, if you do it right and don't misuse the HTML. -- John</description>
		<content:encoded><![CDATA[<p>About Spamassassin score: It happens that I use a Top Level Domain (TLD) &quot;.BIZ&quot; that is associated with much spam. I discover that the Spamassassin Score goes down, as the message is longer (=more valuable). I think, it is said that some TLDs get penalized that way. But it seems like one can live with it.</p>
<p>About HTML Emails: I admit I preferred to write plain text only emails until recently. It was AWeber, that made me investigate the HTML issue with emails further. Now I use a simple HTML Template with a graphics header and some text formatting and send combined HTML/Plain text messages. I don&#8217;t limit this to the newsletter, but also write more HTML/Plain text mails on an individual basis. It looks very professional, if you do it right and don&#8217;t misuse the HTML. &#8212; John</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lund</title>
		<link>http://www.aweber.com/blog/email-deliverability/spamassassin-deliverability-tips.htm#comment-16902</link>
		<dc:creator>Lund</dc:creator>
		<pubDate>Thu, 01 Nov 2007 23:11:12 +0000</pubDate>
		<guid>http://www.aweber.com/blog/email-deliverability/spamassassin-deliverability-tips.htm#comment-16902</guid>
		<description>Thank You for the usefull Tips on Deliverability!</description>
		<content:encoded><![CDATA[<p>Thank You for the usefull Tips on Deliverability!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donate Your Weight</title>
		<link>http://www.aweber.com/blog/email-deliverability/spamassassin-deliverability-tips.htm#comment-16846</link>
		<dc:creator>Donate Your Weight</dc:creator>
		<pubDate>Tue, 30 Oct 2007 21:58:17 +0000</pubDate>
		<guid>http://www.aweber.com/blog/email-deliverability/spamassassin-deliverability-tips.htm#comment-16846</guid>
		<description>Plain text e-mail is just....Plain.  I like an HTML e-mail, it reminds me of a newsletter and I can jump around to the sections of the message I'm most interested in quickly.  With text e-mails, everything looks exactly the same and if I'm busy, I might delete it rather than scan through it to see if it interests me.</description>
		<content:encoded><![CDATA[<p>Plain text e-mail is just&#8230;.Plain.  I like an HTML e-mail, it reminds me of a newsletter and I can jump around to the sections of the message I&#8217;m most interested in quickly.  With text e-mails, everything looks exactly the same and if I&#8217;m busy, I might delete it rather than scan through it to see if it interests me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Premick</title>
		<link>http://www.aweber.com/blog/email-deliverability/spamassassin-deliverability-tips.htm#comment-16842</link>
		<dc:creator>Justin Premick</dc:creator>
		<pubDate>Tue, 30 Oct 2007 18:51:50 +0000</pubDate>
		<guid>http://www.aweber.com/blog/email-deliverability/spamassassin-deliverability-tips.htm#comment-16842</guid>
		<description>Neil,

Your comment highlights a good point: not everyone prefers the same formatting on emails.

This is one reason why we emphasize that you should always include a plain text version when sending an HTML email. Some people prefer to read email in plain text (and may even turn off HTML in their email program).

With respect to your comment that &#34;email is intended to be plain text&#34; I have to disagree. I personally find well-formatted HTML messages easy to read and scan, and know that others also find the format preferable.

Moreover, if email were &#34;intended&#34; to be plain text, then it's unlikely that modern email clients such as AOL, Yahoo, Hotmail, Gmail, Thunderbird, Outlook, etc. would permit any HTML to be displayed in their programs. And as we all know, they do indeed permit HTML.

Different strokes for different folks.</description>
		<content:encoded><![CDATA[<p>Neil,</p>
<p>Your comment highlights a good point: not everyone prefers the same formatting on emails.</p>
<p>This is one reason why we emphasize that you should always include a plain text version when sending an HTML email. Some people prefer to read email in plain text (and may even turn off HTML in their email program).</p>
<p>With respect to your comment that &quot;email is intended to be plain text&quot; I have to disagree. I personally find well-formatted HTML messages easy to read and scan, and know that others also find the format preferable.</p>
<p>Moreover, if email were &quot;intended&quot; to be plain text, then it&#8217;s unlikely that modern email clients such as AOL, Yahoo, Hotmail, Gmail, Thunderbird, Outlook, etc. would permit any HTML to be displayed in their programs. And as we all know, they do indeed permit HTML.</p>
<p>Different strokes for different folks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neil</title>
		<link>http://www.aweber.com/blog/email-deliverability/spamassassin-deliverability-tips.htm#comment-16837</link>
		<dc:creator>Neil</dc:creator>
		<pubDate>Tue, 30 Oct 2007 17:37:37 +0000</pubDate>
		<guid>http://www.aweber.com/blog/email-deliverability/spamassassin-deliverability-tips.htm#comment-16837</guid>
		<description>You should discourage people from sending html in email. HTML is for web pages, email is intended to be plain text. Sending me html will get your email listed as spam faster than anything else. Let me reiterate EMAIL IS SUPPOSED TO BE PLAIN TEXT!!!!!</description>
		<content:encoded><![CDATA[<p>You should discourage people from sending html in email. HTML is for web pages, email is intended to be plain text. Sending me html will get your email listed as spam faster than anything else. Let me reiterate EMAIL IS SUPPOSED TO BE PLAIN TEXT!!!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Liddane</title>
		<link>http://www.aweber.com/blog/email-deliverability/spamassassin-deliverability-tips.htm#comment-16833</link>
		<dc:creator>Jim Liddane</dc:creator>
		<pubDate>Tue, 30 Oct 2007 15:50:19 +0000</pubDate>
		<guid>http://www.aweber.com/blog/email-deliverability/spamassassin-deliverability-tips.htm#comment-16833</guid>
		<description>Usually, our emails rate 0 on Spam Assassin.

However, occasionally, they rate an 0.5 with the accompanying note saying that the message &#34;contains a link to a likely spammer&#34;.

However, when you scroll through the message, no link is highlighted.

As we publish a newsletter, where members are allowed link their own sites, and provide links to sites they find useful, it is difficult to pinpoint which link is the offending one.

Does anybody have any idea how to do this?</description>
		<content:encoded><![CDATA[<p>Usually, our emails rate 0 on Spam Assassin.</p>
<p>However, occasionally, they rate an 0.5 with the accompanying note saying that the message &quot;contains a link to a likely spammer&quot;.</p>
<p>However, when you scroll through the message, no link is highlighted.</p>
<p>As we publish a newsletter, where members are allowed link their own sites, and provide links to sites they find useful, it is difficult to pinpoint which link is the offending one.</p>
<p>Does anybody have any idea how to do this?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
