didier20
asked on
Quota checking doesn't work
Hi All,
There's lots of user in our company who are using Lotus Notes and all of them are satisfied with it except 2 people.
The one from that 2 people is a "normal user" but the other is my General Manager.
The Manager gets huge amount of mails and his mailbox is growing very big.
Unfortunately, the quota checking doesn't work and so sometimes the Local replica looks different than his mailbox on the server. In such case I tell him to archive the old mails and compact the Local mailbox afterwords. This is OK for a while but after some months his mailbox exceeds its limit the synchronizing process goes wrong and the problem begins again.
I've already reinstalled Lotus Notes on his laptop tried refresh design and replace design but it didn't help.
I'm a big trouble I don't know what else I could do to fix the problem. The manager is very angry because he's very busy and has no time to look through hundreds of mails after I create a new Local replica for him.
Every man uses the same design the same server and so on. Why doesn't work the Quota checking properly? Is the server mailbox or the Local or the design to blame?
What can I do?
There's lots of user in our company who are using Lotus Notes and all of them are satisfied with it except 2 people.
The one from that 2 people is a "normal user" but the other is my General Manager.
The Manager gets huge amount of mails and his mailbox is growing very big.
Unfortunately, the quota checking doesn't work and so sometimes the Local replica looks different than his mailbox on the server. In such case I tell him to archive the old mails and compact the Local mailbox afterwords. This is OK for a while but after some months his mailbox exceeds its limit the synchronizing process goes wrong and the problem begins again.
I've already reinstalled Lotus Notes on his laptop tried refresh design and replace design but it didn't help.
I'm a big trouble I don't know what else I could do to fix the problem. The manager is very angry because he's very busy and has no time to look through hundreds of mails after I create a new Local replica for him.
Every man uses the same design the same server and so on. Why doesn't work the Quota checking properly? Is the server mailbox or the Local or the design to blame?
What can I do?
There were major changes between R5 and R6, includng Quota handling.
Quotas are only warnings in general.
What are you expecting Quotas to do for you ?
How much mail are we talking about ?
I have users with over 7 GB on their Local replica and do not have issues.
Make sure you use the newest Client that you can, preferably R 6.55 or R 7.02
I hope this helps !
Quotas are only warnings in general.
What are you expecting Quotas to do for you ?
How much mail are we talking about ?
I have users with over 7 GB on their Local replica and do not have issues.
Make sure you use the newest Client that you can, preferably R 6.55 or R 7.02
I hope this helps !
ASKER
We're using R6.5
I want to copy the quota agent from R5 template (where it works) to the R6 template.
I did it but it doesn't work in the R6 template and I don't know why.
Isn't enough to copy/paste the 1 agent?
When the user open his mailbox a message should appear with his currently mailbox size.
The most important thing would be for me:
The user shouldn't be able to send mails when his mailbox size is over the limit.
This is how it works for those who're using the newer template.
I want to copy the quota agent from R5 template (where it works) to the R6 template.
I did it but it doesn't work in the R6 template and I don't know why.
Isn't enough to copy/paste the 1 agent?
When the user open his mailbox a message should appear with his currently mailbox size.
The most important thing would be for me:
The user shouldn't be able to send mails when his mailbox size is over the limit.
This is how it works for those who're using the newer template.
ASKER
Correction:
This is how it works for those who're using the "older" template.
This is how it works for those who're using the "older" template.
OK, you may also need to see that you have both these routines
Call chkquotaAgent
Call ReleaseSpace
in the Common script library, and also you need to find out where the agent is called from, perhaps from the DB PostOpen ( see Other- Database resources - PostOpen ) in the Design CLient.
I hope this helps !
Call chkquotaAgent
Call ReleaseSpace
in the Common script library, and also you need to find out where the agent is called from, perhaps from the DB PostOpen ( see Other- Database resources - PostOpen ) in the Design CLient.
I hope this helps !
If you're talking about a pop-up dialog box that warns users when their mail file exceeds a limit, then neither the R5 or R6 mail template has this functionality. There is no chkQuotaAgent or ReleaseSpace script libraries in the R5 or R6 mail templates that I can find.
The openNTFmail experience: http://www.openntf.org/projects/pmt.nsf/ProjectLookup/OpenNTF%20Mail%20Experience
Does have a check quota routine in it's template that DOES use a pop-up dialog box that you may be able to use.
In your current configuration, the R6 quotas work if the quota is set above the current mail file size. For example, if the current mail file has 250 mb, and you set the quota to 225, then you have to wait for the mail file to be reduced to below 225 for the quota to start working.
Then, the router sends an email message (there is a quota form in the R6 mail template), and not a pop-up dialog box.
The openNTFmail experience: http://www.openntf.org/projects/pmt.nsf/ProjectLookup/OpenNTF%20Mail%20Experience
Does have a check quota routine in it's template that DOES use a pop-up dialog box that you may be able to use.
In your current configuration, the R6 quotas work if the quota is set above the current mail file size. For example, if the current mail file has 250 mb, and you set the quota to 225, then you have to wait for the mail file to be reduced to below 225 for the quota to start working.
Then, the router sends an email message (there is a quota form in the R6 mail template), and not a pop-up dialog box.
Oh, to answer your question, the server checks the quota on the SERVER version, and not on the local replica. So, a lot of people disable sending deletions to the local replica, this way they can keep stuff locally, and not affect their server size. The local replica can grow to many times the size of the server database and not be affected by quotas since the Server only applies the quota to the database it controls on the server. It cannot manage what it cannot see.
Of course the down side to keeping stuff locally is if the client crashes and you lose the hard drive, then all the saved local mail may be lost if it isn't being backed up.
Of course the down side to keeping stuff locally is if the client crashes and you lose the hard drive, then all the saved local mail may be lost if it isn't being backed up.
ASKER
Marilyng,
You say that "the server checks the quota on the SERVER version"
But if I open the user mailbox on the server there's no quota warning at all for the users who're using the R6 template. Though the quota is set in the Administrator.
SysExpert,
I copied the 2 routines into the Common script library. Still no quota reminder.
Other- Database resources - Database Script - PostOpen is empty
You say that "the server checks the quota on the SERVER version"
But if I open the user mailbox on the server there's no quota warning at all for the users who're using the R6 template. Though the quota is set in the Administrator.
SysExpert,
I copied the 2 routines into the Common script library. Still no quota reminder.
Other- Database resources - Database Script - PostOpen is empty
ASKER
Is this correct when I say that the quota warning should work on the server if the quota is set in the Administrator?
If it's so, I don't understand why the central admin added the quota check agent and 2 routins to the design in the R5 template. Does it apply to the Local mailbox?
Inthat case it would be doable the have 2 different quota for a user mailbox. 1 for local and 1 for the server?
If it's so, I don't understand why the central admin added the quota check agent and 2 routins to the design in the R5 template. Does it apply to the Local mailbox?
Inthat case it would be doable the have 2 different quota for a user mailbox. 1 for local and 1 for the server?
ASKER
The users who have the R5 template gets the quota warning on local and on the server as well.
The users who have the R6 template gets no quota warning neither on local nor on the server.
In both of the cases the quota is set in the Admin.
Why doesn't send the server warnings?
The users who have the R6 template gets no quota warning neither on local nor on the server.
In both of the cases the quota is set in the Admin.
Why doesn't send the server warnings?
Depends. The R5 template might have additional libraries in the database events to programmatically check for quota and display the message. When the server does the message, it appears as an email in the inbox. When you add a bit of programming that has been published in a couple of forums, then it appears as a messagebox when the database is opened. In the second case, the warning appears in both the server and local copy.
The server will only send warnings if the quota was implimented while the mailbox size was below the quota. For example, if the mail box size was 250 mb, and you set the quota for 225 mb, then no warnings will be sent.
The server will only send warnings if the quota was implimented while the mailbox size was below the quota. For example, if the mail box size was 250 mb, and you set the quota for 225 mb, then no warnings will be sent.
ASKER
I understand. I want to add this programming part to R6 template.
I did following:
I copied an agent from R5 to R6 that calls 2 routines ( chkquotaAgent and ReleaseSpace)
I copied the 2 routines into the Common script library
I guess that this isn't enough because it doesn't work. What's the exactly procedure you mentioned was published in the forum?
I did following:
I copied an agent from R5 to R6 that calls 2 routines ( chkquotaAgent and ReleaseSpace)
I copied the 2 routines into the Common script library
I guess that this isn't enough because it doesn't work. What's the exactly procedure you mentioned was published in the forum?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The 2 users are using the mail6.ntf and the other mail5.ntf
With the mail5.ntf is everything OK but when I have a look at the Agent list in mail6.ntf I can't see the check quota agent.
I copied this agent from the mail5.ntf and pasted it to the mail6.ntf but it doesn't work. I tried to copy it directly to the database but it doesn't work either.
The chkquota agent looks very simple.
Option Public
Use "Common"
and
Sub Initialize
Call chkquotaAgent
Call ReleaseSpace
End Sub
Why doesn't work it?
I checked the agent list where it works but couldn't find any other I could copy.
The chkquota Agent calls itself? Or it calls what's in the program by default?
E.G. when I set the quota in the Admin client?