Trying to listen to spamd with both ssl and non-ssl fails under FreeBSD.

Dan Mahoney <[email protected]> Sun, 29 Mar 2026 20:14:27 -0700
Newsgroups gmane.mail.spam.spamassassin.general
Message-ID <[email protected]>
Hey there folks,

I'm trying to have spamd listen on port 783 on my local machine, and on port 784 under FreeBSD 14.4.

Startup args include: --port 783 --ssl-port 784 --ssl --server-key /usr/local/etc/mail/spamassassin/spamassassin.key --server-cert /usr/local/etc/mail/spamassassin/spamassassin.crt

As a result I get spamd only listening on port 784.

root@nnn:/home/dmahoney # netstat -na | grep LIST
tcp4       0      0 *.784                  *.*                    LISTEN
tcp6       0      0 *.784                  *.*                    LISTEN

===

The manpage says:

       -p port, --port=port
           Optionally specifies the port number for the server to listen on
           (default: 783).

           If the --ssl switch is used, and --ssl-port is not supplied, then
           this port will be used to accept SSL connections instead of
           unencrypted connections.  If the --ssl switch is used, and
           --ssl-port is set, then unencrypted connections will be accepted on
           the --port at the same time as encrypted connections are accepted
           at --ssl-port.

===

I suspect the manpage is lying about those connections being accepted both encrypted and unencrypted.

Problem 2:

When I do try to connect, using -K:  I am unable to, and there's no good way to debug this:

root@xxx:/home/dmahoney # spamc -K -S -p 784 -d 127.0.0.1
root@xxx:/home/dmahoney # echo $?
74

(Specifying the CA file doesn't help.  Openssl s_client -connect localhost:784 works but can't validate the cert since I don't specify one).

-Dan