On Sat, Dec 14, 2024 at 11:16:47AM +0300, Michael Tokarev via Postfix-users
wrote:
> What's the reason for the pickup daemon to be waked up every 60s?
> Either on a modern system, or at all?
Because "wakeup" signals from postdrop(1) are not reliable. Absent
frequent message arrival, with postdrop(1) wakeup signals getting
through, messages could otherwise linger in the "maildrop" queue
indefinitely.
> Why it needs to be awaken in the first place, - does it miss mail
> when the system is up and running?
Typically not, but the wakeup makes sure nothing is lost.
> It looks like this wake-up time can be increased way past max_idle
> these days, say, to be 10 minutes or so - and in this case, there
> will be one less postfix process running all the time. Especially
> on systems where local mail submission is not a thing at all.
This can lead to rather long message delivery delays, and should not be
a default setting on server systems. If you want Postfix to be battery
friendly on laptops, take a look at Apples' patches that only start
Postfix when a message arrives, and somehow know to stop it once there's
nothing to do (ideally reliably with the queue empty).
> Ditto, I think, for qmgr - on an idle system where postfix is used
> to send mail maybe once a day or a week, there's no reason to constantly
> rescan the queue. But this is something else still.
Perhaps Postfix is not the right fit for such systems, but if you want
to go the Apple route, look closely at their approach, do at least as
well, and don't repeat their mistakes.
--
Viktor.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
