When using mapped or UNC links between the local domain and its post offices and other domains, the MTA can create a lot of network traffic just scanning its input queues, especially if the message load is light. This can be minimized by setting the scan cycle to a higher number. On the other hand, if the scan cycle is set too high, important messages might have to wait in the input queues to be picked up by the MTA.
By default, when using mapped or UNC links, the MTA scans its high priority queues every 5 seconds and its regular and low priority queues every 15 seconds. You can adjust the scan cycle settings to meet the needs of your GroupWise® system.
In ConsoleOne®, browse to and right-click the MTA object > click Properties.
Click GroupWise > Agent Settings to display the Agent Settings page.

Decrease the number of seconds in the Scan Cycle field if you want the MTA to scan the regular and low priority queues (2-7) more often.
or
Increase the number of seconds in Scan Cycle field if you want the MTA to scan the regular and low priority queues (2-7) less often.
Decrease the number of seconds in the Scan High field if you want the MTA to scan the high priority queues (0-1) more often.
or
Increase the number of seconds in the Scan High field if you want the MTA to scan high priority queues (0-1) less often.
For the locations and specific uses of the MTA input queues, see Message Transfer/Storage Directories in Troubleshooting 3: Message Flow and Directory Structure.
Click OK to save the new scan cycle settings.
ConsoleOne then notifies the MTA to restart so the new settings can be put into effect.
Corresponding Startup Switches
You could also use the /cylo and /cyhi switches in the MTA startup file to adjust the MTA scan cycle.