Hello,
Thank you for your reply. My apologies, I thought these issues were
all possibly interrelated.
To the first issue the postfix process dying. I looked at the service
startup definition on my debian 12 system that's in
/lib/systemd/system/postfix.service I believe this is the section with
the information you requested:
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/bin/true
ExecReload=/bin/true
I stopped and started postfix and used:
systemctl --full --no-pager status postfix
that didn't tell me more than I already knew:
#systemctl --full --no-pager status postfix
? postfix.service - Postfix Mail Transport Agent
Loaded: loaded (/lib/systemd/system/postfix.service; enabled;
preset: enabled)
Active: active (exited) since Thu 2023-07-20 08:31:16 EDT; 11s ago
Docs: man:postfix(1)
Process: 59286 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 59286 (code=exited, status=0/SUCCESS)
Jul 20 08:31:16 hostname.example.com systemd[1]: Starting
postfix.service - Postfix Mail Transport Agent...
Jul 20 08:31:16 hostname.example.com systemd[1]: Finished
postfix.service - Postfix Mail Transport Agent.
I ran "postfix check" I get no warnings. I checked for both selinux
and apparmor neither is installed. I ran "postfix set-permissions"
again no warnings.
I hope this information helps.
Thanks.
Dave.
On 7/19/23, Viktor Dukhovni via Postfix-users <postfix-users@postfix.org> wrote:
> 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
>
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
