Slow Mail Server

Slow Exchange Server

 

In an Exchange environment, MailArchiva receives SMTP journaling traffic from MS Exchange and uses a separate connection to synchronize folder structures with MS Exchange. Receiving SMTP traffic is a light operation and has minimal impact on Exchange services. The folder sync operation, however, may have a potentially bigger impact, especially when synchronizing data for the first time.

 

Should your Exchange server become sluggish due to MailArchiva operations, several options are available:

 

  1. It is important to note that you have complete control over the vigor of folder sync operations. After performing each operation, MailArchiva will pause for a period of SyncWait msec. After processing all users in a given cycle, it will wait SyncWaitInterval msec. By increasing the SyncWait and SyncWaitInterval values in Configuration->Connections->Exchange Connection, MailArchiva will give greater pause and consequently lessen the load on the Exchange server. Since each environment is different, and thus, it It may be necessary to experiment with different values.
Note: Prior to MailArchiva V 7.3.2, the SyncWait needed to be adjusted to account for the fact there are around eight separate threads synchronizing at the same time. Thus, a setting of 250 msec would result in an effective 30 msec set delay between operations. In MailArchiva V7.3.3 and higher, the Sync wait value automatically accounts for the existance of parallel threads.

 

  1. Disable folder synchronization altogether. This action will have the effect that folder structures will not appear in the MailArchiva search interface. Folder sync is typically not a requirement for legal e-discovery purposes. To do so, uncheck or disable the Exchange connection in Configuration->Connections and disable the tree view in Configuration->Search. 
Was this information helpful?

Found this information useful? Visit mailarchiva.com to learn more about MailArchiva.

The page cannot be found

The page you are looking for might have been removed, had its name changed, or is temporarily unavailable. Please make sure you spelled the page name correctly or use the search box.