Updates to meetings coming back undeliverable

[laura]

Users in our organization are reporting an issue when sending meeting
updates. The first time they send the meeting request to internal employees
or outside customers, everything is fine and the meeting schedules without a
problem. If the organizer needs to make a modification to the meeting, say
the time, an undeliverable report will be sent to them that it did not reach
all recipients, but only for outside email addresses. The undeliverable does
not come back right away. The email appears to sit in the queue until it
times out. The undeliverable received is "could not deliver the message in
the time limit specified. 4.4.7". So to the organizer, they think everything
has been sent out and updated without any problems because they don't receive
any undeliverable right away. We are running Exchange 2003 and all users
have Office 2007. Any help would be appreciated.

Thanks!
Laura

 

[Diane Poremsky {MVP}]

From http://support.microsoft.com/kb/284204Numeric 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.
Obviously, if its an update, the address and # of recipients should be ok.
Does the NDR give any clues as to why its not getting sent or accepted by
the outside server?

 

[laura]

there doesn't seem to any indication why the email would just sit in the
message queue until it timed out. that's what is so confusing, they're
correct email addresses! i don't know what to look for next....

 

[sheri]

Did you figure this out? We are having the same problem.

 

[Kfir]

Did anyone find what is the cause and how to fix?

We have the same problem as well. The one thing I think we have in common
and might be a clue is that the server is Exchange 2003 (SP2) and the meeting
update requests are coming from Outlook 2007. From outlook 2003 We do not
have that problem. This happens randomly.

I checked the logs of our firewall and when it happens the Exchanges server
doesn't even try to connect outside to send the message. It just sit in queue
until it bounces as non delivery.

Kfir

 

[laura]

Still haven't found a resolution to this issue. I would suspect it has
something to do with the combo of Exchange 2003 and Outlook 2007.
Frustrating because, like you said, the message just sits in the queue until
it expires. It never attempts to contact the other mail server.

 

[ryan]

I too am having this problem... nothing found on Google... any help would be
greatly appreciated.

-- Ryan

 

[Ryan Carnell]

http://support.microsoft.com/kb/938650/en-us

Still haven't found a resolution to this issue. I would suspect it has
something to do with the combo of Exchange 2003 and Outlook 2007.
Frustrating because, like you said, the message just sits in the queue until
it expires. It never attempts to contact the other mail server.

 

[srinivasmk]

This issue occurs when updated meetings bounce with an NDR Storedrive error.
the recipient mailbox is in lit hold
run the below command to resolve the issue

Set-Mailbox -Identity "(e-mail address removed)" -RecoverableItemsWarningQuota unlimited -RecoverableItemsQuota unlimited -UseDatabaseQuotaDefaults $false -UseDatabaseRetentionDefaults $true

once completed check the output by running the command

get-mailbox -identity "(e-mail address removed) | fl recoverable*, usedatabase*

the output should be as follows, once completed wait for 10-15 minutes and resend the meetig upadate which should be delivered

RecoverableItemsQuota : Unlimited
RecoverableItemsWarningQuota : Unlimited
UseDatabaseRetentionDefaults : True
UseDatabaseQuotaDefaults : False