I have an installation of ESERV2 2.97 build 3114 on Windows 2000 pro that has been live for about 10 months. It has behaved exceptionally until today — it stopped smtpsend and pop3 receive from ISP. Internal mail behaves normally. Passwords etc haven't changed.
I believe that the eserv2\temp directory had so many files (typically .eml and .toss) that the machine was unhappy to do things with that directory. I could not browse it. I eventually did a "rd temp /s" from command line to remove it (EServ service was disabled) and then I recreated the temp directory and started EServ service. Symptons remain.
Do you believe the temp directory overfilling would cause these symptoms? Is Eserv meant to clean these files or should I do it periodically? Any other suggestions?
There is also a 0 bytes file that has a funny character followed by the word mailto in the spool folder that stays there. Logs seem to show it has been there a while so it shouldn't be causing this problem. Should I delete it?
Thanks in anticipation.
David Boro
However further advice on the temp folder would be good?
Also I have a number of messages now in the mail\loop folder. I don't really understand the loop directory. Is this a concern?
Should a file entitled "-" be present in the mail\in folder. It appears not to have been modified since initial installation.
Cheers
David
These temporary files are remained as log files for further analysis if needed. You should regularly remove unnecessary files to prevent the overflowing of the disk.
Yes. You don't need this file.
These are messages that cannot be delivered to recipient. Examine them.
This is the phantom mailbox of an "unnamed" user. Remove it.