https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8382
Bug ID: 8382
Summary: Issues with SSL port binding in spamd
Product: Spamassassin
Version: 4.0.3
Hardware: PC
OS: Mac OS X
Status: NEW
Severity: normal
Priority: P2
Component: spamc/spamd
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: Undefined
Background: There are two ways to configure listeners on multiple ports with
spamd. You may specify --port and --ssl-port, or you can configure individual
socket listeners using the -i option, i.e. -i ssl:*:784 -i *:783
Additionally, you can configure additional SSL options on the command line,
such as --ssl-ca-path, which inadvertently force all listeners into SSL mode.
Both of these listening options have issues.
If you specify --port 783 --ssl-port 784, you get only a listener on 784.
If you specify the ports using the -i options above, you get the proper
listeners, but adding any additional ssl options can force all listeners into
ssl mode as opposed to only those configured to do ssl.
A pull request was created for this:
https://github.com/apache/spamassassin/pull/25
It fixes the above, plus adds some better documentation around these options.
--
You are receiving this mail because:
You are the assignee for the bug.
