Quota problems!

HCL Domino Domino Forum
1

As someone else noted in a previous thread (regarding: e-mail messages held on the server until a person makes enough free space in their mail db), in the Notes documentation it says that:

“After a configured interval, the Router tries to deliver the message” and “Messages that cannot be delivered before the configured expiration time (default = 1 day) are returned…”

However, THERE DOESN’T SEEM TO BE AN INTERVAL FIELD FOR ATTEMPTING RE-DELIVERY OF HELD MESSAGES! (The expiration time is configured via the ‘MailTimeoutMinutes=’ parameter in Notes.ini).

Since this field is missing and I can’t be sure that delivery of the message will occur within a satisfactory period of time (10 to 15 minutes), I’ve enabled the setting ‘Attempt delivery of each message’ so that e-mail held on the server will definitely deliver as soon as enough free space is made in the destination database. This seems to work incorrectly though:

I have a mail file with a 20MB quota, a 19MB warning threshold, and 7MB of free space (13MB used). The user is sent a 12MB e-mail, which should be held on the server until an additional 5MB of free space is made and the used space is reduced to 8 (or perhaps 7) MB. Instead, THE SYSTEM TRIES TO DELIVER THE MESSAGE AND FAILS, resulting in a partial delivery that just serves to further reduce the user’s free space (the amount of used space increases to 18MB before the system realises that there is not enough space and gives the ‘message could not be delivered, over quota warning message’). Other smaller messages that could have been delivered when the amount of used space in the mail db was only 13MB (a 5MB message, for instance) will no longer be delivered, of course. It seems that the test for sufficient free space in the mail file is failing, and the system does try to deliver messages that are too large.

Does anyone know how to set the ‘attempt re-delivery of held messages’ interval, and/or stop the ‘Attempt delivery of each message’ from partially delivering but in the end failing to deliver messages? Could this be a bug, or is it more likely to be a configuration issue?

Thanks,

Paul.

2

Subject: Config Doc

If a message is held because of Quota’s, there is a Quota Control section in the Config Doc that need to be enabled.

Good Luck.

3

Subject: RE: Config Doc

Hi Edmund,

I’m aware of the ‘Quota Controls’ section in the config doc (Router/SMTP - Restrictions and Controls - Delivery Controls). There doesn’t seem to be a field for the re-delivery interval in that section.

Any other ideas?

Thanks,

Paul.

4

Subject: Not sure - doing some testing

I was testing here and getting different results every time. Sometimes the message was delivered less than a minute after the mail file size was reduced. Sometimes the message was delivered up to 5 minutes after the mail file size was reduced.

Sometimes when I issued the “Tell Router Show” command I was getting the next retry as a past time.

sh server

Lotus Domino (r) Server (Release 6.0.1CF1 for Windows/32) 05/01/2003 01:33:47 PM

Server name: brooke/Alpha

Server directory: c:\server\5.0.8\data

Partition: c.server.5.0.8.data

Elapsed time: 00:55:31

Transactions/minute: Last minute: 0; Last hour: 34; Peak: 309

Peak # of sessions: 4 at 05/01/2003 01:00:07 PM

Transactions: 1866 Max. concurrent: 20

ThreadPool Threads: 40

Availability Index: 100 (state: AVAILABLE)

Mail Tracking: Not Enabled

Mail Journaling: Not Enabled

Shared mail: Not Enabled

Number of Mailboxes: 1

Pending mail: 1 Dead mail: 0

Waiting Tasks: 0

Transactional Logging: Not Enabled

Fault Recovery: Not Enabled

Activity Logging: Not Enabled

Server Controller: Not Enabled

tell router show

Msgs State Via Destination

1 Retry( 2) NRPC  [$LocalDelivery] mail\tnolan

                  Last error: Router: Warning: database disk quota exceeded

                  Next retry: 05/01/2003 01:33:25 PM

Transfer Threads: Max = 8; Total = 0; Inactive = 0; Max Concurrent = 4

Delivery Threads: Max = 8; Total = 1; Inactive = 0

5

Subject: Retry interval

The Router will initiate delivery to see if there is work to perform every 60 seconds, or when there is a new message, whichever comes first.

You can turn on DebugRouter=1 and Verbose logging to see these decisions being made (not ready to retry). Including any failed attempts to deliver.