Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How to improve NDR messages?

Status
Not open for further replies.

J741

Technical User
Jul 3, 2001
528
CA
I recently sent a 2.5MB e-mail to our company which was much larger than the allowed maximum size limit, knowing that this would generate an automaic NDR reply message.

Here's the mesage that I got for the reply (some names have been changed to protect the innocent):

Code:
This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.

       mailbox@companyname.com

The NDR had ann attached file called DETAILS.TXT with the following contents:

Code:
Reporting-MTA: dns;companyname.com
Received-From-MTA: dns;defout.myisp.net
Arrival-Date: Fri, 28 Jul 2006 10:28:13 -0600

Final-Recipient: rfc822;mailbox@companyname.com
Action: failed
Status: 5.2.3
X-Display-Name: NetworkUserName

What I want to know is if (and how) I can change the NDR produced by exchange to include more detail, and obfuscate other details.

Specifically, I would like to add the reason for the delivery failure in the NDR. For example, a line of text stating 'message size (2.5MB) is larger than the 1MB maximum'.

I would also like it to include more details about the fact that the message was generated automatically by the Microsoft Exchange Server at our company, and not by someone named 'postmaster'.

Also, I would like to exclude the 'X-Display-Name:' line from the 'details.txt' attached file.

So can anyone tell me where I can make these changes?

- James.

My memory is not as good as it should be, and neither is my memory.

I have forgotten more than I can remember
 
This used to be possible in the days that Exchange 5.5 was supported by MS, but only if you paid Microsoft Consultancy Service $$$s for them to effectively compile you a custom NDR DLL. I'd be very surprised if they still offered this service.

I have to ask, why are you interested in investing so much effort in customising a legacy email product? You should be migrating away from it as fast as you can, as you have significant business risk whilst you remain on unsupported software.
 
Legacy? Unsupported? It's only one generation old! Any my Boss isn't willing to pay Microsoft's rediculous extortion fees to install Exchange Server 2003.

My memory is not as good as it should be, and neither is my memory.

I have forgotten more than I can remember
 
Be that as it may, you're pretty much on your own with an unsupported product.
 
Exchange 5.5 is now two generations old. Exchange 2003 is the current, followed one generation by 2000, then 5.5. If you boss waits long enough, he won't have to upgrade, as there won't be an upgrade path.

When all else fails, READ THE DAMN BOOK!
 
When all else fails, READ THE DAMN BOOK!

Uhm, I don't have a book, or any kind of documentation for the Exchange Server on this Windows 2000 Server.

I also don't see any help files under the Exchange Manager.

Also, I'm not even sure if the version number is 5.5, and I don't know where to check for this as clicking Help-About only tells me the version of the Microsoft Management Console, and not the version of Exchange.

- James.


My memory is not as good as it should be, and neither is my memory.

I have forgotten more than I can remember
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top