Thank you all for making 2009 such a great year for us! We’re looking forward to continuing to help you keep your mailboxes clean in 2010.

In the next couple of weeks we’ll be releasing the new API version 2.0, which will make integrating Purity Networks services with your infrastructure much easier. Keep an eye out over the next couple of months for some really exciting integration news as well!

Over the next 6 months we’ll be launching some great new services, upgrading our filtering technology significantly and expanding our infrastructure as well. We’ll keep you all in the loop here on the blog, but be sure to let us know if you have any ideas for new features or services you’d like to see from us!

We wish you all a Happy New Year and hope that it brings you much joy and prosperity!

I want to take a quick moment and wish everyone a Merry Christmas and Happy Holidays from Purity Networks!  We thank you for your business and look forward to reducing the junk in your email for another great year in 2010.

Due to the holiday season, our telephone support will be closed on:

Saturday, December 25, 2009
Friday, December 31, 2009
Saturday, January 1, 2009

Our support and billing departments will still be answering tickets, though responses may be more delayed than usual. Please note that we still abide by our 24-hour response time guarantee, even on holidays.

Our sales department will be closed on the above specified dates.  Inquiries to our sales@purity.net email address will be addressed on the following business day.

Once again, thank you for your business and Merry Christmas and Happy Holidays!

Just a quick note to let everyone know that we’ve made some visual changes to the ReportCenter functionality of our Account Manager, making the graphs quite a bit easier to decipher as well as better color coding.

Over the next few weeks you’ll see some more changes, most notably behind the scenes with the report data itself.  We’re working on expanding the data that we capture and have available for reporting as well as fixing some issues with the data that we’re gathering currently.  We’ll likely also be adding some additional graphs and reports to the ReportCenter.

Have ideas for data you’d like to see, or different ways to present data?  Comment on this post or email us at support@purity.net so that we can take the ideas and suggestions into account as we build out new reporting features.

With the release of UserProtect, we’re working on a new version of the Purity Networks API to incorporate functionality to work with UserProtect and DomainProtect accounts.  We’re still in the early design and development stage, but we’ve started working on the documentation on the Wiki at the same time to give our users input into the design.

Please see the new wiki section to take a look at what we’re working on.  The new version of the API is not going to be a SOAP API like version 1.0 is.  It’s going to be a RESTful API, which is much easier to work with.

Please give us as much feedback as you can so that we can take it into account as we develop the new version of the API.  Have thoughts or comments?  Let us know in the comment section below or in the discussion section on the wiki page.

We’re happy to announce that our new UserProtect service is now available for ordering! See our services page for detailed information.

We’re working on a new version of our API that will include UserProtect functionality, but at the moment it’s not available yet.  We’re hoping to have this available for use in the next couple of weeks.

Please be sure to let us know what you think about the new UserProtect service!

This is just a reminder to check the Catch-all Report under the Tools menu in the Account Manager to see if you have any domains that have catch-alls enabled.  Purity Networks does not support domains with catch-alls enabled.

We have not been running the automatic disable process that will disable these domains for some time, but we will be starting to run this process again on 10/10/2009.  If you have not taken care of the issue before then, any domains that have catch-alls enabled will be disabled and mail will no longer be accepted for them.

For more information on catch-alls and why we don’t allow them, see this knowledgebase article and this knowledgebase article. For Exchange users, please see this knowledgebase article on how to properly configure Exchange to reject invalid users at the SMTP transaction level.