Testing auth, I set up the following tcpserver line: /usr/bin/tcpserver -R -H -c 400 -g 65534 -u 89 1X9.2XX.2.XX 125 /usr/local/bin/spamdyke-5.0.0 -lexcessive --log-target stderr -f /etc/spamdyke.conf.v5 /var/qmail/bin/qmail-smtpd /var/vpopmail/bin/vchkpw /bin/true
Not using qmail-smtpd patch for auth, attempting to use spamdyke for auth. This line works great for 4.3.1 and has been in production for years on the same system. I did the testing from a shell to open a new port and use it. TLS connects fine and if I use a tcp relay IP file (-x option to tcpserver) then everything proceeds normally, so it's not TLS causing the segfault AFAICT. Here's the specific segfault: Feb 26 14:02:56 XXXX kernel: spamdyke-5.0.0[10230]: segfault at 1 ip 00007fa9661de244 sp 00007fffcc40cdf0 error 4 in libc-2.17.so[7fa966193000+1a3000] The binary is made with ./configure --enable-tls with debug and config-test on (4.3.1 naturally has them turned off for binary size decrease but works either way). _______________________________________________ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
