Message delivery occurs when the Router deposits a message in the recipient's mail file.

You
can control how the Router behaves when delivering messages to mail files on the Domino
server. For example, you can specify whether messages are always encrypted, how many
server threads the Router can use to deliver messages, and what the Router does with
messages sent to users whose mail files are larger than the allowed size.
Delivery Controls

Field Description

Maximum delivery The maximum number of server threads Domino can create to deliver
threads mail from MAIL.BOX to local mail files. The Router automatically sets the
default maximum number of delivery threads based on server memory.
Letting the Router select the maximum number is usually best. To set the
maximum number manually, enter a maximum between 1 and 25, based
on the server load.

Encrypt all Choose one:

delivered mail
•Enabled - When delivering messages to local mail files, Domino encrypts
the messages, regardless of whether the sender encrypted the message or
the recipient's mail file encrypts messages.
•Disabled (default) -- Domino encrypts messages only if the recipient's
mail file is set to encrypt received messages.
Note When encryption is enabled and an external user requests a return
receipt for a message sent to a user whose mail file is on the server, the
return receipt message that Domino generates contains a blank message
body.

Pre-delivery agents Users who create LotusScript or Java agents for their mail files can set
that the agent runs before new mail arrives. When delivering mail, if the
Router detects such a pre-delivery agent, it runs it on against message
before the message ever appear in the recipient's Inbox. Use this field to
specify whether the server permits the use of pre-delivery agents. Choose
one:
•Enabled - (default) Allows the Router to run agents that process mail
before delivering it to user mail files on the server.
•Disabled - Prevents the Router from running pre-delivery agents.

Pre-delivery agent The maximum time (in seconds) that a pre-delivery agent, such as a mail
timeout filter, can run before the Router interrupts it. Because the Router waits for
pre-delivery agents to complete, failure to restrict agents can slow
routing performance on the server. The default time-out is 30 seconds.

User rules mail Notes users can create mail file rules that automatically process new
forwarding mail. Client mail rules specify an action to take on newly-delivered
messages that meet certain conditions. Use this field to specify whether
the Router on this server supports the rule action to send copies of
selected messages automatically to other recipients. Choose one:
•Enabled - The Router supports the "Send copy to" action for client mail
rules, allowing users to send copies of messages automatically to other
recipients.
•Disabled - Prevents Notes clients from using the "Send copy to" rule
action.
Quota Controls
Field Description

Over Warning Specifies how often the Router delivers notifications to users who exceed
Threshold their warning threshold.
Notifications
Choose one:
•None - The Router does not deliver notifications when mail files grow
larger than the specified warning threshold.
•Per Message - The Router delivers a notification for every message it
delivers after the mail file exceeds the specified warning threshold.
•Per Interval N - Send notifications at a specified interval until the user
deletes or archives enough messages to bring the size of the mail file
below the specified Warning Threshold. When this option is selected, an
additional field, "Warning Interval Minutes," appears.

Warning Interval Specifies, in minutes, how long the Router waits to send the next Over
Minutes Warning Threshold Notification

Over Quota Specifies how often the Router delivers notifications to users who exceed
Notification their quota.
Choose one:
•None - The Router does not deliver notifications when mail files grow
larger than the specified warning threshold.
•Per Message - The Router delivers a notification for every message it
delivers after the mail file exceeds the specified quota.
•Per time interval - The Router immediately sends an "over quota"
notification to the user's mail file; the notification is sent immediately -- not
according to the specified per time interval setting.

Error Interval Specifies, in minutes, hours, or days how long the Router waits to send
the next Over Quota Notification.

