Imap.maxmessagesize Appears To No Longer Be Working
(Doc ID 2371689.1)
Last updated on MARCH 20, 2019
Applies to:
Oracle Communications Messaging Server - Version 8.0.2 and laterInformation in this document applies to any platform.
Symptoms
Using: Messaging Server 8.0.2.2.20180122
imap.maxmessagesize appears to no longer be working.
We have role.imap.maxmessagesize = 157286400, so imapd should never accept a message larger than 150meg.
imcheck -m output on a particular user shows the messages are all recent, so this is not a coincidence of some messages created long ago, before the limit was implemented.
The bad part of this is that it is causing mshttpd to core.
It is also sort of frustrating because we have this one user with 19 messages in the Drafts folder which are all 3.9gig in size (not counting any expunged).
Performing an "imcheck -m user/<userid>/<folder>" shows recent messages that are greater than the 2 GB limit.
Snip of output:
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |