Re: Null-client configuration in MULTI_INSTANCE_README
- On Fri, Dec 28, 2012 at 04:13:39AM -0800, Jay Kay wrote:
> What I am not sure about is the "mtaadmin address group" as itAll non-trivial configuration is on the mailhub, the nullclient
> is called in the readme.
> Does the example assume "mtaadmin@..." is a valid recipient
> at [mailhub.example.org] or is it assumed that "mtaadmin" is aliased
> to the "real" external recipient(s) in another place?
does not do any list expansion.
> From /etc/postfix/virtual it looks like "root" is aliased to aIt is aliased to <mtaadmin@$myorigin>, but without having to
> local user "mtaadmin"
specify the domain explicitly, thus making the recipe site-independent.
> In my test configuration I have replaced "root mtaadmin" withThe envelope recipient does not appear in headers. Since virtual(5)
> "root final.recipient@..." in /etc/postfix/virtual which
> will give me the mails with the correct headers
rewriting applies only to the envelope recipient, this change just
makes the configuration of the nullclient more volatile (likely to
need future changes) with no benefit.
The nullclient configuration is designed to require no ongoing
support beyong choosing the correct "mtaadmin" group (i.e. replace
"mtaadmin" with the name of the system support group for the host
in question). The group will get all mail addressed to root, and
any replies to mail sent by "root".
If necessary you can add similar virtual and generic rewrite rules
for other system accounts, "bin", "lp", ... if they run cron jobs
that may generate email notices.