> On Aug 20, 2017, at 8:46 PM, Boris Rybalkin <ribal...@gmail.com> wrote:
>
> Let's say I am packaging all those tools myself and I would like to build a
> relocatable package, is it possible to not have null-client?
Will Postfix be responsible for delivering locally generated email
that is injected not via SMTP, but via /usr/sbin/sendmail? If so,
the sendmail(1) command needs to know where to find the Postfix
configuration files, queue-directory etc. Various things that
send email (like e.g. cron) will not be passing around a non-default
config directory, and in any case you still typically need the default
configuration directory in order to use (another) (non-default)
configuration directory.
Postfix is not a small relocatable application, it is a system of
multiple interacting components operating at different privilege
levels (including "root" for master(8) and local(8) so it can run
as other users), maintaining state in queue directories, listening
on network ports, ...).
> Just to explain why do I need all this.
> This is all for syncloud.org open source project where we package popular
> services (mail, files, social network) for end-user's personal use on
> single-board computers (at the moment).
Postfix should be a core component of the system (even if optional),
that is packaged in a fixed location.
> So we would like to package with zero paths in binary and be able to change
> location if needed.
A good idea for various software, especially to support concurrent
multiple versions, but Postfix is not the right software for this
type of deployment.
--
Viktor.