Over Quota Specifies the action the Router takes when receiving new mail for a user
Enforcement whose mail file is larger than the specified quota.
Choose one:
•Deliver anyway (don't obey quotas) - (Default) The Router continues to
deliver mail to a mail file that is over quota.
•Non Deliver to originator - The Router stops delivering new messages to
the mail file and returns a nondelivery message to the sender reporting
that the message could not be delivered because the intended recipient's
mail file was full.
•Hold mail and Retry - The Router stops delivering new messages to the
mail file and temporarily holds incoming messages in MAIL.BOX until space
is available in the mail file. After a configured interval, the Router tries to
deliver the message. If the user has sufficiently reduced the size of the
mail database by the next scheduled delivery attempt, the mail is
delivered. Messages that cannot be delivered before the configured
expiration time (default =1 day) are returned to the sender as
undeliverable.
If you choose this option, the document displays additional fields
where you can specify how the server handles held messages.
Domino mail servers use a MAIL.BOX database to hold messages that are in transit. Mail clients
and other servers use SMTP or Notes routing protocols to deposit messages into MAIL.BOX. The
Router on each server checks the address of each message in MAIL.BOX and either delivers the
message to a local mail file or transfers it to the MAIL.BOX database on another server.
Server processes -- including server threads and the Router -- that write to MAIL.BOX require
exclusive access to it. To ensure exclusive access, processes that write to or read from
MAIL.BOX lock the database to prevent simultaneous access by other processes. Other
processes trying to access the database must wait until the currently active process completes
and unlocks the database before they can complete.
In most cases, a mail process locks MAIL.BOX for only an instant. However, longer wait times
occur when the Router or another process reads or writes a large message. When there is a
large amount of new mail -- for example, on a busy system with heavy mail traffic -- several
server threads may try to deposit mail into MAIL.BOX while the Router attempts to read and
update mail. Under heavy loads, such contention for a single MAIL.BOX database degrades
performance.
On servers that run Domino Release 5 and higher, you can improve performance significantly
by creating multiple MAIL.BOX databases on a server. Using multiple MAIL.BOX databases
removes contention for MAIL.BOX, allows multiple concurrent processes to act on messages,
and increases server throughput. While reading one MAIL.BOX, the Router marks the database
"in use" so other server threads trying to deposit mail move to the next MAIL.BOX. As a further
benefit, having multiple MAIL.BOX databases provides failover in the event that one MAIL.BOX
becomes corrupted.
When creating additional MAIL.BOX databases, consider placing each one on a separate disk.
Because disk contention is rarely an issue for MAIL.BOX, placing each additional MAIL.BOX
database on a different disk will not improve performance per se. However, distributing the
databases across multiple disks does ensure greater availability in the event of a disk failure.
Creating a second MAIL.BOX database offers a large performance improvement over using a
single MAIL.BOX. Depending on server mail traffic, adding a third and fourth MAIL.BOX
database may further improve performance. However, the improvement gained with each
additional MAIL.BOX is increasingly smaller.
You specify the number of MAIL.BOX databases on the Router/SMTP - Basics tab of the
Configuration Settings document. Changes to the mailbox count take effect only after the next
server restart.
After you configure a second MAIL.BOX database, you can use mail statistics to determine
whether additional MAIL.BOX databases are needed.
After the new mailboxes are created, the old MAIL.BOX file is no longer used by the router. Any
messages in MAIL.BOX need to be copied into one of the newly created mailboxes on the
server. The file naming convention used when multiple mailboxes are created is MAIL1.BOX,
MAIL2.BOX, ... MAILN.BOX, where N is the number of mail boxes specified in the Configuration
Settings document.
For more information, see the topic Determining how many MAIL.BOX databases to place on a
server.
To create multiple MAIL.BOX databases
1. Make sure you already have a Configuration Settings document for the server(s) to be
configured.
2. From the Domino Administrator, click the Configuration tab, and expand the Messaging
section.
3. Click Configurations.
4. Select the Configuration Settings document for the mail server or servers you want to
administer, and click Edit Configuration.
5. Click the Router/SMTP - Basics tab.
 6. Complete this field and then click Save & Close:

Field Description

Number of mailboxes Indicates the number of mailboxes (MAIL.BOX databases) on servers

that uses this Configuration Settings document. If this field is blank, one
mailbox is used. Configure a maximum of ten mailboxes.

7. Restart the server to put the new setting into effect.