It seems to be a client (I am using Outlook express) issue changing the port to 465 and removing unlinit somewhat solved the issue.
But in I have grep spamdyke /var/log/mail.info Sep 22 07:46:17 server spamdyke[4311]: ALLOWED from: d...@elektronik.dk to: d...@vip.cybercity.dk origin_ip: 127.0.0.1 origin_rdns: (unknown) auth: (unknown) It doesn't ask for authentication 127.0.0.1 is enveloped in the ssl protocol. In fact in many cases users will be able to use my server as open relay. That is not what intended ----- Original Message ----- From: "Sam Clippinger" <s...@silence.org> To: "spamdyke users" <spamdyke-users@spamdyke.org> Sent: Tuesday, September 22, 2009 5:55 AM Subject: Re: [spamdyke-users] I can hardly make a SMTPS connection > Well I can't say with 100% certainty that I understand what's happening > here, but two things jump out at me right away. Both of them are in > your /etc/init.d/qmail file. > > First, your spamdyke configuration file specifies that spamdyke should > expect SMTPS on every incoming connection, but your /etc/init.d/qmail > file instructs tcpserver to listen on the SMTP port (25). This is > possible but very unusual -- SMTPS connections are typically expected on > port 465. If I had to guess, I'd guess this is the problem; incoming > connections are using plaintext SMTP but spamdyke is expecting SMTPS > (SMTP over SSL). > > Second, your /etc/init.d/qmail file uses the "ulimit" command to limit > each spawned process to a maximum of 16 MB of memory. This is pretty > low, especially when the OpenSSL libraries are in use. On my server, I > allow incoming connections to use 80 MB of memory. I suggest either > increasing or removing the limit to see if the behavior changes. > > -- Sam Clippinger > _______________________________________________ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
