Mail Delivery System Error

[nortk]

I have given someone an e-mail address using my domain name, and it has been working fine for months. However, recently, this person (my dad, actually) sent an e-mail to someone, but apparently he sent it to an incorrect e-mail address.

 

The result, though, was that I was the one who received a "Mail Delivery System" error on my main account, rather than my dad receiving it on his account.

 

Is this the standard way that it should work? I know his account is configured correctly, yet somehow I'm the one getting the error e-mail (including, by the way, the entire contents of the e-mail my dad was sending to someone else).

 

Is there anything I can do about that, or is it related more to the destination server of the original e-mail?

 

Hope my question makes sense. Thanks for your help.

 

Norm Krumpe

[ThumpAZ]

This is handled by where the NDR (Non-Delivery Report) items are sent.

I was cruising through cpanel and did not see where exactly this should/could be modified. It may have to do with the Default address as this is dealing with where unrouted email goes to.

 

Most NDRs sent by the remote server will also try to send an NDR to the 'administrator' of the mail server. This is something setup by the remote admin. I wonder, what is the To:, CC: or BCC: addresses in the email you received. I am pretty sure that they will show an account that is not necessarily your personal one, but is something to do with administrator.

To keep this from happening again, you can set the default email route to :blackhole: for the different items in your domain, and then NDRs of this sort will simply disappear, except for those sent directly to the user.

 

Let me know if my assumption is correct, and I will work with you further if you find it to be incorrect and wish to pursue it further.

 

EDIT: My spelling really does stink

Edited April 7, 2004 by TCH-Glenn

[nortk]

Well, looking more carefully, it seems that the user used Neo-Mail to send the e-mail. Could that be related? Here's what the returned message looks like (edited for brevity and privacy, with some highlighting by me). Is this possibly a Neo-Mail configuration issue?

 

Thanks for your help.

 

Norm

 

 

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

 

Return-path: <mymainusername@server16.totalchoicehosting.com>

Received: from mymainusername by server16.totalchoicehosting.com with local (Exim

4.24)

for xxxx@xxxx.xxx; Tue, 06 Apr 2004 14:41:31 -0400

From: "my dad's name" <mydadsusername@****>

To: failed recipient address

X-Mailer: NeoMail 1.26

X-IPAddress: 66.202.6.23

MIME-Version: 1.0

Message-Id: <E1BAvVr-00040M-Vg@server16.totalchoicehosting.com>

[OnlineAutorama]

Yeah this is like the 3rd time different messages i've had this happen to me here.

I believe the fix is to submit a support ticket which i'm about to do. this is the 3rd time i've received this message, Every 24hrs.

 

Mail Delivery System [Mailer-Daemon@server128.tchmachines.com]

This message was created automatically by mail delivery software.

A message that you sent has not yet been delivered to one or more of its recipients after more than 72 hours on the queue on server128.tchmachines.com.

 

The message identifier is: 1IAjdu-0007Qk-To

The subject of the message is: =?utf-8?B?UkU6ICjnkZ7mmJ/mj5DnpLot5q2k6YKu5Lu25Y+v6IO95piv5Z6D5Zy+6YKu?=

=?utf-8?B?5Lu2KUhlbHAuIFByb2JsZW0gd2l0aCBCcnVzaGxlc3MgMg==?=

=?utf-8?B?NWEgRVND?=

The date of the message is: Tue, 17 Jul 2007 05:46:52 -0400

 

The address to which the message has not yet been delivered is:

 

No action is required on your part. Delivery attempts will continue for some time, and this warning may be repeated at intervals if the message remains undelivered. Eventually the mail delivery software will give up, and when that happens, the message will be returned to you.

Edited July 21, 2007 by OnlineAutorama

[TCH-Don]

As you say open a help desk ticket.

[TCH-Dick]

I have removed this email from the queue as the receiving server is no longer online.

Although I don't recommend it, you will need set up a filter to block these notices if you do not want to receive them when a delivery fails.