On Mon, Dec 10, 2001 at 07:55:07AM +0100, Roland Schneider wrote:
Nothing special needed, start the daemon as usual and
SSL/TLS will work if the other end also knows about TLS.
Send mail to cour...@lists.sourceforge.net
and look at the headers in the response. They will show
if everything worked out, just like the headers in this
post.
Without any information from your side I just recommend
RTFM again, and dont forget to generate and specify the
certificate.
Appreciate the feedback. The issue I have is that evolution doesn't know
about STARTTLS. I haven't generated the certificate yet, but I'll see if
the error message below is spurious and that's the real issue.
[root@odin conf]# /usr/lib/courier/sbin/couriertcpd -address=0 \
-stderrlogger=/usr/lib/courier/sbin/logger -stderrloggername=esmtpd-ssl \
-maxprocs=20 maxperip=20 -pid=/var/spool/courier/tmp/emsptd-ssl.pid \
-nodnslookup -noidentlookup smtps /usr/lib/courier/bin/couriertls \
-server -tcpd /usr/lib/courier/sbin/courieresmtpd \
/usr/lib/courier/libexec/courier/modules/esmtp/authstart authdaemon
/usr/lib/courier/sbin/couriertcpd: -pid argument is required.
[root@odin conf]#
I'm using a combination of paramaters that appear in imapd and esmtpd's tcp
listeners that appear to me should work, but this particular error message
is throwing me.
5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] smtps again
