We are currently performing emergency database maintenance on the G1 gateway to repair a corrupted user database. We estimate a total time for repair of 30-60 minutes. During a portion of this time SMTP services on G1 will be disabled. Sending servers will queue the mail until services are restored and will deliver at that time.
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.
Our G1 gateway has completed database maintenance, and normal mail flow has resumed.
Our G1 gateway began experiencing issues sometime around 8:00 am CST today. We did not become aware of the issue until 10:30 this morning, and once we knew there was a problem we began taking the necessary steps to fix it. Apparently there was a database error in the gateway that began causing all mail to be put into an unscanned queue and not processed. The gateway is currently undergoing database maintenance, and should be back up and running within the hour.
We apologize for the inconvenience this has caused, and we thank you for choosing Purity Networks.
An index file of the accepted user list in our G1 gateway’s database became corrupted. This is causing all incoming mail to be temporarily put into an “Unscanned” queue. At the very worst, some messages may be bounced to the sender. We are currently working with MailFoundry to get this issue resolved, and it should be fixed soon.
