This is interesting. I thought this used to work but testing on a new
Plesk installation shows it doesn't. I think Plesk has patched
qmail-smtpd to start an SSL session when the connection starts on port
465 instead of 25. spamdyke doesn't understand that, so it's waiting
for normal SMTP traffic to start (and doesn't pass the SSL traffic
through correctly).
I've already added a new flag to spamdyke's next version to explicitly
support SMTPS. I'll be sure to test it with Plesk too.
-- Sam Clippinger
Otto Berger wrote:
> Hi,
>
> i have on all of our PLESK-servers a problem the with SSL support. TLS
> works fine so far. But if a client trys to connect via port 465 the
> connection give an timeout (connection died). Did i miss anything?
>
> spamdyke 3.1.5 (also with 3.1.3)
> Fedora and Centos machines.
>
> Thanks in advance,
> Otto
>
>
> My /etc/xinetd.d/smtps_psa:
>
> service smtps
> {
> socket_type = stream
> protocol = tcp
> wait = no
> disable = no
> user = root
> instances = UNLIMITED
> server = /var/qmail/bin/tcp-env
> server_args = /var/qmail/bin/relaylock
> /usr/local/bin/spamdyke -f /etc/spamdyke/spamdyke.conf
> /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true
> /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
> }
>
>
> _______________________________________________
> spamdyke-users mailing list
> [email protected]
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users
_______________________________________________
spamdyke-users mailing list
[email protected]
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
