journal message delivery rejected
- Started getting a MOM alert this morning:
Severity: Critical Error
Source: MSExchangeTransport
Name: A message was rejected by the remote server. This message will be deferred and retried because it was marked for retry if rejected.
Checking the queue, I found one message that is now up to 303 retries. Get-Message reveals the following error:
400 4.4.7 The server responded with: 554 5.3.4 STOREDRV.Deliver; Content conversion limit(s) exceeded. The failure was replaced by a retry response because the message was marked for retry if rejected.
The destination mailbox is our journal mailbox. Research indicates that this error is likely due to the message being larger than allowed. This message size is 239721 bytes, well below the 10MB limits on the connectors, and the journal mailbox is set to unlimited. The journal mailbox routinely handles messages much larger than this one, so the reason for this problem escapes me.
Any ideas?
Thanks,
Mike
Answers
The most possible cause would be, the certain special message limits have been exceeded. Please refer the answer in this thread. The limits are hardcoded, unchangeable
“Considerations for Content Conversion Tracing” section in Managing Content Conversion Tracing
- Marked As Answer byJames-LuoMSFT, ModeratorMonday, November 02, 2009 1:26 AM
- Thanks, James! I enabled content conversion tracing and discovered that we're getting the same "Recipient data exceeds the limit of 2000 characters" error that you are (or were) researching for the user in this thread (http://social.technet.microsoft.com/Forums/en/exchangesvradmin/thread/39443689-577b-426d-83e4-e5111173c718). The odd part of this is that our failure only occurred for the journal report, not on the original message.This particular message is not business-critical, so I'm just going to delete it from the queue. I did want to thank you for pointing me to that article, which helped me find the underlying problem.Best Regards,Mike
- Marked As Answer byJames-LuoMSFT, ModeratorMonday, November 02, 2009 1:26 AM
All Replies
The most possible cause would be, the certain special message limits have been exceeded. Please refer the answer in this thread. The limits are hardcoded, unchangeable
“Considerations for Content Conversion Tracing” section in Managing Content Conversion Tracing
- Marked As Answer byJames-LuoMSFT, ModeratorMonday, November 02, 2009 1:26 AM
- Thanks, James! I enabled content conversion tracing and discovered that we're getting the same "Recipient data exceeds the limit of 2000 characters" error that you are (or were) researching for the user in this thread (http://social.technet.microsoft.com/Forums/en/exchangesvradmin/thread/39443689-577b-426d-83e4-e5111173c718). The odd part of this is that our failure only occurred for the journal report, not on the original message.This particular message is not business-critical, so I'm just going to delete it from the queue. I did want to thank you for pointing me to that article, which helped me find the underlying problem.Best Regards,Mike
- Marked As Answer byJames-LuoMSFT, ModeratorMonday, November 02, 2009 1:26 AM
- Glad to help :)
