From: Jeremy C. <jd...@ko...> - 2014-11-19 05:24:55
|
On Tue, Nov 18, 2014 at 07:52:24PM -0600, Corey Halpin wrote: > On 2014-11-18, Jeremy Chadwick wrote: > > It's almost as if use of IMAP IDLE causes the daemon to effectively > > ignore any other poll sections. > > From the fetchmail manpage, in "The Run Control File" section, under > "Singledrop vs Multidrop options": > > The 'idle' option is intended to be used with IMAP servers > supporting the RFC2177 IDLE command extension, but does not strictly > require it. If it is enabled, and fetchmail detects that IDLE is > supported, an IDLE will be issued at the end of each poll. This > will tell the IMAP server to hold the connection open and notify the > client when new mail is available. If IDLE is not supported, > fetchmail will simulate it by periodically issuing NOOP. If you need > to poll a link frequently, IDLE can save bandwidth by eliminating > TCP/IP connects and LOGIN/LOGOUT sequences. On the other hand, an > IDLE connection will eat almost all of your fetchmail's time, > because it will never drop the connection and allow other polls to > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > occur unless the server times out the IDLE. It also doesn't work > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > with multiple folders; only the first folder will ever be polled. Thank you Corey! Yup, I didn't actually manage to read that in the man page. Bummer, although that conflicts with the following from section "GENERAL OPERATION": Each server name that you specify following the options on the command line will be queried. If you don't specify any servers on the command line, each 'poll' entry in your ~/.fetchmailrc file ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ will be queried. ^^^^^^^^^^^^^^^^ Back to cronjobs, either that or maintaining two separate fetchmail config files + pid files, etc. :/ -- | Jeremy Chadwick jd...@ko... | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | |