Is Autopinger flying on auto-pilot?

by Maskil on April 17, 2008

In an earlier posting, I mentioned the issues I’ve been encountering with the Autopinger blog ping service. My last action was to make use of the “E-mail Administrator” function, which generated an e-mail message to ‘vinson@autopinger.com’. At that stage, I hadn’t received a response from the administrator. In my Inbox this morning, however was a “Delivery Status Notification (Delay)” for the message. While there may well be a valid technical reason for the delay, this does not bode well for Autopinger.

From: Mail Delivery Subsystem [mailto:mailer-daemon@googlemail.com]
Sent: Thursday, April 17, 2008 12:44 AM
To: *@gmail.com
Subject: Delivery Status Notification (Delay)
This is an automatically generated Delivery Status Notification
THIS IS A WARNING MESSAGE ONLY.
YOU DO NOT NEED TO RESEND YOUR MESSAGE.
Delivery to the following recipient has been delayed:
vinson@autopinger.com
Message will be retried for 2 more day(s)
Technical details of temporary failure:
TEMP_FAILURE: The recipient server did not accept our requests to connect. Learn more at http://mail.google.com/support/bin/answer.py?answer=7720
[mail.autopinger.com. (10): Connection dropped]
—– Message header follows —–

The Help Center topic referenced reads as follows:

‘The recipient server did not accept our requests…’
This error message indicates that we’ve attempted to make a connection with your recipient’s server but didn’t receive a reply. Some possible causes include the following:
* The other domain doesn’t have up-to-date MX records or is otherwise misconfigured.
* The other domain is blacklisting or graylisting messages from Gmail.
* The other domain is experiencing temporary networking problems.
We recommend contacting the customer service department of the recipient’s domain for further instructions. If you receive this bounce message when sending to your Google Apps domain, please see our instructions for configuring your MX records.

Related posts:

Share

Previous post:

Next post: