Re: [Fetchmail-users] fetchmail not polling multiple servers when IMAP IDLE used

[Matthias A. <mat...@gm...>]

Am 23.11.2014 um 13:13 schrieb Peter Pentchev:
> On Sat, Nov 22, 2014 at 12:45:28AM +0100, Matthias Andree wrote:
>> Am 19.11.2014 um 06:24 schrieb Jeremy Chadwick:
>>
>>> 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,
>>
>> sorry about that.  In my opinion IMAP IDLE is somewhat useless due to
>> its limited applicability.  Either you bind resources on server and
>> client end keeping lots of connections open, or it simply won't work.
>> It may have been conceived as an INBOX monitor but once we start talking
>> about server-side filters, possibly sieve, that assumption seems
>> far-fetched...
>>
>> Thanks for pointing out the inconsistency in the manual page, I have
>> seen do that, and the next fetchmail releases will error out if --idle
>> is combined with multiple mailboxes and/or accounts.
> 
> Hmm, shouldn't it only error out in daemon mode?  I guess it might be
> fine for a single round of checks for new mail.
> 
> G'luck,
> Peter
> 

Hi Peter,

--idle does not look at --daemon, so --idle will make fetchmail sit on
the first polled IMAP mailbox that offers idle support and loop there,
so I presume the refusal should be independent of daemon mode.

Cheers,
Matthias