Hi,
Thanks for your answer, can you add few words to describe problem and solution?
Problem: a) The checking interval may be too short, i.e. the last job is still running and fetching mails when cron triggers the next one (maybe due to a large amount of mails or big mails with attachments). However, the default is 10 minutes and that should be ok. b) The process may have been aborted because of whatever (check the logs). Now, in the next run the process detects that there seems to be its predecessor still running. However, it just did not finish cleanly and left the PID behind. Possible Solution: You can run the command suggested by Gustave, which uses the "force" option. If the problem persists you may want to check the database table "process_id". Delete any entries belonging to the postmaster pop 3 process. On the next run it should run now smoothly again. HTH, Tobias -- Tobias Lütticke Systems Architecture inovex GmbH Pforzheim (Head Office) Karlsruher Strasse 71 D-75179 Pforzheim Tel.: +49 (0)72 31 / 31 91 - 84 Fax: +49 (0)72 31 / 31 91 - 91 mailto:t.luetticke@inovex.de http://www.inovex.de