Exchange Server Forums

Outlook Appointment - 4.4.7 NDR

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2003] >> Message Routing >> Outlook Appointment - 4.4.7 NDR

Page: [1]

Message

<< Older Topic Newer Topic >>

Outlook Appointment - 4.4.7 NDR - 24.Sep.2008 2:22:07 PM

Kezzran

Posts: 38
Joined: 25.Feb.2008
Status: offline

Hello again all. I have a question about an undeliverable message issue we ran into with Exchange (2003) late last week. Here is the situation:

An employee sent an appointment to a number of internal and external email addresses using his Outlook 2007 client. These were all delivered and accepted. Following this, the appointment had be be rescheduled, which he did within Outlook 2007 by changing the date/time and clicking on the Send Update button. The updated appointment was delivered internally without error, but was not delivered to the external recipients. The message was retried throughout the evening by Exchange until it finally timed out, returning an NDR to the meeting scheduler (this was all confirmed using Message Tracking Center).

The text of the delay:

Reporting-MTA: dns;servername.domainname.COM
Final-Recipient: rfc822;jim.bob@mhcdc.org
Action: delayed
Status: 4.4.7
Will-Retry-Until: Fri, 19 Sep 2008 21:59:25 -0500
X-Display-Name: 'jim.bob@mhcdc.org'

Final-Recipient: rfc822;joe.bob@ps.net
Action: delayed
Status: 4.4.7
Will-Retry-Until: Fri, 19 Sep 2008 21:59:25 -0500
X-Display-Name: Joe Bob

The text of the NDR:

Your message did not reach some or all of the intended recipients.

    Subject:    Super Secret Meeting

The following recipient(s) cannot be reached:

    Joe Bob on 9/19/2008 10:03 PM
          Could not deliver the message in the time limit specified. Please retry or contact your administrator.
          <servername.domainname.COM #4.4.7>

    'jim.bob@mhcdc.org' on 9/19/2008 10:03 PM
          Could not deliver the message in the time limit specified. Please retry or contact your administrator.
          <servername.domainname.COM #4.4.7>

I'm able to connect to the external mail servers using Telnet without difficulty, and all other mail to these domains is being delivered without error. Everything appears to be working correctly, except for the revised calendar appointment, which was not delivered to the external recipients for some reason.

My question is, how do I determine what happened here?

Thanks,
Kezzran

Post #: 1

Featured Links*

RE: Outlook Appointment - 4.4.7 NDR - 25.Sep.2008 8:34:19 AM

ravisha_22

Posts: 445
Joined: 16.Sep.2008
Status: offline

Check what messaging system the recipient is on, whether it can accept calendar updates etc.

If yes...

Turn on SMTP logging in the first place and send a meeting and update and see the logs.

_____________________________

Ravishankar

(in reply to Kezzran)

Post #: 2

RE: Outlook Appointment - 4.4.7 NDR - 25.Sep.2008 4:03:09 PM

Kezzran

Posts: 38
Joined: 25.Feb.2008
Status: offline

ravisha,

Thank you for the reply. I did test this with a Yahoo account, and it worked fine, so I think that it should work even if they don't have Exchange/Outlook at the other end. Please correct me if I'm wrong.

I think I may have to put this down to a temporary anomoly. Microsoft's own site indicates that a 4.4.7 is typically an issue on the receiving server (although it is strange that both external addresses we were attempting to send to at that time did not work):

Per Microsoft:

http://support.microsoft.com/kb/284204

Numeric Code: 4.4.7

Possible Cause: The message in the queue has expired. The sending server tried to relay or deliver the message, but the action was not completed before the message expiration time occurred. This NDR may also indicate that a message header limit has been reached on a remote server or that some other protocol timeout occurred during communication with the remote server.

Troubleshooting: This code typically indicates an issue on the receiving server. Verify the validity of the recipient address, and verify that the receiving server is configured to receive messages correctly. You may have to reduce the number of recipients in the header of the message for the host that you are receiving this NDR from. If you resend the message, it is placed in the queue again. If the receiving server is on line, the message is delivered.

Thanks,
Kezzran

(in reply to ravisha_22)

Post #: 3

RE: Outlook Appointment - 4.4.7 NDR - 3.Dec.2008 11:02:30 AM

szilagyic

Posts: 1
Joined: 3.Dec.2008
Status: offline

We are having the exact same problem, too. I have confirmed that Outlook 2003 works fine. I've also looked around and there is no solution available. Hopefully Microsoft will fix this although I'm not getting my hopes up too high.

(in reply to Kezzran)

Post #: 4

RE: Outlook Appointment - 4.4.7 NDR - 6.Jan.2009 6:30:49 PM

marc@infiniteconsult

Posts: 1
Joined: 6.Jan.2009
Status: offline

We also are having the same issue with our Exchange 2003/SBS server and Outlook 2007. And another client of ours is having the same problem. Haven't found any cause or cure.

Would appreciate hearing if anyone found anything that fixed or a workaround.

Thanks..

_____________________________

Marc Chaton
Infinite Consulting Services

(in reply to szilagyic)

Post #: 5

RE: Outlook Appointment - 4.4.7 NDR - 12.Jan.2009 7:26:45 AM

ravisha_22

Posts: 445
Joined: 16.Sep.2008
Status: offline

I want to know if the mails are NDRed only for meeting updates or for general meeting requests as well?

