I checked the port status both with Mercury running and shut down, using both TCPView (thanks, kwikzilver!) and Telnet, and can confirm that Mercury is the only program responding on port 25.

-=Glen

[quote user="Rolf Lindby"]

Glen: Could you give some more details about your environment please so we can see if there is some common factor that triggers this.

/Rolf 

[/quote]

I have a Windows 2000 Advanced Server, running IIS w/ ASP.NET and a few applications.  Mercury handles all our mail between the Internet and our local users, running a shared copy of Pegasus.  Mail is delivered with the MercuryE module.  Let me know if you need any other info, or if there is a log file at the time of the crash that I can post that gives details of what happened.  Things have been stable for the last week which is good, and I did do a reboot last week when I upgraded our backup software, so maybe that's all it needed.

-=Glen

[quote user="Glen Jackson"]I have a Windows 2000 Advanced Server, running IIS w/ ASP.NET and a few applications.  Mercury handles all our mail between the Internet and our local users, running a shared copy of Pegasus.  Mail is delivered with the MercuryE module.  Let me know if you need any other info, or i[/quote]

Do you run Mercury as service?

Does anything respond if you try to telnet into each port you've set Mercury to work with, if Mercury is not running that is? Reason for me to ask, is that way back in time 2001 or so, we had problems getting IIS on Win2K to pair with Mercury, spite not loading IIS-smtp modules and trying to allocate multiple adapters IIS "stole" all adapters and smtp-ports.

The DOS-command to view ports are: netstat -an

f.ex. to see if port 25 is in listening state type: netstat -an | find ":25 "

Go to Configuration->Protocol Modules and than deactivate "MercuryX connection and process scheduler". Now it should work after restart.

Peter:

I had initially tried running Mercury as a service, but could not figure out how to monitor it this way and generally like leaving the monitor screen on, so I went back to just running it ther old way. I disabled the SMTP server in IIS many years ago when I first set up Mercury, and it is also disabled in WinGate (also running on that server), so there should not be any port conflicts. I will shut down Mercury and test that port this weekend when nobody is emailing. Thanks for the tip!

-=Glen

An additional tip:

You can use TCPView to find out more details about wich application is using what port.This is one of the great tools from SysInternals.

See: http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx