Re: [courier-users] submission problems

[Ángel <an...@16...>]

On 2023-01-05 at 20:55 +0100, co...@ec... wrote:
> Hi,
> 
> I updated my courier-mta server from version 1.1.8 to 1.1.10.
> 
> It starts up without problems, imap over ssl also works (port 993).
> But when I try to use smtp over ssl (port 465), it does not work
> anymore as before.
(...)


IMAP over ssl works, while SMTP over SSL fails to establish the
connection. But both are the same at that point, using the same
binaries.

The working IMAP over tls will have a process similar to:
/usr/sbin/couriertcpd -address=0 -maxprocs=... -maxperip=... -access=/etc/courier/imapaccess.dat -nodnslookup -noidentlookup 993 /usr/bin/couriertls -server -tcpd -user=courier /usr/lib/courier/courier/imaplogin ...

whereas SMTP over tls should look basically the same but running courieresmtpd instead of imaplogin, e.g.

/usr/sbin/couriertcpd -stderrlogger=/usr/sbin/courierlogger -stderrloggername=esmtpd-ssl -maxprocs=... -maxperip=... -maxperc=... -pid=/var/run/courier/esmtpd-ssl.pid -stderrlogger=/usr/sbin/courierlogger -noidentlookup -user=courier -group=courier -access=/etc/courier/smtpaccess.dat -address=0 465 /usr/bin/couriertls -server -tcpd /usr/sbin/courieresmtpd


Assuming the later is running (as it probably does, since *something*
is replying on that port), you should check why is couriertls not .
Have a look at the TLS_CERTFILE= configured for the esmtpd-ssl, you can
verify it is indeed set for that binary looking at /proc/<pid>/environ
and also that the user under which it is running is able to open the
file (including all intermediate folders)