i want to know whether these meeting updates are showing as stuck in the queue and are not to be found in the queue folder?

Please answer both the questions, because i have seen a somewhat close resembling bug, for which a hotfix is available.

Please do the testing by generating a meeting update and let me know the answers.

_____________________________

Ravishankar

(in reply to Kezzran)

Post #: 6

RE: Outlook Appointment - 4.4.7 NDR - 28.Jan.2009 9:55:31 AM

baggydog

Posts: 2
Joined: 28.Jan.2009
Status: offline

Ravisha,
I am having the exact problem as your first question: emails are NDRed only for meeting updates not the original meeting request. Once a meeting is created if it is changed the updated meeting requests hangs in the queue until a delay message is sent then eventually an NDR after the retrys expire. The updated message can be found in the queue using Find Messages for that queue but they are NOT in the vsi1 queue folder.

In my case this only happens when there is a mix of internal and external recipents of the calendar request. If I split the calendar request into 2, one for internal recipients and one for external, then I can send updates just fine.

Any hotfix that you know of would be great as this has been bugging me for a long time.

Thanks!

John V.

< Message edited by baggydog -- 28.Jan.2009 10:01:31 AM >

(in reply to ravisha_22)

Post #: 7

RE: Outlook Appointment - 4.4.7 NDR - 29.Jan.2009 5:30:00 AM

ravisha_22

Posts: 445
Joined: 16.Sep.2008
Status: offline

Ok there is indeed one KB article: http://l.lenovo.com/ajtk/servlet/JJ?H=2nhwno&R=10179569&P=17679512

But i suggest youto go through the KB article carefully and match your situation with the conditions given the KB and then test it out in oe server and then got for wider deployment.

_____________________________

Ravishankar

(in reply to baggydog)

Post #: 8

RE: Outlook Appointment - 4.4.7 NDR - 29.Jan.2009 9:20:50 AM

baggydog

Posts: 2
Joined: 28.Jan.2009
Status: offline

Did you mean to post a link to Lenovo? Would you be so kind as to list the KB number?

Thanks!

John V.

(in reply to ravisha_22)

Post #: 9

RE: Outlook Appointment - 4.4.7 NDR - 29.Jan.2009 9:23:13 AM

ravisha_22

Posts: 445
Joined: 16.Sep.2008
Status: offline

hahahaha my bad

was doing some other stuff parallely, so got mixed up, here you go.

http://support.microsoft.com/Default.aspx?kbid=938650

_____________________________

Ravishankar

(in reply to baggydog)

Post #: 10

RE: Outlook Appointment - 4.4.7 NDR - 6.Apr.2009 3:20:08 PM

tomekc

Posts: 5
Joined: 6.Apr.2009
Status: offline

I have same problem but with new appoitment sent by Outlook 2007 -> Exchange 2003 SMB.
When user is trying to invinite more than 20 externall persons, messages is stucking in exchange queue and after 24 hours he have 20 undelivery messages in his mailbox.
But, he can send exacly same message to exacly same people as a regular e-mail and is going trough.
I'd made some tests and try to create distribution group with 40 recipients and send some appoitment from callendar and everybody got it and he can track messages.
So my question is, what is a different (probally in header) to send for 40 people and send for distrinution group with same 40 addresses. Why exchange can't deliver message from callnedar to 40 people and can delivery to distribution list ?
User is complain that he was abble to send appoitment from callendar for more than 25 persons from Outlook 2003. After upgrade outlook to 2007 he can't.

Thanks everyone for future help

< Message edited by tomekc -- 6.Apr.2009 3:40:11 PM >

_____________________________

TC

(in reply to ravisha_22)

Post #: 11

RE: Outlook Appointment - 4.4.7 NDR - 30.Jun.2010 4:59:26 AM

taga_ipil

Posts: 55
Joined: 19.Jun.2010
Status: offline

Hi Guys,

Pardon my intrusion on this thread, but I have a similar or quite weird problem.

I can email a customer and I am using Outlook 2003, however on the other hand my co-workers cannot email the customer using Outlook 2007 and get the same 4.4.7 error notification.

hope to hear from you.

Thanks

(in reply to tomekc)

Post #: 12

RE: Outlook Appointment - 4.4.7 NDR - 30.Jun.2010 9:56:15 AM

uemurad

Posts: 8232
Joined: 7.Jan.2004
From: California, USA
Status: offline

If you can get the message delivered and someone else can't, you should first look for differences. The main one being the recipient address. When the others attempt to send, are they manually typing the address or are they allowing autocomplete to function? The most common cause is that your other users are using a cached address that is not valid.

Next, check Message Tracking to see what happens to your message as opposed to theirs.

After that check the SMTP logs to see what happens to your message as opposed to theirs.

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange (2007-2011)
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to taga_ipil)

Post #: 13

RE: Outlook Appointment - 4.4.7 NDR - 30.Jun.2010 10:29:21 PM

taga_ipil

Posts: 55
Joined: 19.Jun.2010
Status: offline

Hi uemurad,

I think I know now the problem. Thanks

I use the Message Tracking and found out that the other user smtp was submitted to one of our smtp relay that has a poor reputation while mine was forwarded to a good reputation smtp relay. My additional question right now is how to point that user to use that good smtp relay? considering we both belong to the same Storage Group.

thanks in Advance

< Message edited by taga_ipil -- 1.Jul.2010 1:48:32 AM >

(in reply to uemurad)

Post #: 14