Since thursday or friday, We can't seem to log on to the popserver or send anything to our eserv. Eveverthing else, web, proxy, works just fine.
I tried to look around, but I am currently out of idea.
The only thing I see that is weird, is in ipauthorisation, there is a 0.0.0.0 adresse. I tried to delete it in the eserv.ini but it keeps coming back.
Maybe it as nothing do to with it, but just in case.
Probably, your Eserv gets settings from registry? Have you a file named noreg in the Eserv "root" folder?
Smpt and pop for outside (ISP) seems to be working just fine. We just can't connect to our pop server from internal lan.
All network parametres have not changed in a long time.
ie: 192.168.0.0 255.255.0.0
No file named like that. And it has been working right for months now until that little misshap.
Any ideas?
Do you use tossspool.bat file or integrated antivirus?
Also, please tell Eserv build number.
P.S. noreg file causes Eserv to read settings from Eserv.ini instead of system registry. So, you can edit Eserv.ini and (after restart) get updated settings.
Your special user fax@dtm.com sent a lot of messages for nobody using some strange way. Eserv tries to move these messages to mail\loop folder but fails because disk is full (error code 112). Every POP3 and SMTP connection forces to run Tosser to process huge number of spooled messages but waits because Tosser is a critical section than cannot run more than one time simultaneously. Also, because of large number of messages, every Tosser cycle is very long time. Therefore, it seems that mail server is not responding.
Solution:
Doing a great job helping out.
Have a nice day!
There were still Hard drive space, but too many files in each folder to even answer the requests.