Home Forums OS X Server and Client Discussion Mail 10.3.9 – A Tale of Two Quotas

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #369875
    JasonHeiser
    Participant

    One of my users stopped receiving e-mail recently. According to [b]/var/log/mail.log[/b], all delivery attempts on his behalf were being deferred. I logged into [b]SquirrelMail[/b] and it told me his mailbox was at 100% of his quota.

    In [b]Server Admin > Mail > Accounts[/b], however, he was supposed to have 19% free space remaining.

    [b]/usr/bin/cyrus/quota[/b] was saying the same thing: 19% free space remaining.

    Then I tried [b]/usr/bin/cyrus/bin/cyrus-quota[/b] and it told me what [b]SquirrelMail[/b] was saying: this guy was over his limit.

    I used [b]WorkGroup Manager[/b] to increase his quota so he had room to delete his mail.

    The quota change had no effect. I stopped and started mail services. His quota remained at the previous level. I even tried to change his quota with [b]cyradm[/b]. It had no effect.

    In the end, I managed to purge a bunch of space-hogging attachments to make his mailbox operational again.

    I have two questions:

    (1) What is the difference between [b]quota[/b] and [b]cyrus-quota[/b]? One is wrong and one is right. Unfortunately, it appears that [b]Server Admin[/b] is using the wrong one. Plain ol’ [b]quota[/b] used to work just fine. I know because I used it in a script for sending periodic reminders to users who were edging too close to their limit. I’ve had to switch it to [b]cyrus-quota[/b] so the notifcations work again.

    (2) Why didn’t my quota adjustment in [b]Workgroup Manager[/b] take effect?

    I’m beginning to think that the incremental security fixes that Apple releases are starting to create a small disconnect between the GUI admin tools and the server itself. Given 10.3.9 server’s age, I’m afraid Apple’s not paying enough attention anymore.

    #369991
    gw1500se
    Participant

    I’m not sure about #1 as we don’t set mail quota here but we do set disk quotas. That works however, there is a bug in mail that does not respect the quota and hangs when the user exceeds it. At that point the users mail database is messed up and has to be re-imported.

    On the other hand, #2 should work except when you change quotas the user must logoff before they take effect.

    I hope that helps a little.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.

Comments are closed