We are currently performing emergency database maintenance on the MF1 gateway to address an issue that was causing errors in mail delivery.

ETA: Unknown – database maintenance times can vary, though it should be complete within the next couple of hours

Mail Delivery Status: Mail will be queued on the sender’s server and will be delivered once mail services restart after the database maintenance

We will update this post as soon as the issue has been corrected.

Update 9:22PM Central: After further investigation it was determined that mail services on all three of our gateways was impacted for approximately 1 hour and 20 minutes this evening due to issues with the DNS servers that our gateways use to resolve IPs.  This issue caused our gateways to be unable to resolve IP addresses properly causing mail to not be able to be delivered properly.

We have since changed to different DNS servers for resolution, resolving the issue.  MF1 continues to work on its database maintenance but mail is being delivered as it works.  Customers on MF1 may notice a slight delay in delivery times as the database maintenance completes.

During the outage emails destined for customer servers will have queued on the sending servers and should be delivered as those servers retry at a later time.

Our apologies for this situation! Due to the length of the outage we will be crediting all customers 5% of their monthly service charges which will be applied against your next bill. Please contact us if you have any questions.

We moved our DNS servers several weeks ago, but apparently one of the OpenDNS servers had the wrong information cached. This was rectified a couple of days ago, which is why we are seeing these problems today.  Now, there are several senders that still have bad DNS information cached.  If you are not receiving messages from some senders, be sure to notify them that they need to update their DNS cache.

Here is how the sender can find out if their cache is bad:

The sender’s system administrator needs to do a lookup on their mail server to see what IP address they’re getting for our gateway. Additionally, it would be helpful if they could get us the nameserver records they’re seeing for ijnet.net as well.

Examples:

On windows:

nslookup -type=a g1.ijnet.net
nslookup -type=ns ijnet.net

On linux:

dig g1.ijnet.net a
dig ijnet.net ns

Our correct IP’s are:

MF1 – 216.246.89.41

MF2 – 216.246.89.42

G1 – 216.246.89.40

G2 – 216.246.89.37

As always, if you have any questions, feel free to contact us at support@purity.net.

Thank you for choosing Purity Networks.

Having been in the antispam business for a little over four years, we have become very familiar with the various and numerous methods by which spammers try to foil email security systems.  With this key industry knowledge, we believe that we have been given the opportunity to be of service such as few others can.

Over the next couple of weeks, you will see us roll out a new set of services that will allow our customers to promote their services to our enormous database of email addresses.  Due to our understanding of antispam techniques, we will be able to guarantee virtually 100% delivery, thusly increasing your sales.

We know this is an extremely abrupt shift in business practices, but in these rough economic times, we need to take it where we can get it.

Please watch this blog for additional announcements in the near future.

The database maintenance for MF1 and MF2 is complete, and normal mail flow has resumed.  We apologize for any inconvenience.

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.