Link to home
Create AccountLog in
Avatar of high_sobo
high_soboFlag for United States of America

asked on

Two users calendar invite meeting request get stuck in the smtp queue in Exchange 2003 R2 (64Bit)

I have an Exchange 2003 server I take care of with an occasional problem. Two user sending calander invite meeting request to multiple external users at multiple domains has the message become stuck in the queue for the outbound connector. I don't know if this happens with all her meeting cancellations sent to external users but it is at least some. It may also happen with meeting requests but I can't, at this point, be sure. Here's what I know:
1) It's only this two user who experiences the issue.
2) The queue for the "Default Outbound" SMTP connector goes into retry and other messages appear to be stuck behind this one.
3) The message causing the issue usually - maybe always - has multiple external recipients.
4) It today's case, the message is large-ish (37,627). I'm not sure if that's always the case6
5) Looking at message tracking, the last entry shows "SMTP: Message Routed and Queued for Remote Delivery"
6) There is nothing in the SMTP logs related to this message. This indicates to me that it is not getting as far as a delivery attempt by the SMTP service to any remote server.

This is an Exchange 2003 R2 (64Bit) server,
SOLUTION
Avatar of Jason Watkins
Jason Watkins
Flag of United States of America image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of high_sobo

ASKER

No there's no restrict message size of 37MB
SOLUTION
Avatar of Simon Butler (Sembee)
Simon Butler (Sembee)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
ASKER CERTIFIED SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Firebar & Sembee2,
I ended up using an unpublished hotfix from Microsoft.  However I wanted to reward both of you with points for your gracious time and interest attempting to help me solve my issue!

Thank you