Service Changes: Follow-up
by George RobertsWe had a couple people contact us with concerns about their number of messages and I just wanted to clarify a couple of things.
If you’re looking at your reporting and seeing a large spike on the last day of each month, this is a known issue. The report data that we get from the MailFoundry appliances has a bug in it when sending daily reports in that it sends the complete month’s data on the last day instead of just the daily totals for that day. Until this bug is fixed we will simply be discarding the last day of the month from the totals we use for overage billing. To see what type of totals you generated for March, for example, set the end date to March 30th.
The second issue is in the “totals over time” graph in the bottom right. These numbers are WAY out of whack. This is a bug on OUR end, not MailFoundry’s. I’m trying to track it down and get those numbers fixed, but in the meantime, please ignore those numbers. The easiest way to total up your usage is to total up the slices of the pie chart in the upper left until I get the monthly totals graph fixed.
We’ve had requests for additional reporting data. It’s high on my list of things to do. If you have ideas for reports, changes to the existing reports such as how the data is presented, etc., please contact support@interjuncture.com so that we can take them into consideration as we expand our reporting.
April 8th, 2008 at 2:40 am
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.