Entourage stuck large messages fill up Exchange logs

G

geofftate

Hi, trying to work around a recurring problem. Mixed PC/Mac client
environ, Exchange 2003.

I have a max outgoing message size of 10MB set in Exchange. When an
Entourage 2004 user tries to send a message that is too large, it
remains in their outbox and keeps retrying to send. Exchange logs the
message each time it retries, without accepting it of course. This
fills up the Exchange logs -- in an extreme case (someone stupidly
tries to send a 200MB image file) it can fill up the Exchange logs and
take down the server in minutes. It's happened three times so far to
oblivious users.

I assume others have encountered this? Ideas? Any way to have Exchange
not log these, or perhaps a client-side workaround? Thanks.

gt
 
G

geofftate

Holy cow, never even ocurred to me that this might be a bug with an MS
hotfix. I just figured it was another one of those Entourage
deficiencies. Servers me right for not even serching the KBs. Thanks
Ben!
 
R

Rich Matheisen [MVP]

geofftate said:
Holy cow, never even ocurred to me that this might be a bug with an MS
hotfix.
Click to expand...

It's not. The hotfix corrects the problem caused by the conflicting
message size restrictions.
 
R

Rich Matheisen [MVP]

geofftate said:
Installed the hotfix and it worked. Exchange now ignores oversized
attachments being sent from Entourage instead of logging them. Thanks

How is this not a bug? In what way are the message size restrictions in
Exchange "conflicting?" Conflicting with what?
Click to expand...

Conflicting with each other. Did you read the KB article?
 
G

geofftate

Ah, sorry, I'd missed that part. Article says it can be caused by a
conflict between mailbox message size limit and global message size
limit. Except in my case, this has nothing to do with a conflict. All
users are using the default global message size limit. Yet the hotfix
still fixed the problem. Still seems like a bug...
 
R

Rich Matheisen [MVP]

geofftate said:
Ah, sorry, I'd missed that part. Article says it can be caused by a
conflict between mailbox message size limit and global message size
limit. Except in my case, this has nothing to do with a conflict. All
users are using the default global message size limit. Yet the hotfix
still fixed the problem. Still seems like a bug...
Click to expand...

.. . . which the hotfix corrected. :)
 
Top