if you specify an invalid IP in listen-address in tpop3d.conf liek 0.0.0.0, or some IP that your machine doesn't own, the init script will say OK when you try to start it, but looking in the logs, and checking running processes shows that it fails to start! I think I'm noticing a general trend in our daemon init scripts with this. Does anyone think this is worth looking over on every single daemon init script? Reproducible: Always Steps to Reproduce: 1. 2. 3.
There is currently no decent way to check for successful startup of tpop3d because tpop3d daemonizes first and fails later. This issue has been sent upstream and will probably be fixed in the next release. If you notice other init scripts that ignore startup failures, please report them separately if they have not been reported already. P.S.: 0.0.0.0 is a valid address
