We’re currently investigating an issue on the G1 gateway that is causing mail to not be delivered properly. It appears at this time that mail is queuing on the gateway and not being delivered to destination servers. We will be performing a database maintenance on the gateway to attempt to alleviate this issue.

We will update this post as soon as we have additional information.

Update: Database maintenance has completed and mail is flowing smoothly again. Please contact support@purity.net if you have any additional issues.

We’ve received reports from several customers that they’re having issues receiving email through the G1 gateway. Our initial investigation shows that G1 has been accepting mail but is possibly queuing mail before delivering to customer’s servers.

We’re doing further investigation at this time to determine a resolution to this issue and will update this post as we have more information. During our investigation there may be brief periods where G1 is unavailable due to reboots or other maintenance steps.  During any unavailability mail will queue at the sender’s server.

We apologize for any inconvenience this has caused.

Update at 7:38AM Central: We are running a database maintenance on G1 at this time to resolve issues with the internal databases. During this time G1 will not be available to receive mail. Mail will queue on the sender’s servers and be delivered after the maintenance has been completed. Unfortunately it is not possible to determine an ETA because database maintenance has a variable length. It is currently 25% complete. We will update this post when the status changes.

Update at 8:34AM Central: Database maintenance completed approximately 45 minutes ago and mail should be flowing normally at this time.  Any messages that were backlogged either have been delivered or will be delivered shortly. There is a large backup of quarantined mail waiting to be delivered to the Live Quarantine system which will take time to catch up.  Please contact support@purity.net if you are still seeing issues, but at this time mail appears to be flowing smoothly.  We will continue to monitor the situation.

This morning we are experiencing queuing of email on the G1 gateway. We are performing an emergency database maintenance cycle to attempt to mitigate the situation. The ETA for resolution at this time is unknown.

UPDATE: During this maintenance there may be periods of time where the G1 gateway is unavailable to accept connections. This will cause mail to queue on the sender’s server and be retried at a later time according to their settings.

UPDATE 11:40AM: Database maintenance is complete and mail appears to be flowing properly again. Please note that it may take some time for mail flow to return to normal as the gateway has a backlog of mail to process. We apologize for any inconvenience this might have caused!

Mailfoundry engineers have temporarily taken the G1 gateway offline as they investigate an issue causing some mail to get stuck in queue.  We expect services to be restored shortly but currently do not have an ETA.  At this time mail will queue on the sending server and will be delivered after G1 comes back online and the sender retries.

Update: G1 is back up and performing normally.

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.