defaultmailboxquota anomaly

Sun Java(tm) System Messaging Server 6.3-1.04 (built May 9 2007; 32bit)

I have a situation where i have set: store.defaultmailboxquota = 262144000

on my mailstore.

imquotacheck reveals that the user accounts do in fact have the proper quota eg

john25600020550-258---

Imap clients seem to also report the quota properly, however within the messenger express interface the quota is not reported properly and in fact shows:

Your mailbox disk quota is: 4194304MB

If i add a mailquota value to the user's directory entry the web interface reports properly.

Did i miss something in my configutil for webmail, is this a bug, or do i just need to populate my user directory accounts with mailquota values ?

-john

[768 byte] By [goubeauxa] at [2007-11-27 10:28:00]
# 1

Hi,

Looks like a new bug - I can reproduce on my own test system. You will note that the underlying quota information changes when you log-in using messenger-express/UWC - so it appears that is being displayed is 'correct', its why the quota is being changed is the question e.g.

Before login:

bash-3.00# ./imquotacheck

NameQuota(K) Usage(K) %Quota# Usage# % OverDate WarnDate

-- -- -- - - -- --

admin25600000-0---

After login:

bash-3.00# ./imquotacheck

NameQuota(K) Usage(K) %Quota# Usage# % OverDate WarnDate

-- -- -- - - -- --

admin-0--0---

I will look into it over the next day or two.

Regards,

Shane.

shane_hjortha at 2007-7-28 17:49:11 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 2

Hi,

I have logged a bug for this issue, bug #6580785 - "Webmail displays incorrect quota information when mailquota attribute isn't set". Please log a sun support case (if you have a support contract) if you want this bug fixed in the short-term.

With regards to the quota changing behaviour which I noted previously, this appears to have been more due to caching of LDAP information within the imapd/stored processes so was to be expected (I was forcing the update of the quota database using the iminitquota -a command rather then waiting for caches to update). Once the LDAP cache had expired the quota was updated correctly in the quota database.

Regards,

Shane.

shane_hjortha at 2007-7-28 17:49:11 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...