Thank you both for the hints, I rebooted and saw no change when testing.
On a guess I used "systemctl stop postfix" and tried to manually start postfix
with
"postfix start" at the command line.
Strangely that allows the openssl test command to work perfectly ?!
I am able to repeat the starting and stopping of postfix at will with command
"postfix start/stop" and things seem to work.
Even used T-bird and sent myself and email.
Oct 11 15:38:36 mail6 postfix/submission/smtpd[3371]: 33C2318002F8:
client=angelo.uits.uconn.edu[137.99.80.129], sasl_method=PLAIN,
sasl_username=abb17003
Oct 11 15:38:36 mail6 postfix/cleanup[3379]: 33C2318002F8: warning: header
Subject: real test mail6 from angelo.uits.uconn.edu[137.99.80.129];
from=<alf02...@appmail.uconn.edu> to=<ang...@uconn.edu> proto=ESMTP
helo=<[137.99.80.129]>: HEADER_CHECKS(5)
I think I need to research how RHEL7 and systemctl crank up Postfix.
Thanks.
P.S.
In case someone sees something obvious, 1st try fails but strangely 2nd try
works fine...and port 465 works 587 no.
1ST TRY
[root@mail6 ~]# systemctl start postfix
Job for postfix.service failed because the control process exited with error
code. See "systemctl status postfix.service" and "journalctl -xe" for details.
[root@mail6 ~]# systemctl status postfix.service
â postfix.service - Postfix Mail Transport Agent
Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; vendor
preset: disabled)
Active: failed (Result: exit-code) since Fri 2019-10-11 15:41:41 EDT; 8s ago
Process: 3053 ExecStop=/usr/sbin/postfix stop (code=exited, status=0/SUCCESS)
Process: 3488 ExecStart=/usr/sbin/postfix start (code=exited,
status=1/FAILURE)
Process: 3485 ExecStartPre=/usr/libexec/postfix/chroot-update (code=exited,
status=0/SUCCESS)
Process: 3482 ExecStartPre=/usr/libexec/postfix/aliasesdb (code=exited,
status=0/SUCCESS)
Main PID: 2985 (code=killed, signal=TERM)
Oct 11 15:41:40 mail6.its.uconn.edu systemd[1]: Starting Postfix Mail Transport
Agent...
Oct 11 15:41:41 mail6.its.uconn.edu systemd[1]: postfix.service: control
process exited, code=exited status=1
Oct 11 15:41:41 mail6.its.uconn.edu systemd[1]: Failed to start Postfix Mail
Transport Agent.
Oct 11 15:41:41 mail6.its.uconn.edu systemd[1]: Unit postfix.service entered
failed state.
Oct 11 15:41:41 mail6.its.uconn.edu systemd[1]: postfix.service failed.
2ND TRY
[root@mail6 ~]# systemctl status postfix
â postfix.service - Postfix Mail Transport Agent
Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; vendor
preset: disabled)
Active: failed (Result: exit-code) since Fri 2019-10-11 15:41:41 EDT; 1min
20s ago
Process: 3053 ExecStop=/usr/sbin/postfix stop (code=exited, status=0/SUCCESS)
Process: 3488 ExecStart=/usr/sbin/postfix start (code=exited,
status=1/FAILURE)
Process: 3485 ExecStartPre=/usr/libexec/postfix/chroot-update (code=exited,
status=0/SUCCESS)
Process: 3482 ExecStartPre=/usr/libexec/postfix/aliasesdb (code=exited,
status=0/SUCCESS)
Main PID: 2985 (code=killed, signal=TERM)
Oct 11 15:41:40 mail6.its.uconn.edu systemd[1]: Starting Postfix Mail Transport
Agent...
Oct 11 15:41:41 mail6.its.uconn.edu systemd[1]: postfix.service: control
process exited, code=exited status=1
Oct 11 15:41:41 mail6.its.uconn.edu systemd[1]: Failed to start Postfix Mail
Transport Agent.
Oct 11 15:41:41 mail6.its.uconn.edu systemd[1]: Unit postfix.service entered
failed state.
Oct 11 15:41:41 mail6.its.uconn.edu systemd[1]: postfix.service failed.
[root@mail6 ~]#
[root@mail6 ~]#
[root@mail6 ~]# systemctl start postfix
[root@mail6 ~]# systemctl status postfix
â postfix.service - Postfix Mail Transport Agent
Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; vendor
preset: disabled)
Active: active (running) since Fri 2019-10-11 15:43:06 EDT; 3s ago
Process: 3053 ExecStop=/usr/sbin/postfix stop (code=exited, status=0/SUCCESS)
Process: 3551 ExecStart=/usr/sbin/postfix start (code=exited,
status=0/SUCCESS)
Process: 3548 ExecStartPre=/usr/libexec/postfix/chroot-update (code=exited,
status=0/SUCCESS)
Process: 3545 ExecStartPre=/usr/libexec/postfix/aliasesdb (code=exited,
status=0/SUCCESS)
Main PID: 3623 (master)
Tasks: 3
Memory: 2.9M
CGroup: /system.slice/postfix.service
ââ3623 /usr/libexec/postfix/master -w
ââ3624 pickup -l -t unix -u
ââ3625 qmgr -l -t unix -u
Oct 11 15:43:06 mail6.its.uconn.edu systemd[1]: Starting Postfix Mail Transport
Agent...
Oct 11 15:43:06 mail6.its.uconn.edu postfix/master[3623]: daemon started --
version 2.10.1, configuration /etc/postfix
Oct 11 15:43:06 mail6.its.uconn.edu systemd[1]: Started Postfix Mail Transport
Agent.
-ANGELO FAZZINA
ang...@uconn.edu
University of Connecticut, ITS, SSG, Server Systems
860-486-9075
-----Original Message-----
From: owner-postfix-us...@postfix.org <owner-postfix-us...@postfix.org> On
Behalf Of Thilo Molitor
Sent: Friday, October 11, 2019 3:14 PM
To: Postfix users <postfix-users@postfix.org>
Subject: Re: Trying to understand error message in logs
...and check permissions on *all* the directories in the path leading to the
lockfile for proper access (at least eXecute permission) and no conflicting
ACLs
(as viktor already wrote).
--tmolitor
Am Freitag, 11. Oktober 2019, 15:00:36 CEST schrieb Viktor Dukhovni:
> Reboot your system, and try again.
>
> > On Oct 11, 2019, at 2:49 PM, Fazzina, Angelo <angelo.fazz...@uconn.edu>
> > wrote:
> >
> > Hi, thanks for the tip about checking SELINUX. Sadly no change when
> > testing openssl command with SELINUX off.
> TLS has nothing to with this. The SMTP server is unable to
> lock a file that is used to avoid waking up all the SMTP
> listeners every time a new connection arrives. The lock
> file ensures that only listener is waiting to accept new
> connections at a time.
>
> The EPERM error is not normal in this context. On my
> system:
>
> $ ls -ld /var/spool/postfix{,/pid{,/inet.smtp}}
> drwxr-xr-x 16 root wheel 16 Aug 4 22:46 /var/spool/postfix
> drwxr-xr-x 2 root postfix 19 Apr 18 04:43 /var/spool/postfix/pid
> -rw------- 1 root postfix 0 Feb 19 2017
> /var/spool/postfix/pid/inet.smtp
>
> which shows that only root can open the lock file, and yet
> there are no issues with the lock, because Postfix opens
> the file before dropping privs. So if you're seeing EPERM,
> your system is either configured with additional security
> restrictions, or has become confused and needs a reboot.
>
> Also, make sure there are no additional extended ACLs on the file,
> immutable bits, ... Good luck.
>
> Don't waste time with TLS, that's entirely irrelevant.
