<?xml version="1.0" encoding="ISO-8859-1"?><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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: Confirmed Opt-In Protects Against Spamza and Other Malicious Sites</title>
	<atom:link href="http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm/feed" rel="self" type="application/rss+xml" />
	<link>http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm</link>
	<description>Email Marketing Tips and Best Practices: AWeber Blog</description>
	<lastBuildDate>Wed, 15 Feb 2012 14:21:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
	<item>
		<title>By: Do This! (Not That) For Better Email Delivery</title>
		<link>http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm/comment-page-1#comment-71543</link>
		<dc:creator>Do This! (Not That) For Better Email Delivery</dc:creator>
		<pubDate>Fri, 17 Jun 2011 13:49:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm#comment-71543</guid>
		<description>[...] the subscriber. But if you don&#8217;t have confirmed opt in on, you run the risk of again getting bad email addresses on your list. You&#8217;ll also open yourself up to more spam complaints, and subscribers who [...]</description>
		<content:encoded><![CDATA[<p>[...] the subscriber. But if you don&#8217;t have confirmed opt in on, you run the risk of again getting bad email addresses on your list. You&#8217;ll also open yourself up to more spam complaints, and subscribers who [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What to Do About Low Email Delivery Rates</title>
		<link>http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm/comment-page-1#comment-70825</link>
		<dc:creator>What to Do About Low Email Delivery Rates</dc:creator>
		<pubDate>Mon, 13 Jun 2011 14:08:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm#comment-70825</guid>
		<description>[...] Protect Against Malicious Sign Ups [...]</description>
		<content:encoded><![CDATA[<p>[...] Protect Against Malicious Sign Ups [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Koning</title>
		<link>http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm/comment-page-1#comment-40157</link>
		<dc:creator>Peter Koning</dc:creator>
		<pubDate>Wed, 10 Sep 2008 20:03:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm#comment-40157</guid>
		<description>Re the single optin that&#039;s hanging around, and moving subs from one list to another, I like the API idea. What I suggest is that the option to send an email to my-cust-list@aweber.com be used for this API.

The my-cust-list would be single optin and ONLY allowed for moving already subscribed COI subs from one list to another.

I also suggest that single optin ONLY be allowed for this purpose - i.e. to process subscribers who are already COI.

So single optin forms for new subs could be phased out and aweber would only be allowing COI for ALL lists and all customers. That should improve deliverability for all of us while solving the need for an API - we could simply have an email sent by our order handling scripts to my-cust-list@aweber. 

Maybe some parsing would be needed to pick out the person&#039;s email address, but you have parsers for that.</description>
		<content:encoded><![CDATA[<p>Re the single optin that&#8217;s hanging around, and moving subs from one list to another, I like the API idea. What I suggest is that the option to send an email to <a href="mailto:my-cust-list@aweber.com">my-cust-list@aweber.com</a> be used for this API.</p>
<p>The my-cust-list would be single optin and ONLY allowed for moving already subscribed COI subs from one list to another.</p>
<p>I also suggest that single optin ONLY be allowed for this purpose &#8211; i.e. to process subscribers who are already COI.</p>
<p>So single optin forms for new subs could be phased out and aweber would only be allowing COI for ALL lists and all customers. That should improve deliverability for all of us while solving the need for an API &#8211; we could simply have an email sent by our order handling scripts to my-cust-list@aweber. </p>
<p>Maybe some parsing would be needed to pick out the person&#8217;s email address, but you have parsers for that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derrick</title>
		<link>http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm/comment-page-1#comment-40155</link>
		<dc:creator>Derrick</dc:creator>
		<pubDate>Wed, 10 Sep 2008 18:49:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm#comment-40155</guid>
		<description>I agree with Gobala. If you are in direct marketing, you want a completely different followup series going out to customers and you want to remove them from your prospect list.

In addition, you can&#039;t force your customers to confirm by withholding their product like you can with a freebie. 

You could offer an unadvertised bonus. But there will still be a number of customers who won&#039;t take that extra step.

I would like to see some kind of API that you could use remotely to MOVE a prospect to a customer list automatically after a sale.

If they&#039;ve already given you permission to send them email, moving them to a different list would not violate their rights. It would only serve to stop additional email offers for the same product.</description>
		<content:encoded><![CDATA[<p>I agree with Gobala. If you are in direct marketing, you want a completely different followup series going out to customers and you want to remove them from your prospect list.</p>
<p>In addition, you can&#8217;t force your customers to confirm by withholding their product like you can with a freebie. </p>
<p>You could offer an unadvertised bonus. But there will still be a number of customers who won&#8217;t take that extra step.</p>
<p>I would like to see some kind of API that you could use remotely to MOVE a prospect to a customer list automatically after a sale.</p>
<p>If they&#8217;ve already given you permission to send them email, moving them to a different list would not violate their rights. It would only serve to stop additional email offers for the same product.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gobala Krishnan</title>
		<link>http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm/comment-page-1#comment-40120</link>
		<dc:creator>Gobala Krishnan</dc:creator>
		<pubDate>Sun, 07 Sep 2008 03:42:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm#comment-40120</guid>
		<description>To Chris - I think having a single-optin helps in some cases and Aweber should allow it. 

I used it mainly to register customers after purchase, and remove them from the non-customer list (automation). The non-customers / subscribers have already double-optin so when they buy I just get a single optin. 

I need to remove as many customers as possible from the non-customer list to ensure I don&#039;t send a promotion / offer to someone who just bought a product a few minutes ago. 

I think Aweber should maintain the single optin feature. Besides if im not mistake the moment an email bounces a few times or is flagged by the user as SPAM, it&#039;s automatically removed from my list.</description>
		<content:encoded><![CDATA[<p>To Chris &#8211; I think having a single-optin helps in some cases and Aweber should allow it. </p>
<p>I used it mainly to register customers after purchase, and remove them from the non-customer list (automation). The non-customers / subscribers have already double-optin so when they buy I just get a single optin. </p>
<p>I need to remove as many customers as possible from the non-customer list to ensure I don&#8217;t send a promotion / offer to someone who just bought a product a few minutes ago. </p>
<p>I think Aweber should maintain the single optin feature. Besides if im not mistake the moment an email bounces a few times or is flagged by the user as SPAM, it&#8217;s automatically removed from my list.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Brisson</title>
		<link>http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm/comment-page-1#comment-40113</link>
		<dc:creator>Chris Brisson</dc:creator>
		<pubDate>Fri, 05 Sep 2008 18:31:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm#comment-40113</guid>
		<description>By having this post is actually a bad thing. Now that all aweber users have now heard about it, many will USE it. 

I would recommend taking this post down. It just brings more attention to something that none of us need more of.

This post may do more wrong than good and in the end what is the main purpose of this post?

Just my opinion.</description>
		<content:encoded><![CDATA[<p>By having this post is actually a bad thing. Now that all aweber users have now heard about it, many will USE it. </p>
<p>I would recommend taking this post down. It just brings more attention to something that none of us need more of.</p>
<p>This post may do more wrong than good and in the end what is the main purpose of this post?</p>
<p>Just my opinion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Premick</title>
		<link>http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm/comment-page-1#comment-40112</link>
		<dc:creator>Justin Premick</dc:creator>
		<pubDate>Fri, 05 Sep 2008 14:07:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm#comment-40112</guid>
		<description>Peter, Jonathan, Carol,

I agree - that&#039;s a cool idea. Looking into it :)</description>
		<content:encoded><![CDATA[<p>Peter, Jonathan, Carol,</p>
<p>I agree &#8211; that&#8217;s a cool idea. Looking into it <img src='http://blog-cdn.aweber-static.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gobala Krishnan</title>
		<link>http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm/comment-page-1#comment-40110</link>
		<dc:creator>Gobala Krishnan</dc:creator>
		<pubDate>Fri, 05 Sep 2008 06:22:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm#comment-40110</guid>
		<description>I used to do single optin - more subscribers, better for the ego :) 

No anymore though.</description>
		<content:encoded><![CDATA[<p>I used to do single optin &#8211; more subscribers, better for the ego <img src='http://blog-cdn.aweber-static.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  </p>
<p>No anymore though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carol Bentley</title>
		<link>http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm/comment-page-1#comment-40094</link>
		<dc:creator>Carol Bentley</dc:creator>
		<pubDate>Wed, 03 Sep 2008 21:55:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm#comment-40094</guid>
		<description>Yep!  Count me in favour of that &#039;badge idea&#039;.  Aweber has such a good reputation it would be good to demonstrate the ethics we follow by using your services.</description>
		<content:encoded><![CDATA[<p>Yep!  Count me in favour of that &#8216;badge idea&#8217;.  Aweber has such a good reputation it would be good to demonstrate the ethics we follow by using your services.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm/comment-page-1#comment-40093</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 03 Sep 2008 21:05:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.aweber.com/blog/email-deliverability/confirmed-opt-in-protects-against-spamza.htm#comment-40093</guid>
		<description>After reading this blog entry, one thought comes to mind... why in the world would AWeber allow *ANY* of their customers to operate a non-COI mailing list? I&#039;m asking an honest question. Doesn&#039;t AWeber bare some degree of responsibility (and liability) for offering a non-COI mailing list option? Please list the &quot;benefits&quot; that an AWeber customer gets by choosing to configure a mailing list that doesn&#039;t have confirmation turned on for web forms. Can you list ANY benefit at all that outweighs the risks that have been outlined in numerous blog posts? Didn&#039;t think so. The fact that AWeber even allows their customers to bypass COI with web based forms is a joke, and I think you guys know it too. So can you please stop preaching about the benefits of COI, and flip the switch once and for all that makes AWeber a 100% COI e-mail service provider?</description>
		<content:encoded><![CDATA[<p>After reading this blog entry, one thought comes to mind&#8230; why in the world would AWeber allow *ANY* of their customers to operate a non-COI mailing list? I&#8217;m asking an honest question. Doesn&#8217;t AWeber bare some degree of responsibility (and liability) for offering a non-COI mailing list option? Please list the &quot;benefits&quot; that an AWeber customer gets by choosing to configure a mailing list that doesn&#8217;t have confirmation turned on for web forms. Can you list ANY benefit at all that outweighs the risks that have been outlined in numerous blog posts? Didn&#8217;t think so. The fact that AWeber even allows their customers to bypass COI with web based forms is a joke, and I think you guys know it too. So can you please stop preaching about the benefits of COI, and flip the switch once and for all that makes AWeber a 100% COI e-mail service provider?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Content Delivery Network via blog-cdn.aweber-static.com

Served from: www.aweber.com @ 2012-02-15 19:46:19 -->
