Soeren Yes, this is a problem with fetchPOP and the earlier versions of fetchmail.
It is not a problem with the version of fetchmail in v2.2.0a10. In this version, if a new run of a fetch task is triggered while another is still running, the new run is skipped. Thrown exceptions stopping all message fetching is also fixed in this version, as are many other small and not so small issues. Which ever timer you use with fetchPOP you will still want to ensure that whatever happens... 1) a new fetch task never runs before the old one has completed 2) if the old fetch task fails a new one will run. All in all you might find it easier to switch to the new fetchmail as fetchPOP is being deprecated. Any help wringing the bugs out of that would be appreciated. -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
