What version are you using? Check your mail box folders, and spool folder for files left behind after the shutdown, particularly single files (they go in pairs, like policemen)
I've found that a message James doesn't like can cause problems when re-starting if it is still in the system. Messages james doesn't like can include messages to an unreachable postmaster, or returned to an unreachable sender. I had problems when my DNS couldn't lookup a meaningful IP address for James to use for itself, though I'm not sure why it checked DNS for local delivery. That said I don't think I've come across any of this in the distributed versions, only from time to time im the CVS version. d. > -----Original Message----- > From: Mike Bridge [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 17, 2001 9:01 PM > To: [EMAIL PROTECTED] > Subject: Problems restarting james > > > Hi- > > I'm just trying out James on Linux, but I find that if I stop > it (by hitting Ctrl-C) and restart it, it stops answering > on port 25 and port 4555. When I try telnetting into those > ports it hangs before printing the welcome message. > > Any ideas what might cause this? I was able to deliver mail > to it before I restarted it. I was able to get it to work > again by reinstalling it from scratch, but each time I > restart it, it stops working. There don't appear to be any > relevant log messages. > > Thanks, > > -Mike > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
