Re: IMAP Idle in Daemon mode as non-root user
Andrew C Aitchison <[email protected]> Wed, 26 Jul 2023 16:26:48 +0100 (BST)
| Newsgroups | gmane.mail.fetchmail.user |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 26 Jul 2023, [email protected] wrote: > I would like to have multiple Fetchmail instances running on > machine. All instances shall be started directly on system start-up > and running all the time until the system is shutdown. Each of the > instances shall hold one IMAP Idle connection. That sounds reasonable. > Is using the daemon mode the correct way or would it only be > required to start/call each Fetchmail instance once in start-up and > it will continue to run? > What about errors (e.g. interruptions of the IMAP connection), will > fetchmal simply continue its processes or will they abort and have > to be restarted? How to ensure that Fetchmal runs forever and does > never close a process? fetchmail -idle *will* terminate on errors and closed connections; The attached log file shows that it has stopped 52 times for me so far this year; the error 11's were my ISP down for maintenance. So, yes if you cannot have daemon mode and IDLE, you will need some sort of wrapper script, daemon monitor, or cron job that checks and restarts fetchmail when it stops. I have a cron job which summarizes my unread mail a couple of times a day and that reports if the pid-file is missing or there is no matching process. I am only fetching my own mailbox and am happy to restart fetchmail manually ... Personally, if it were important that a service was *always* available I would not trust the daemon providing the service to ensure that is stayed up, but would want something else to monitor and if necessary restart it. >> Gesendet: Mittwoch, den 26.07.2023 um 16:10 Uhr >> Von: "Andrew C Aitchison" <[email protected]> >> An: [email protected] >> Cc: [email protected] >> Betreff: Re: [Fetchmail-users] IMAP Idle in Daemon mode as non-root user >> >> On Wed, 26 Jul 2023, [email protected] wrote: >> >>> is it possible to run IMAP Idle in daemon mode as non-root user? I don't get the point on how to configure the daemon interval if IMAP wants to keep the connection open for "Idle". >>> Wouldn't the daemon interval conflict with the connection that is kept open? >>> >>> Could someone help me with my understanding? >> >> Are you using daemon mode because you want to connect to several >> mailboxes ? In IDLE mode you can only connect to one mailbox, so I >> think the answer is "No, you cannot run IDLE and daemon mode in the >> same process". >> >> If you want to connect in IDLE mode, I would suggest a separate >> FETCHMAILHOME directory, with its own config, and run a separate >> fetchmail -f <configfile> >> process for each mailbox. >> >> -- >> Andrew C. Aitchison Kendal, UK >> [email protected] > > > _______________________________________________ > Fetchmail-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/fetchmail-users > -- Andrew C. Aitchison Kendal, UK [email protected] _______________________________________________ Fetchmail-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fetchmail-users
fetchmail-idle.stopped
(text/plain, 3.6 KB)
fetchmail -idle stopped at Sat 14 Jan 06:25:15 GMT 2023 with error 2 fetchmail -idle stopped at Sat 14 Jan 10:57:44 GMT 2023 with error 129 fetchmail -idle stopped at Sat 14 Jan 10:59:13 GMT 2023 with error 129 fetchmail -idle stopped at Thu 26 Jan 01:17:37 GMT 2023 with error 2 fetchmail -idle stopped at Sat 4 Feb 19:28:58 GMT 2023 with error 2 fetchmail -idle stopped at Sat Feb 4 19:49:30 GMT 2023 with error 129 fetchmail -idle stopped at Sat Feb 4 19:54:44 GMT 2023 with error 0 fetchmail -idle stopped at Sat Feb 4 19:55:01 GMT 2023 with error 0 fetchmail -idle stopped at Sat Feb 4 20:00:33 GMT 2023 with error 129 fetchmail -idle stopped at Sat Feb 4 20:02:01 GMT 2023 with error 129 fetchmail -idle stopped at Sat Feb 4 20:05:02 GMT 2023 with error 129 fetchmail -idle stopped at Sat Feb 4 20:06:22 GMT 2023 with error 129 fetchmail -idle stopped at Sun Feb 12 08:44:18 GMT 2023 with error 2 fetchmail -idle stopped at Tue 14 Feb 03:49:43 GMT 2023 with error 2 fetchmail -idle stopped at Mon 27 Feb 19:54:33 GMT 2023 with error 2 fetchmail -idle stopped at Tue 7 Mar 15:26:03 GMT 2023 with error 2 fetchmail -idle stopped at Sun 12 Mar 18:20:23 GMT 2023 with error 2 fetchmail -idle stopped at Wed 15 Mar 06:25:30 GMT 2023 with error 2 fetchmail -idle stopped at Tue 28 Mar 12:09:54 BST 2023 with error 2 fetchmail -idle stopped at Thu 6 Apr 05:02:54 BST 2023 with error 11 fetchmail -idle stopped at Thu 6 Apr 05:03:30 BST 2023 with error 11 fetchmail -idle stopped at Thu 6 Apr 05:05:29 BST 2023 with error 11 fetchmail -idle stopped at Thu 6 Apr 05:09:27 BST 2023 with error 11 fetchmail -idle stopped at Thu 6 Apr 05:42:33 BST 2023 with error 11 fetchmail -idle stopped at Thu 6 Apr 05:44:44 BST 2023 with error 11 fetchmail -idle stopped at Thu 6 Apr 05:49:09 BST 2023 with error 11 fetchmail -idle stopped at Sat 8 Apr 02:29:55 BST 2023 with error 2 fetchmail -idle stopped at Tue 18 Apr 02:35:13 BST 2023 with error 2 fetchmail -idle stopped at Sat 22 Apr 20:53:31 BST 2023 with error 2 fetchmail -idle stopped at Fri 28 Apr 03:01:58 BST 2023 with error 2 fetchmail -idle stopped at Sun 7 May 08:46:52 BST 2023 with error 2 fetchmail -idle stopped at Wed 10 May 15:49:31 BST 2023 with error 2 fetchmail -idle stopped at Wed May 10 19:14:12 BST 2023 with error 2 fetchmail -idle stopped at Thu May 11 06:01:23 BST 2023 with error 2 fetchmail -idle stopped at Sat May 13 21:52:53 BST 2023 with error 2 fetchmail -idle stopped at Mon 15 May 06:25:12 BST 2023 with error 2 fetchmail -idle stopped at Wed 17 May 10:42:13 BST 2023 with error 2 fetchmail -idle stopped at Sat 20 May 23:49:26 BST 2023 with error 2 fetchmail -idle stopped at Tue 23 May 18:56:04 BST 2023 with error 2 fetchmail -idle stopped at Fri May 26 12:41:39 BST 2023 with error 2 fetchmail -idle stopped at Fri 26 May 21:27:26 BST 2023 with error 2 fetchmail -idle stopped at Sun 4 Jun 16:56:54 BST 2023 with error 2 fetchmail -idle stopped at Sat Jun 10 02:13:44 BST 2023 with error 2 fetchmail -idle stopped at Fri 16 Jun 11:04:50 BST 2023 with error 2 fetchmail -idle stopped at Sat 17 Jun 08:33:59 BST 2023 with error 2 fetchmail -idle stopped at Sun 18 Jun 23:37:22 BST 2023 with error 2 fetchmail -idle stopped at Mon 19 Jun 01:10:04 BST 2023 with error 2 fetchmail -idle stopped at Sun 25 Jun 17:01:56 BST 2023 with error 2 fetchmail -idle stopped at Tue 27 Jun 02:40:55 BST 2023 with error 2 fetchmail -idle stopped at Sat 1 Jul 12:08:57 BST 2023 with error 2 fetchmail -idle stopped at Sat 15 Jul 06:25:10 BST 2023 with error 2 fetchmail -idle stopped at Tue 25 Jul 03:17:04 BST 2023 with error 2