Am 01.02.2012 21:14, schrieb Johann 'Myrkraverk' Oskarsson:
> Rob MacGregor <rob...@gm...> writes:
>
>> If you have a single daemon polling all the mailboxes, impossible. If
>> you have one daemon per mailbox, trivial (see the SIGNALS section of
>> the man page).
>
> Not really impossible. It's just a matter of adding some IPC mechanism
> and probably some other features that allow the command line client to
> tell the daemon which mailbox to pull.
>
> Depending on the complexiting of the sources, this may be close to
> impossible.
IPC isn't the issue here, but sorting the command line parsing and
"which mailbox is active" stuff out is, and that work would entail
getting rid of the "no command line options permitted with running
daemon"...
I'd presume it's an effort that might easily amount to two dozen hours
for someone moderately acquainted with the sources because it requires
adaptations in multiple parts of the code.
Also, fetchmail would need to lock individual mailboxes against
concurrent access -- but instead, it locks the whole process instead,
which is another obstacle.
I suppose fetchmail 8 might follow a different model compared to all
earlier versions, more modular, which would make such code additions
easier. I haven't yet made a real plan, as fetchmail 7 would have to
happen first (with less radical changes), yet real life has gotten in
the way of things again.
> I suppose it's rarely needed so I don't think it's worth much efford; as
> it's quite easy to have a different daemon per mailbox.
Plus you can stop the daemon, run fetchmail with "-d0" option (to defeat
the daemon mode) + the server's name (from the "poll" option) on the
command line, and then restart the original daemon.
No big deal from the command line, quite a big deal in code adaptation.
Best regards
|
