search mailixf and you find a few cgi tools

I sent and received test messages to both local and non-local hosts without error.

it suddenly just stopped working.  no settings were changed anywhere.

 any explanation for this???

any help is appreciated!

What stopped working? Inbound - outbound, core delivery?

You need to follow the message path through the system as you analyze what has happened.

Can you connect to Mercury via MercuryS?

Can you connect to Mercury via MercuryP?

What happens if you can connect to MercuryS, and you send a message - does the message get accepted or not? if it is accepted and destined to a local account, can you see the core processing the message after reception?

 Etc - only structured fault finding will help you to ask a more specific question here, and then we can help you better.

Sorry, I'll be more specific.

 I have a test user account set up as billgates@0.0.0.0 (my ip address)

for some reason Outlook is saying "can't connect to incoming mail server (POP3)"  and the same for outgoing (SMTP)

 it was working fine, i sent and received mail no problem through Outlook and I could see the work processing through Mercury (MerucryS & MercuryP). now when i try, i get that error in Outlook and the POP or SMTP servers aren't doing anything in Mercury. it's as if they aren't listening or something.

i just sent a test message through Mercury to my gmail address and received it. Although, when I replied to the test message from gmail, it hasn't shown up on the MercuryP yet.

Sounds like your firewall is in the way...

Try a command prompt, type telnet <the ip of your mercury> <portno>

For ex. telnet mercurymachine 110

Would give you a pop3 command prompt like
+OK <1789797987987.2292982@hostname.domain>, POP3 server ready.

And then a flashing prompt, type QUIT, and you get
+OK hostname.domain Server closing down.

 If you have no connection there, something is blocking traffic - or not listening for traffic - even if MercuryP is paused you should get a connection, terminating immediately saying something like, please try again later...

thats what i thought too, but i didn't change any port forwarding settings on my router and remember, the mail was working for a couple test messages.

i did the telnet test like you said, got:

  Connecting To 0.0.0.0...Could not open connection to the host, on port 110
: Connect failed

You have a network or firewall issue.

You are not really using 0.0.0.0 are you?

Are you using the internal or external IP?

Some real info may help.

nono,i'm using my real, external ip address, NOT 0.0.0.0

- the windows firewall is not on
- the ports 25 & 110 are forwarded to the correct machine (happens to be 192.168.1.100). i confirmed this two ways: ipconfig/all and i'm connected to it via VNC, which is port 5900 forwarded to 192.168.1.100
- there are no other firewalls installed on the machine

again, everything was working fine. i made NO changes whatsoever. suddenly, it just stopped working.

i thought maybe this was a trial version of Mercury or something, but I don't see anything saying it is.

Well to get this one correct, you first need to be on the inside (elliminate the port forward problem - work on that later)

At the inside, using a machine on 192.168.1.0 subnet, or even the Mercury machine itself first, connect to 192.168.1.100 via telnet. If this doesn't work - something is interfering your traffic, most likely at the machine itself - or a number of possibilities:

1. You did or the machine did an windows update during the night, and Mercury wasn't started if the machine was rebooted
2. The night update activated the firewall
3. You have antiviral software installed, which "steals" the traffic
4. You have an IP-conflict in your network, making either the gateway hop illegal, or duplicate IP
5. You have new drivers, that for some reason scrambles some tcp-traffic

ok, i just tested again. Outlook says it's finding the servers, it just can't log on to the servers.

outlook says it may have to do with SSL settings, but i have SSL turned off in Outlook, MercuryP and MercuryS

Please - do the basics first - at the same network, use telnet - can you connect to Mercury from the same machine or another machine via port 110?

tried telnetting locally, same error message "Could not open connection to host on port 110"

i tried:
o localhost 110
o 192.168.1.100 110

Then you have something blocking traffic within the machine.

Is MercuryP visible?

You haven't mis-configured MercuryP to listen on IP, another port or anything like that? 

Windows firewall is off? 

Antiviral software?

Extra firewall software? (norton, gatedefender, etc...)

No bogus routes within the machine, look at "route print"

"Is MercuryP visible?"   not sure what you mean by that..   it appears that it is not listening. 

Windows firewall is off.  I uninstalled all antivirus software and there is no extra firewall going on.

Not sure how route print is going to help, could you explain please?

Is the POP3 server module (MercuryP) actually selected as an active protocol module? Can you see the Mercury POP3 Server console window in Mercury? Is MercuryP set to listen on port 110? Are there any connection control entries for MercuryP that might block access?

/Rolf 

MercuryP is selected as an active protocal module.

Mercury POP3 Server console window is visible in Mercury.

MercuryP is set to listen on port 110.

There are no MercuryP connection control entries set.

:-/

very confused...

MercP "IP interface to use" is empty?

TCP/IP networking is loaded?

Can you connect with telnet to any other ports?

Can you ping 127.0.0.1?

MercP IP interface to use is empty

TCP/IP networking is loaded

I can connect to the ftp and ssh servers both locally and non-locally

Packets are sent and received when pinging 127.0.0.1

[quote user="goinbonkers"]

I can connect to the ftp and ssh servers both locally

[/quote]

On the same machine as Mercury?

I'm confused too. It should be working.