<?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: Service Changes: Follow-up</title>
	<atom:link href="http://www.easyantispam.com/blog/2008/04/07/service-changes-follow-up/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.easyantispam.com/blog/2008/04/07/service-changes-follow-up/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Thu, 21 Aug 2008 20:09:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Javier</title>
		<link>http://www.easyantispam.com/blog/2008/04/07/service-changes-follow-up/#comment-921</link>
		<dc:creator>Javier</dc:creator>
		<pubDate>Tue, 08 Apr 2008 08:40:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.easyantispam.com/blog/2008/04/07/service-changes-follow-up/#comment-921</guid>
		<description>Hi George.

This change in billing strategy is a most dissapointing. Right now EAS doesn't give me tools to be able to analyze if I'll be impacted by this change:

- DomainProtect show absolutely no statistics whatsoever in the report center, so I'm totally blind on those domains
- ServerProtect packages domain detail report don't show a total message count, I have to add it myself
- Daily graphs show a spike on the last day of the month, so I'm told not to use them
- I'm left with a pie chart that I have to add up by hand to see how many messages the Server Protect is processing.

To be honest George, if your intention has always been to charge for overages (as stated in your earlier post), you should at least have the reporting tools ready so that we can make an informed decission and be able to manage the resources we have here.

We asked many times about the billing policy EAS had, and we were told repeatedly RBLs didn't count towards the total amount of messages processed by the system. We were also told that we should not be worried about the lack of statistics for Doman Protect packages as we would never be billed for overages. I think it's fair enough that, given EAS intention to charge for averages since the beginning, we should have been informed of this beforehand: "Look, we are not charging RBL now, but we intend to in the future".

I'm happy with the service you provide, except for a few quirks, everything has been running smoothly, but I've done some numbers and I just can't afford to pay the astronomical figures you're going to charge me in two months time.

I guess you'll be losing  me as a customer if you don't come up with a more flexible approach to base email messages allowed per package and overage limits.

Thanks for your time.</description>
		<content:encoded><![CDATA[<p>Hi George.</p>
<p>This change in billing strategy is a most dissapointing. Right now EAS doesn&#8217;t give me tools to be able to analyze if I&#8217;ll be impacted by this change:</p>
<p>- DomainProtect show absolutely no statistics whatsoever in the report center, so I&#8217;m totally blind on those domains<br />
- ServerProtect packages domain detail report don&#8217;t show a total message count, I have to add it myself<br />
- Daily graphs show a spike on the last day of the month, so I&#8217;m told not to use them<br />
- I&#8217;m left with a pie chart that I have to add up by hand to see how many messages the Server Protect is processing.</p>
<p>To be honest George, if your intention has always been to charge for overages (as stated in your earlier post), you should at least have the reporting tools ready so that we can make an informed decission and be able to manage the resources we have here.</p>
<p>We asked many times about the billing policy EAS had, and we were told repeatedly RBLs didn&#8217;t count towards the total amount of messages processed by the system. We were also told that we should not be worried about the lack of statistics for Doman Protect packages as we would never be billed for overages. I think it&#8217;s fair enough that, given EAS intention to charge for averages since the beginning, we should have been informed of this beforehand: &#8220;Look, we are not charging RBL now, but we intend to in the future&#8221;.</p>
<p>I&#8217;m happy with the service you provide, except for a few quirks, everything has been running smoothly, but I&#8217;ve done some numbers and I just can&#8217;t afford to pay the astronomical figures you&#8217;re going to charge me in two months time.</p>
<p>I guess you&#8217;ll be losing  me as a customer if you don&#8217;t come up with a more flexible approach to base email messages allowed per package and overage limits.</p>
<p>Thanks for your time.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
