Posted on 05/25/2010 9:09:19 AM PDT by butterdezillion
I’ll pass on the advice to my husband since he’s the computer expert in the household. He knows what we’ve been through.
I have another question regarding my mail. This morning I sent an e-mail to someone I’ve been conversing with rather intensely about the eligibility issue and the strategy to use what I have for real, legal results. Three hours and twenty minutes after I sent the e-mail my ISP kicked back an auto response saying they couldn’t deliver my e-mail to that address; they said it was a permanent error. But it’s the same address I’ve been e-mailing to all along and the person contacted me through the blog this afternoon without mentioning anything about changing e-mail addresses. He’s wondering if I’ve gotten his e-mail. The last e-mail I sent him was using my daughter’s e-mail yesterday, and I was able to receive e-mail from him through that yesterday as well.
Is it normal for it to take the system almost 3 1/2 hours to decide it can’t deliver a message? I’ve always gotten undeliverable notifications instantly, until this.
Does somebody have the power to cut off my communications to just certain e-mail addresses? If so, who would have that kind of power?
“who would have that kind of power?”
Any mail server on the planet.
From: http://support.microsoft.com/kb/284204
Non-delivery reports (NDRs) are system messages that report the delivery status of a message to the sender. The messages are a subclass of a general message information structure that is referred to as delivery status notifications. Delivery status notifications describe three different types of situations:
Success (2.X.X numeric codes)
Persistent transient failure (4.X.X numeric codes)
Permanent failures (5.X.X numeric codes)
To learn more about delivery status notifications, see Request for Comment (RFC) 1891 and RFC 1893.
NDRs are generated whenever a message cannot be delivered. If the computer can detect the reason for the failed delivery, it maps the reason onto a status code, and a corresponding error message is printed. (To see a list of these codes, see RFC 1891 and RFC 1893.) For NDRs, most numeric codes are reported in the form of 5.X.X and are described as permanent failures. However, there are certain transient conditions that cause 4.X.X codes.
Note that the server that is reporting the problem is listed before the numeric code. In the example NDR in the “Introduction” section, the reporting server is server.nwtraders.com. Sometimes the server that is reporting the problem is not the server that is actually experiencing the issue.
One simple possibility:
Numeric Code: 5.2.2
First Available: Exchange 2000 Service Pack 3 (previously 4.2.2 in earlier release).
Possible Causes: The recipient’s mailbox is over its storage limit.
Troubleshooting: Verify the mailbox storage and the queue storage quota limit.
what HE said.
Can a mail server just refuse to deliver a certain e-mail, without there being technical issues such as an already-full inbox, etc? Is there a way to find out where the problem is coming from?
Check the e-mail for an NDR code, maybe it gives you a reasonable explanation.
And try the e-mail again in a day or so. Sometimes these things just happen.
My NDR didn’t include a server or a code. It said:
>>>>>>>>
This message was created automatically by the Windstream mail system.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
——— This is a copy of the headers of the original message. ———
Return-Path: (redacted)
X-WS-COS: (redacted)
X-Cloudmark-Category: Undefined:Undefined
X-Cloudmark-Analysis: (redacted)
X-Cloudmark-Score: 0
Authentication-Results: (redacted)
Received: from (redacted) by (redacted)
(redacted 2.2.2.45 r()) with ESMTPA
id redacted;
Wed, 26 May 2010 08:26:16 -0400
Message-ID: (redacted)
From: “Nellie” (redacted)
To: (redacted)
References: (redacted)
Subject: (redacted)
Date: Wed, 26 May 2010 07:26:05 -0500
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset=”iso-8859-1”;
reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
Nothing jumps out as alarming, though.
Try it again tomorrow.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.