Recommended NetWare Server Parameters for the NetWare MTA

The default Maximum Packet Receive Buffers setting on a NetWare server is inadequate for the NetWare MTA in configurations that include numerous TCP/IP and remote file connections. Set Maximum Packet Receive Buffers to at least 2500 for the NetWare MTA in such configurations.

If you are also running the NetWare POA on the same server, see Recommended NetWare Server Parameters for the NetWare POA.

Estimating NetWare MTA Memory Requirements

The amount of memory required for the NetWare MTA is influenced by many factors, including:

• Number of post offices and domains
• Volume of message traffic between post offices and domains
• Volume of large messages (for example, large attachments, remote updates, and so on)
• TCP/IP or mapped/UNC links between MTAs

The table below provides approximate memory requirements for various MTA activities. Actual numbers may vary somewhat from release to release, but the numbers provided do illustrate what activities require relatively more or less memory and what configuration options require more memory than others. This information can be used to produce a rough estimate of the memory required for your particular MTA configuration. Always remember this basic rule when it comes to planning for memory: More is better.

MTA Component	Approx. Memory	References
Agent Engine (gwenn4.nlm)1	5500 KB	(required)
MTA (gwmta.nlm)	469 KB	(required)
Main thread, UI, CSS, logging, statistics	140 KB	(required)
Dispatcher thread	500 KB	(required)
Scanner threads (each)2	40 KB	(required) See Adjusting the Number of MTA Scanner Threads for the Domain and Post Offices. See also /fast0 and /fast4.
Router threads (each)	40 KB	(required) See Optimizing the Routing Queue. See also /maxrouters and /maxidlerouters.
Routing queue      Queue entry size      Queue base size	60 KB 1920 KB	(required)
Direct connections      (1 per domain/post office)	10 KB	(required for direct connections) See Using Mapped or UNC Links between Domains.
TCP master receiver	200 KB	(required for TCP/IP connections) See Using TCP/IP Links between Domains. See also /tcpport.
IP sender threads (each)	15 KB	1 required for TCP/IP connections; up to 4 available)
IP receiver threads (each)3	15 KB	(required for TCP/IP connections) See Adjusting the Number of MTA TCP/IP Connections. See also /tcpinbound.
Admin thread      Idle      Processing	20 KB 125 KB	(required for domain database update and repair) See Displaying MTA Admin Thread Status. See also /noada.
eDirectory user synchronization      (when active)	35 KB	(required for eDirectory user synchronization) See Using eDirectory User Synchronization. See also /nondssync.

¹ The Agent Engine (gwenn4.nlm) needs to be loaded only once per server, no matter how many agents (POAs and/or MTAs) are running on that server, as long as they are running in the same address space.

² By default, there are 2 scanner threads, for a default total of 80 KB. For TCP/IP connections, additional scanner threads are created for each location to which the MTA connects.

³ By default, there are 40 receiver threads, for a default total of 600 KB for inbound connections.

The table below provides some very general memory figures for running both GroupWise agents on the same server.

Concurrent Users	Actual Memory Usage at Peak Time
100 active users (100-250 users in post office)	50 MB
250 active users (250-500 users in post office)	110 MB
500 active users (500-1000 users in post office)	125 MB
1000 active users (1000-2500 users in post office)	150 MB

Recommended Windows Parameters for the Windows MTA

If you are running the Windows MTA for a domain or post offices located on a NetWare server, you might need to increase Maximum File Locks Per Connection from its default setting.

Estimating Windows MTA Memory Requirements

Although the Windows MTA memory requirements differ slightly from the NetWare MTA, you can use the figures provided for the NetWare MTA to see what MTA processes are most memory intensive. See Estimating NetWare MTA Memory Requirements.