Undeliverable mail

[Harmon Koeltz]

Hello
I have this sporadic problem on a computer running Vista Home Premium and
Outlook 2007. Occasionally, when I send an email to an address I have used
frequently, I will receive a message that the email was not delivered
because the "destination computer was not found." This occurs randomly to
some Yahoo acounts as well as some where the ISPs name is part of the
address. My software is up to date as is my A/V software. Additionally, the
undeliverable message arrives as much as twelve hours after sending the
email. Sometimes, but not always, a new message to the same address goes
through.

Thanks

Harmon

 

[VanguardLH]

in message

Occasionally, when I send an email to an address I have used
frequently, I will receive a message that the email was not
delivered because the "destination computer was not found.".

Do not descibe an error message. Do not summarize an error message.
SHOW the entire error message by copy-and-paste or transcribe it
verbatim. For an NDR (non-delivery) report, it would also help if you
show the entire e-mail, including the headers (but munge out your
username or e-mail address) so respondents can verify from whom the
NDR was sent.

Additionally, the undeliverable message arrives as much as twelve
hours after sending the email. Sometimes, but not always, a new
message to the same address goes through.

Again, having the FULL content of the NDR (and headers) could help in
determing what was really going on; otherwise, you present a vague
situation which results in vague responses.

The extended delay could be that the mail host for the recipient is
undergoing maintenance or is otherwise ****ed up. It happens. You
did not mention over how long this problem has occurred.

The recipient might also have greylisting, if available, enabled on
their account. So whether or not your e-mail gets delivered depends
on how well your mail host handles re-sending of e-mails. If
available, greylisting help eliminate spam because the mailer trojan
on infected user hosts will not retry sending their crap. See
http://en.wikipedia.org/wiki/Greylisting.

 

[Brian Tillman]

I have this sporadic problem on a computer running Vista Home Premium
and Outlook 2007. Occasionally, when I send an email to an address I
have used frequently, I will receive a message that the email was not
delivered because the "destination computer was not found."

That's a routing or domain name service issue and since you didn't include
the exact text of the error, it's not really possible to state whether or
not you can address it.

 

[Harmon Koeltz]

That's a routing or domain name service issue and since you didn't include
the exact text of the error, it's not really possible to state whether or
not you can address it.

Sorry
Here is an exact copy of the message with the recipient's name x'd out:

This Message was undeliverable due to the following reason:



Your message was not delivered because the destination computer was not
found. Carefully check that it was spelled correctly and try sending it
again if there were any mistakes.



It is also possible that a network problem caused this situation, so if you
are sure the address is correct you might want to try to send it again. If
the problem continues, contact your friendly system administrator.



The following recipients did not receive this message:



<************@bellsouth.net>



Please reply to (e-mail address removed)

if you feel this message to be in error.





The recipients have all received emails from me before and after these
events.



Thanks



harmon

 

[Brian Tillman]

Here is an exact copy of the message with the recipient's name x'd
out:
This Message was undeliverable due to the following reason:
Your message was not delivered because the destination computer was
not found.

This says that the router at charter.net, your ISP, could not find a mail
destination for the address you supplied for that particular message. This
occurred after the message left your PC and arrived at Charter's mail
router, so you cannot affect the problem. It appears to me to be an
intermittent domain name service problem on Charter's end.