We’re ready for a few testers to give the API some work and give us some feedback on it.

We have the following functions done:

listDomains

Lists domains assigned to the specified server

addDomain

Adds a domain to the specified server

addDomainAlias

Adds an alias domain to the specified domain

deleteDomain

Deletes the specified domain

deleteDomainAlias

Deletes the specified alias domain from the specified domain

listDomainAliases

Returns a list of alias domains associated with the specified domain

If you’re interested in helping us test the API, please contact support.

Hi everyone,

We’ve been doing some work on the Account Manager API and I’d like some feedback on what everyone feels they need as far as functionality in the API.  First, let me say that at this time we’re only planning on implementing an API for ServerProtect accounts.  We may add some DomainProtect functionality at a later point, but we’re concentrating on basic add/delete/list type functionality for ServerProtect accounts at this time.

Currently, we have the following working:

listDomains – Returns a comma-separated list of domains mapped to the specified server
addDomain – Add a domain to the system, mapped to the specified server

We’ll have a deleteDomain function ready to go shortly as well.

So, after those three functions, what else is needed?

The API is implemented as a SOAP web service.  We’ll have easy to use PHP examples available when we release the API.

Just a quick post to let you know some of the plans for our infrastructure as they stand right now.  We’re open to thoughts and comments on these plans.  We think they’re solid, but other sets of eys/thoughts may come up with something we haven’t thought of.

We’re currently in the process of building out what we call our Edge, which is a multiple server cluster of servers which will handle RBL checking.  The servers that make up this cluster are virtual instances that are part of a grid.  We will be able to automatically add/remove instances to the grid as load requires.  They will be accessed via DNS round robin to distribute load across the cluster.  Messages that pass the RBL checks will be delivered to the appropriate MailFoundry appliance for additional checks.  Messages that pass those checks will then be delivered to your mail server.

We’re also in the planning states of building out a Backup MX service, which will have MailFoundry appliances located at a separate datacenter facility and will be served by a second Edge cluster.  This will be an add-on service, likely for $20-25 per month per ServerProtect account and $2-3 per DomainProtect account.

The primary Edge is up right now and we’re doing testing on it.  We’ve still got some work to do on it, building some reporting tools for it as well as the monitoring and automatic scaling system.  We don’t have a specific release date for it yet, but we’re hoping to have it ready for customer testing within the next few weeks.  The backup Edge will be easy, since it will essentially be a duplicate of the primary with different targets for the MailFoundry appliances.

The Backup appliances and infrastructure are still being planned.  We’re researching datacenters right now.  We’re thinking it will be a couple of months before we’re ready to go with this service.

Any thoughts and ideas are welcome.

Just a quick update on the plans for overage billing.  It’s likely we’ll push this back a month or two because of a couple things:

1) We’re still developing our new billing system.  And while it will probably be ready in time for the July billing cycle, we want to make sure everything is working properly before we add another facet to the billing.

2) As most of you know, there’s an issue with the reports we receive from the MailFoundry appliances on the last day of the month.  We’re waiting on a fix from MailFoundry which is supposed to come out with the next release of the appliance software, but we don’t have a specific date on that release yet.

3) We’re making some pretty extensive changes to our infrastructure over the next couple of months.  This will change how we collect some of the reporting data and we want to make sure we have that up and running and working properly before we start billing for overages. (More on the infrastructure changes in a follow-up post).

If you have any questions, please let us know.

Last night we experienced a complete infrastructure power outage due to a problem with a power distribution unit that delivers power to our cabinet at our datacenter.  Unfortunately, it took some time to diagnose exactly what particular piece of equipment was causing the problem and then to resolve the issue.

The problem has been resolved at this time, however, we will need to schedule a short downtime in the next week or so to upgrade a piece of power hardware to reduce the chances of an outage like this happening again in the future.

By way of apology for the extended downtime, we will be issuing $10 service credits for all ServerProtect customers and $2 service credits for all DomainProtect customers.  This credit will appear in your account in the next week or so.

Ken returns!  It’s the Spamfighters Podcast, Episode 7.

Spamfighters Episode 7 [ 4:57 ] Play Now | Play in Popup | Download (1057)