Re: [Fetchmail-users] delay interval

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

Am 04.01.2017 um 18:24 schrieb piequiex:
>> Am 03.01.2017 um 18:00 schrieb piequiex:
>>> Hello.
>>>
>>> Is it possible to set delay interval after every received message? 1-2
>>> seconds.
>>>
>> Hi,
>> no there isn't unless you want to change code or are using the --mda option.
> I have use --mda.
>
>> However, this should never be necessary. Why do you try to do that?
> The problem is I loss all messages, except first two. They all must be parsed
> with script, which I execute from procmailrc.

Then your script or the corresponding .procmailrc is faulty, or procmail
is, or your upstream server is, and it appears something's
asynchronously messing up things for you.

I don't see how you could find a delay interval that would *guarantee*
your setup to not lose mail. Imagine your computer running fetchmail
gets under load or swap pressure and the given delay that worked "in
good weather" is insufficient "in bad weather".

fetchmail waits until the command --mda has completed and obtains its
exit code (or termination signal) through pclose(), before fetching the
next message. You must make sure your script does not terminate
prematurely without losing its exit status, and that procmail properly
processes your script's exit status and conveys it back to fetchmail.
I know this is hard to get really robust with procmail, which is why
I've replaced it more than a decade ago, and warnings against using
procmail have been in fetchmail's manual for years.
(Error-handling endeavours get the typical non-trivial procmailrc on the
brink of becoming unreadable because you need to code all error-trapping
yourself.)

I am not going to help with debugging your procmailrc though, procmail
was abandoned more than 15 years and was retired more than 2 years
ago[1], and its website has disappeared.
I suggest that you debug your script and rigging and plan to migrate to
maildrop or another filtering solution that is still maintained and
supported.

Questions on how to use maildrop with fetchmail's --mda option can be
asked here, for maildrop itself, it has lists on its own.

[1] <https://marc.info/?l=openbsd-ports&m=141634350915839&w=2>

Sorry, this isn't terribly helpful on the short term, but I don't think
that changes to fetchmail's setup would make your script setup robust.
You really need to debug it and prepare yourself to exchange procmail in
the long run.