Perfect, all of that makes sense. Here's 3 more:
- The way I understand master.cf is that it spins up services. For
instance, the smtp(d) service to accept incoming connections on port 25, or
qmgr that handles the various queues (like active and deferred). For other
services that wish to interact with say 'verify', how do they do this?
Would it be accurate to compare it to an HTTP routing table? They call
postfix with the service name, and in turn get the executed command?
- Why are Postfix manual pages for these services identical?
- smtp/lmtp
- bounce/trace
- Is there any documentation for the service 'relay'?
On Fri, Oct 15, 2021 at 12:25 AM Viktor Dukhovni <postfix-us...@dukhovni.org>
wrote:
> On Fri, Oct 15, 2021 at 12:15:23AM -0500, Tyler Montney wrote:
>
> > So by private, you mean services that end users shouldn't be able to
> > interact with? Public services have CLI tools (as an interface) whereas
> > private ones do not.
>
> Yes.
>
> > For wakeup, why would a service need wake up timer? It has no active
> > requests so what is it doing when being woke? Perhaps some kind of
> > maintenance tasks?
>
> Services that need to run periodic maintenance tasks are periodically
> woken up by the "master" service. The stock master.cf file has
> reasonable settings for their wakeup timers.
>
> For example, the pickup service periodically scans the "maildrop" queue,
> just in case Postfix was down when a local message was submitted, or
> postdrop(1) failed to notify the pickup(8) service for some reason.
>
> Similary, qmgr(8) periodically rescans the deferred and incoming queues.
> ...
>
> --
> Viktor.
>
