Returned E-mail

Why didn't my e-mail get there?

At NexLAN, we pride ourselves on providing reliable, consistent e-mail services, supported by a staff of expert troubleshooters who are ready to help you quickly resolve any issues you may have along the way.

When you send an e-mail through your NexLAN-hosted account, there are times that you will receive a message from "Mailer-Daemon," explaining that your mail is undeliverable or delayed.  Sometimes this is an issue on the sending server (i.e. NexLAN) side of things, but often it's an issue on the receiving end.

Before you give us a call, check your "bounced-back" message against this list of frequent issues.  If you still can't resolve what happened, please forward the bounced-back message to us at nexlan@nexlan.com.  In addition to deciphering the Mailer-Daemon messages, we can dig through our mail server logs and help piece together exactly what happened.


Scenario 1: Mailbox is full

From: Mail Delivery System [mailto:Mailer-Daemon@thisdomain.net]
Sent: Friday, November 12, 2005 8:37 AM
To: you@yourdomain.com
Subject: Mail delivery failed: returning message to sender 

This message was created automatically by mail delivery software.

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:

  adam@thisdomain.net
    mailbox is full

------ This is a copy of the message, including all the headers. ------

The above original message will not reach its intended recipient (adam@thisdomain.net).  The reason is in the third paragraph.  Quite simply, the mailbox is full.  The recipient needs to delete messages from his/her account to make room for your message and any other incoming mail.

 

Scenario 2: User unknown

The original message was received at Wed, 01 Dec 2004 16:01:32 -0600

----- The following addresses had permanent fatal errors ----- <brent@thisdomain.net>

----- Transcript of session follows ----- ... while talking to smtp.thisdomain.net

>>> RCPT To:<brad@thisdomain.net>
<<< 550 5.0.0 <brad@thisdomain.net>... User Unknown

This message also will not reach its intended recipient (brent@thisdomain.net).  The last line of the message explains that the user is unknown.  Check that you haven't made a typo in the email address.  If there are no errors, the account may have been closed. 

 

Scenario 3: Domain not found

The original message was received at Wed, 17 Aug 2005 12:17:51 -0500

----- The following addresses had permanent fatal errors ----- <clara@thisdomaine.net>

----- Transcript of session follows ----- ... while issuing MX query to

554 DNS server responded with 3 (Domain Not Found)

This message failed to be delivered due to a mistyped domain name (i.e. thisdomaine.net vs. thisdomain.net).  There was no mail server associated with the domain ("MX query"), and the message was returned.  This message must be resent to the correct domain.

 

Scenario 4: Non-Fatal Errors

-----Original Message-----

From: Mail Delivery Subsystem [mailto:MAILER-DAEMON@nexlan.net]

Sent: Tuesday, January 10, 2006 3:06 PM

Subject: Warning: could not send message for past 4 hours

 

**********************************************

** THIS IS A WARNING MESSAGE ONLY **

** YOU DO NOT NEED TO RESEND YOUR MESSAGE **

**********************************************

 

The original message was received at Tue, 10 Jan 2006 15:05:54 -0600

----- The following addresses had transient non-fatal errors -----

<dave@thisdomain.net>

----- Transcript of session follows -----

Warning: message still undelivered after 4 hours Will keep trying until message is 2 days old

This message will continue to attempt to be delivered to the recipient.  It is merely a warning message, explaining that it has not yet arrived.  There are many explanations for receiving this message:

  1. An issue on the sending server.
  2. An issue on the receiving server.
  3. An issue with the two communicating.

Often this delayed message will be followed by a message notifying  you that delivery of the email ultimately failed.  We suggest re-sending the message and seeing if it "goes through" the second time around without any problems or delay.

 

Scenario 4: 4.4.7 Error

-----Original Message-----

From: Mail Delivery Subsystem [mailto:MAILER-DAEMON@nexlan.net]

Sent: Thursday, August 3, 2006 3:06 PM

Subject: Undeliverable: (subject of original message)

Your message did not reach some or all of the intended recipients.
Subject: Subject_Of_Original_Message
Sent: DateTime
The following recipient(s) could not be reached:
'Recipients_Name' on DateTime
Could not deliver the message in the time limit specified. Please retry or contact your administrator.
<FQDN_Of_Sending_Server#4.4.7>

A 4.4.7 NDR message usually indicates a problem on the receiving server. Check the validity of the recipient's address, as well as whether the receiving server is configured to receive messages correctly. If you then resend the message, it is placed in the queue again, and if the receiving server is up, the message is delivered.

A 4.4.7 NDR message can also indicate that a message header limit has been reached on a remote server or that some other protocol timeout has occurred while communicating with the remote server. It may be necessary to reduce the number of recipients in the header of the message for the host to which you are receiving this error. If you then resend the message, it is placed in the queue again, and if the receiving server is up, the message is delivered. (more)



Don't see your message or something similar?  Forward the entire bounced-back message - including all of the details from the Mailer-Daemon - to nexlan@nexlan.com.  We'll help you investigate and get your mail to your recipient.

 For additional information and network support, contact us at 217.431.7236.

 


 

Legal Disclaimer
Copyright © 1998-2008 NexLAN, LLC.