-- bump --

Still have this sissue, and as far as I know, the dns enteries are right, as it is using the same values that our old mail server is using, and it was working/running.

I am not sure what else to do here? Help?

I have checked via telnet both ports 25 and 110 *just to be sure*.

From the server, everything is fine (out to mail.mailenable.com, and locally), then from another server on a different conenction to the problem server, and it was fine also.

So, it does not seem like a blocked port.

Ok... i hope this helps show something. I did a test email from outlook, and it went through perfectly, so it will send email locally, but as soon as i tried to send to an external address (gmail.com) it sits and waits. Here is the log: *** SMTP ACTIVITY LOG *** 05/23/07 15:52:14 SMTP-IN B2F7410E5D4...

I have looked at trying that... and there is no record of the email going through the server... which is REALLY weird. I will try it again, and post results.

I have all the logs logging, so i will check EVERY log file that there is.

there is no log generated, as the file is never being sent. I just dont get it. There is no reason for this? I have everythign set up (at least I am 99% positive), and it is accepting incoming, and everything.... as soon as I try to send out, nothing happens. I just dont get it. why can't i just sen...

OK... I looked into it a little further, I had changed my SMTP setting back to my ISP, so anyway, I changed it back to the Mail Enable's SMTP, and sent out an email. I have followed the logs (I have EVERY log logging) and it does not show anything about that email I tried. I know it was accepted, as...

You do know that the 10030 hotfix is a MailEnable SMTP hotfix? Available from our web site hotfix page? What do the logs say when the messages are trying to be sent? The debug logs should be showing errors of the message send failures. Yes, the hotfix has been applied already, and as for the log fi...

Ok... yes, that would be the problem, i see the check box, and i now checked it, as well, the 16, was the max number of concurrent connections allowed (when i didn't even check the allow checkbox on the next tab). Hope this fixes the problem

v2.37 (fresh install of 2000 server) and all patches/hotfixes are up to date. It was a standalone download and install of MailEnable, so PLESK is not installed.

I hope that this is just a local problem to you (no offense), as I just installed the ClamWin on my mail server, and so far, it is working well. We are going to be migrating our clients over to the new server once we get the baysian filter working a little bit better. I am curious to see if in fact ...

If you are running Professional version 2 then you can enable the concurrent mailbox access feature in the POP properties. we are using Pro v2.37 and I have the concurrent connection from teh default 16, to now 50. It still every now and then gives me that same issue, for no reason, then after some...

I have 85 messages in my outbound queue that have been there for a few days, and I cannot send them. I have right-clicked and send all now, and it still does not send.

The email is not generating any delivery failures, or anything? I am stumped.

OK... I did it. It has been changed, yet when in the Received column of Outlook, it still shows +1hour after the sent time.

When I look at the header information, it says the timezone is -400, when i am -500... this is weird...

lol... look at the times on the server here... it says i replied at 10:11 am, and my time zone is set to -5 hours (which is where i am).

Why did they have to go and change the time for the time zone

I have a brand new install of 2000 server, all updates, fresh install of Mailenable Profession v2, updates of mailenable, the version is 2.37, there are no more updates to do. I am in Ontario Canada, with the new eastern time zone change fro daylight savings time. I dont know what is wrong, but my t...