On Wed, Jul 19, 2023 at 06:03:17PM -0400, David Mehler via Postfix-users wrote:
> I'm trying to migrate to a new setup, Debian 12 with Postfix 3.7 and
> Dovecot 2.3 using virtual mailbox domains. There are no local everyone
> is virtual. The first problem I'm seeing is the Postfix process is
> exiting:
You're packing too many problems into one post, which discourages
substantive help. Best to restart one problem at a time.
> #systemctl status postfix
> ? postfix.service - Postfix Mail Transport Agent
> Loaded: loaded (/lib/systemd/system/postfix.service; enabled; preset: e>
> Active: active (exited) since Wed 2023-07-19 15:02:03 EDT; 4s ago
This is likely because of a mismatch between the service defintion and
the actual Postfix start code it invokes. Is the (ultimately master(8))
process actually expected to remain in the foreground? Or is the
"exited" actually normal here, because the service definition is
starting a "background" job?
See the postfix(1) manpage about various ways to start Postfix, and
see what the service definition is trying to do.
> I suspect this is occurring because of this:
>
> 2023-07-19T15:19:58.474716-04:00 hostname postfix/master[41002]:
> warning: process /usr/lib/postfix/sbin/smtpd pid 41013 exit status 1
No, because master(8) keeps running regardless of whether various
services are failing or not. Once the service startup issue is
put to bed (it is probably fine, but let's get that out of the way),
we can try to solve each of the remaining problems one at a time.
Some of them suggest that perhaps you have SELinux or AppArmor, ...
refusing to allow various kinds of file access.
Run "postfix check" and address any reported problems. If "postfix
set_permissions" does not fix the various file permission problems,
look to disable SELinux or AppArmor.
--
Viktor.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
