You don't say which version you are now running, but make sure you are using v4.52 or apply patches to v4.01 to avoid a security issue.  Details are here or on www.pmail.com .

Hi all,

I have inherited support for this mail server for a new client of mine. On Friday someone had incorrectly set the DNS so the server (Windows XP Workstation actually) could not connect to the interenet. After fixing that and then setting the correct SMTP server so it could actually send mail everything looked good. Today I got a call from the client saying they were getting an error when trying to read mail. I have found that Mercury was not running and does not want to start. The steps I have tried so far:

- Restarted the mail server

- Emptied out temp files

- Checked event viewer and Mecury 32 logs - no mention of any problem

- Updated to V4.51 - same problem

If I run the Mecury loader it tries like 14 times to start and I can see the mercury.exe file appearing in the application list in task manager but it keeps dissapearing and eventually gives up.

If anyone can give me any ideas on what to try next it would be really appreciated.

Best Regards,

Michael.

A corrupt mercury.ini can produce these symptoms, although I would have thought updating would fix that (maybe it imported the 'corruption' as an existing setting [:S]).

Try restoring this file (from mercury.bak, mercury.bk2 or an external backup)

The guy who set this up logged on and got it working again, no idea what he did. But it's working is the main thing. I will check what the solution was for next time.

 Cheers,

Michael.