Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
This is not correct. You do NOT need to run compact to unlock the mail send function again.
1. ) your server needs to be configured correctly : Server document / transaction log / Quota enforcement -- must be set to "Check file size when adding a note"
2.) your Notes client must have the notes.ini variable $Reactivate_Mail_Quota=1 set.
This can be done by using a desktop policy. Details are described here : https://www-01.ibm.com/support/docview.wss?uid=swg21247798
When the user has deleted a lot of mails, he can run Actions / Reactivate mail send functions to update the quota information.
Furthermore I do recommend reviewing your quota policy. Blocking inbound mail when a user is above quota will most likely have a negative business impact. e.g. an important inbound mail being rejeceted because of being over quota. The better solution is to disable mail send functions when a user is above quota.
Suppose a user has DB of 700MB. He was on leave for two days and his DB is now 700 MB. So he won't be able to receive any emails. When he arrive for duty after leave he will delete a lot of mail, but still he won't be able to receive any emails. He will call IT department and ask them to help and they will have to compact his mail from the Server console manually. We are experiencing this type of scenario very often.
It is not only the case of employee being on leave. Mostly when they came in the morning after a night shift or weekly off this happens.
You dont need to compact a database just because it is large. What you might want to do is to focus on databases which contain lots of whitespace. Please note that running compact over and over again will increase fragmentation on disk. There is a good reason to keep whitespace within the NSF, but at the end of the file. Here is a blog post I wrote a long time ago showing how to run compact . also note that this post does not include DMBT
I would suggest that instead putting the threshold on database size, it should be based on % use. Compacting a 90% full db make no sense if the %use is also >= 90%. Once sufficient emails are deleted so that % use dropped to say 80% then compact would be effective.
Tinus Riyanto - Prisma Global Solusi