Some of you have reported issues with the new Account Manager when using IE7.  I’m happy to let you know that the problem has been fixed…  and it was caused by a single errant comma in the javascript code.  Funny how one little comma can cause so many problems, eh?

We’re experiencing some caching of mail on our gateways at this time due to what appears to be a bad spam or virus definition.  MailFoundry techs are currently working to resolve the issue as quickly as possible.  We will post again when we have an update, which should be shortly.

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.

For those that have contacted us regarding not receiving quarantine digests since the server upgrade, thank you.  Digests have been fixed.  In fact, you should have just received a very long digest.

I won’t get too technical but essentially the problem was that as we migrated to the new server we took a little time to put into place a database change we had been working on to make the quarantine databases more efficient.  This change required us to make changes in our quarantine system code.  Unfortunately, the code we changed in the digest process had a problem with it and it has taken us a bit to track down the bug and squash it.

Thank you for your patience, but I believe that was the last migration-related issue we had left to fix.  If you know of any other problems, please let us know.

We need to run a database check on MF1 and MF2 today.  This may cause some messages to be delayed, but no mail will be lost.

We will post again when this is completed.