A 15 Mbit/sec connection (and much more) can easily be handled by Mercury, assuming the hardware is up to it. Make sure there aren't any references to old networking data in the settings, and verify in the task manager that only one instance of Mercury is started after server restart. If there is any real-time antivirus software or similar running, make sure all Mercury directories and email ports are excluded from scanning.

/Rolf 

Mercury server has been having some issues, where it stops recieving mail or pop server stops functioning, or mail stops being delivered.  Restarting server does not help.  I did discover that if I look in task manager the mercury.exe is still resident.  If i force the process closed then start mecury everything is ok.  The only change to the environment is the circuit.  went from a fractional t1 to a 15 meg down 5 meg up circuit and change of ip address.  Is mercury having issue keeping up with the high speed line.  I have appliued the latest release

thank you

The speed of the line should not affect the performance of Mercury as it is the SMTP protocol that is used to send/receive email messages and Mercury simply prepares the messages before they are handed over to SMTP.

What errors are being reported? Does Mercury stop completely (hang), or can you still access other functions within the program. I would look at your logs to try to determine the cause of the failures.