No Grace Period Observed Before User Went Over Quota
Last updated on JUNE 29, 2017
Applies to:Oracle Communications Messaging Server - Version 7.0.0 and later
Information in this document applies to any platform.
We have a Version 7 mail store:
libimta.so 7u3-17.01 64bit (built 12:33:34, Jun 8 2010)
with a very minimal configuration on quota, as defined by configutil:
store.defaultmailboxquota = 104857600
We had a user who went over his quota and seemed to progress from "going over quota" to "rejecting mail" pretty much immediately, with no grace period. The messaging server logs were checked for approximately 3 weeks back, but, nothing was found which indicated the user had been in danger of going over quota. Here is an example of what was observed in the mail.log_current log:
- Mail is delivered:
25-Aug-2011 16:08:37.29 ims-ms D 28 XX@ZZ.COM rfc822;firstname.lastname@example.org user1@ims-ms-daemon <4E56730B.email@example.com>
- Mail starts bouncing (notice the 2 hour span between the successful Enqueue/Dequeue and the Enqueue/Rejection):
25-Aug-2011 18:13:46.71 ims-ms R 10 XX@YY.com rfc822;firstname.lastname@example.org user1@ims-ms-daemon <DA6047890CFFE440ABDA9B18A2359DF8252118B1@mailstore.domain.com> Over quota
A quick test was run against another user to verify the expected behavior. For this test, the user's quota was set to 1 byte and then a test message was sent. The mail.log_current log file reflected the bounce, so the quota was then changed back to it's original value. After doing this, iminitquota was run to reset the quota value and the message was then processed. Here is what was observed in the log file for the test:
26-Aug-2011 17:07:10.01 ims-ms Q 1 XX@YY.com rfc822;email@example.com test2@ims-ms-daemon
<0LQJ00MNVOV0BS80@mailstore.domain.com> Over quota Over quota
26-Aug-2011 17:12:10.13 ims-ms D 1 XX@YY.com
rfc822;firstname.lastname@example.org test2@ims-ms-daemon <0LQJ00MNVOV0BS80@mailstore.domain.com>
Can some light be shed on what might have possibly caused this?
No changes were made to the systems. It should be noted, however, that this particular server was not installed and configured the same as the rest of the messaging servers in the deployment. It was installed by a 3rd party and was left with a mostly default configuration as far as quotas go.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms