TOTAL DOMAIN QUOTA

[MailEnable]

Current versions of MailEnable support quotas for Mailboxes only. Version 5.11 will support postoffice quotas (ie: domain quotas) and the page was updated prematurely when the web site was revamped later this month. With 5.11, system administrators will be able to stipulate quotas for postoffices and when these quotas are reached, alerts are raised and the administrator of the postoffice is notified.

Postoffice quotas were anticipated earlier, but deferred because they required some significant improvements to MailEnable's message store indexing (and these have recently been completed and are in a test phase). Once this testing is completed; 5.11 will be availabe with the associated quota features.

[nccng2001]

Finally, I did see the total domain quota configuration in MailEnable 5.11.

However, it is only notification to certain email user within the particular domain once it hits a pre-defined percentage of the total domain quota. Does it allow bouncing of emails and informs the sender of the recipient's over quota problem?

Thanks

[MailEnable]

Thanks for the feedback.

As you have said, the current implementation does not generate bounce-back notfications to the sender. But there are some significant considerations associated with this.

Bounceback is undesirable because it causes backscatter spam.

We see alot of this, even with mailbox quotas (and the abuse can cause significant heart-ache for the postoffice administrator as well as the broader community).

The scenario is this:

Unauthenticated spammer forges mail from and sends spam e-mail to postoffice or domain that has exceeded quota.
Message bounces and is sent to innocent bounceback spam receiver. (Who is likely to report the spam in which case the IP address is blacklisted, causing delays and bogging down queues)... and so on. An abused server can take hours to fix.

We are looking at tighter control over this by only bouncing back when the sender is absolutely identified by domainkeys, etc.
Such extensions will appear in future revisions; but for now, the basic postoffice quota support should provide some relief.

[nccng2001]

We are an email hosting company.

We have lost much revenue on this quota as there is no form of restriction. Hence, all our users are over-using it till today. That is the reason why we have delay our upgrade with MailEnable.

We may have a suggestion to your problem. Just a thinker.

- When an email arrives to a sender whose postoffice (or rather known as domain to lay man) or account quota has been exceeded, a repository in MailEnable can contain these emails.
- The repository can act like a catch all account for over quota problem. A configuration to clear the repository should be default to say 30 days. Once over the pre-defined date, the emails will be wiped out.
- An email will be generated by MailEnable to inform the recipient about :
- his quota's problem
- the sender's information
- the email's subject
- the email's sending date
- Once the domain or account has cleared some of their emails, and is within the quota, the recipient can request from the repository to send the email back to him.

From here, we can have some form of restrictions for our hosting and can yield more revenue in this way as they may like to consider to expand the quota.

Also, we did a test on new MailEnable 5.11 trial period with the quota setting, we set one fo the account to 1MB quota and the account still keeps receiving email, despite the over quota problem. There is also no notification sent to the pre-designeated user.

Thanks

[nccng2001]

It seems like the age-old problem has not been heard from the developer.

This is sad....

[MailEnable]

Its just a matter of priorities. Our recent priorities have been in getting the 5.5 release stable and delivered (associated with its improvements in scalability and speed).
With this out of the way, we can continue to improve in areas like quota notification/mailbagging (as you have outlined here).

[poweredge]

Somehow I still couldn't find the total per domain/per postoffice quota in v10.34, any hints please? The current working one Set Quota still means per user, not per Postoffice in total as tested.

I've just came across how Plesk control panel calculated the total disk usage, it simply sum up the sf directory of the particular post office, so there much be a way to implement the total disk limit for individual postoffice somehow.

12312.jpg (96.41 KiB) Viewed 17578 times

[poweredge]

Current versions of MailEnable support quotas for Mailboxes only. Version 5.11 will support postoffice quotas (ie: domain quotas) and the page was updated prematurely when the web site was revamped later this month. With 5.11, system administrators will be able to stipulate quotas for postoffices and when these quotas are reached, alerts are raised and the administrator of the postoffice is notified.

Postoffice quotas were anticipated earlier, but deferred because they required some significant improvements to MailEnable's message store indexing (and these have recently been completed and are in a test phase). Once this testing is completed; 5.11 will be availabe with the associated quota features.

I read in the above "Version 5.11 will support postoffice quotas (ie: domain quotas) "

May be it's here, but not exactly the feature everyone wants. (ie, Quota feature allocates a total say 100GB, then allow user admin to freely distribute among their users)

12321.jpg (87.76 KiB) Viewed 17568 times