hanrat
asked on
Attachment limit OMA 2003
We have a SBS 2003 R2 server with OMA. The limits are set to 60 MB in the Exchange System Manager, but using an OMA client, an e-mail attachment of more than 4 or 5 MB won't work.
When looking for an answer, i find these articles for Exchange 2007, where the web.config parameter maxRequestLength value has to be modified. But looking for something alike for 2003, i can't find it.
Who can help me out?
When looking for an answer, i find these articles for Exchange 2007, where the web.config parameter maxRequestLength value has to be modified. But looking for something alike for 2003, i can't find it.
Who can help me out?
praveenkumare_sp
We can do a global setting , but i am not sure of a per mailbox setting
ASKER
I'm looking for a global setting, ofcourse.
in 2003 we cant restrict the size of the attachment, but we can restrict the size of the messaage .
So we can indirectly reduce the size of the attachment using these changes . let me know if thats fine ?
So we can indirectly reduce the size of the attachment using these changes . let me know if thats fine ?
ASKER
Yep, that's AOK! As long as it concerns OMA with Mail for Exchange clients.
ASKER
Dear praveenkumare_sp,
I'm looking for a global setting for OMA. This setting does not apply to OMA nor Mail for Exchange. Why do you think this setting will help me?
Hans
I'm looking for a global setting for OMA. This setting does not apply to OMA nor Mail for Exchange. Why do you think this setting will help me?
Hans
ASKER
It's not helping because i'd already have limits up to 60 MB, as mentioned in my opening post and the Mail for Exchange clients can't send large e-mails.
first I think we need to understand your problem.
MailforExchange (nokia)
ActiveSync (google android, ipad/iphone, windows mobile)
All use ActiveSync, they also have their own limits on the device themselves. Exchange 2003 uses it's organisational limits for all services, these cannot be changed on an individual service basis (as far as I am aware). if you have set the organisational limit, then the issue is with the device itself.
Not only that, if it was Exchange rejecting your message it wouldn't strip the attachment off, it would send you an NDR telling you it's too big.
MailforExchange (nokia)
ActiveSync (google android, ipad/iphone, windows mobile)
All use ActiveSync, they also have their own limits on the device themselves. Exchange 2003 uses it's organisational limits for all services, these cannot be changed on an individual service basis (as far as I am aware). if you have set the organisational limit, then the issue is with the device itself.
Not only that, if it was Exchange rejecting your message it wouldn't strip the attachment off, it would send you an NDR telling you it's too big.
ASKER
Hi Demazter,
Thanks for your questions. It concerned both a Nokia, HTC and an iPad. I found these articles for Exchange 2007 OMA, where it is the limits of the IIS cache that's involved in this matter. As OMA 2003 also uses IIS i expect more or less the same issue here.
Looking for limits in ActiveSync i find other saying there are none. As we have the same limit with 3 devices, it feels to me like a server sided limitation.
I'm asking the user for specific error messages.
Thanks!
Thanks for your questions. It concerned both a Nokia, HTC and an iPad. I found these articles for Exchange 2007 OMA, where it is the limits of the IIS cache that's involved in this matter. As OMA 2003 also uses IIS i expect more or less the same issue here.
Looking for limits in ActiveSync i find other saying there are none. As we have the same limit with 3 devices, it feels to me like a server sided limitation.
I'm asking the user for specific error messages.
Thanks!
ASKER
The user does not receive an error message. In the Mail for Exchange client on the Nokia, the message moves to the sent items box and is never received by the recipient.
How to trouble shoot this?
How to trouble shoot this?
I am not aware of anywhere to set such a limit with Exchange 2003. I am going to build an Exchange 2003 server now so I can test this for you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hey Craig,
That really sounds promising! Will an IISReset be enough or do i have to restart the server to take changes into effect?
Kind regards,
Hans Rattink
That really sounds promising! Will an IISReset be enough or do i have to restart the server to take changes into effect?
Kind regards,
Hans Rattink
ASKER
Yeah!! After an iisreset it worked... Great! I'd put it to 20480 and could sent an e-mail with a file attacment of 12 MB!
Thanks a really lot, Craig!
Thanks a really lot, Craig!
ASKER
Finally somebody who actually knew the answer. Also thanks to the moderators for bringing my question twice to the attention of the experts.
Wow, same problem, IISRESET doesn't do, I will try a reboot tonight, did you also try the UploadReadAheadSize setting in Web Config for this to work, I wonder if there is one other tweak you have done that I am not aware of?
ASKER
Hi O2C,
Sorry for the late answer. I didn't try the UploadReadAheadSize, the other just worked for me. Please mind that all other settings in the Exchange System Manager where set ok, to about 60 MB.
Kind regards,
Hans
Sorry for the late answer. I didn't try the UploadReadAheadSize, the other just worked for me. Please mind that all other settings in the Exchange System Manager where set ok, to about 60 MB.
Kind regards,
Hans