We have a problem with quotas on a mail database in a cluster environment LN 5.11 (server2 and server3). Quotas have the same value on both servers. Users are located on server2 (mail file location). If someone exits the quota he still receives new mail and his DB still grows but only on the home server (where mail file is located). We have trouble replicating on the second server. We're getting this error: "Unable to write to database because database would exceed its disk quota."
This sounds like correct behavior to me. New mail is still delivered when a ma ilfile is over quota, otherwise the mail would be lost. But when the database replicates (clusters) to the other machine, the quota kicks in and rejects the replication. I think everything is working as it should. Feel free to write back if I am missing something.
This was first published in October 2003