Eric,
at the moment I use the same file the "normal" qmail installation use.
spamdyke.conf:
tls-dhparams-file=/var/qmail/control/dh1024.pem
2014-03-28 20:08 GMT+01:00 Eric Shubert :
> On 02/05/2014 06:34 AM, Marc Gregel wrote:
> > Just for the records:
> > With Version
-file=/var/qmail/spamdyke/whitelist_ip
> sender-whitelist-file=/var/qmail/spamdyke/whitelist_sender
> dns-blacklist-entry=ix.dnsbl.manitu.net
> dns-blacklist-entry=zen.spamhaus.org
>
> reject-missing-sender-mx
> reject-empty-rdns
> reject-unresolvable-rdns
> reject-ip-in-cc-rdns
> r
Arne, maybe you can try to set
log-level=debug
an watch the mail-log for useful infos...
2014-03-18 10:02 GMT+01:00 Arne.Metzger :
> Ok, problem must be spamdyke. I removed spamdyke from smtp_psa and
> smtps_psa and auth works fine.
>
> So, where is my misconfiguration?
>
> Am 18.03.2014 08:25,
Just for the records:
With Version 5.0.0 and the new option "tls-dhparams-file" everything works
great, TLS uses the strong cipher suites now!
Thank you :-)
2013-09-10 Marc Gregel :
> Looking forward to the Update :-)
>
>
> 2013/9/10 Sam Clippinger
>
>> I thi
Haggy,
can you take a look to this error here:
https://www.mail-archive.com/spamdyke-users@spamdyke.org/msg03991.html
THX :-)
2014-02-03 Haggy :
> Thanks a lot Sam for you great, great work !!!
>
> Based on Sams work the MySQL Version of 5.0.0 has been released:
>
> http://haggybear.de/de/spamdy
same test from a different host
> (e.g. so it's not "localhost:25" but "mail.domain.com:25")?
>
> It works fine on my server on both port 25 (TLS) and port 465 (SSL), not
> that that helps. :)
>
> -- Sam Clippinger
>
>
>
>
> On Feb 3, 2014, a
I had the same problem...
tar -xzvf spamdyke-mysql.tgz
gzip: stdin: not in gzip format
As workaround I unzipped the whole stuff on my windows machine with 7zip,
then uploaded it again.
2014-02-04 Arne.Metzger :
> Hi,
>
> i get an error when i try to expand the tarfile from
>
> http://www.hagg
Hi there,
after upgrading from 4.3.1 to 5.0.0 I can't use TLS anymore:
(TLS-LEVEL=SMTP)
No idea where to start the debug, because when I switch back to 4.3.1
everything works fine again.
I tried the Version with MYSQL from @Haggy too - same problem, same error.
That's the output:
openssl s_clien
Im also running qmail with plesk and made a quick check:
excatyl the same settings like @Arne wrote above!
2013/10/21 Sam Clippinger
> I have some good news and some bad news...
>
> The good news: spamdyke version 5.0.0 is done, tested and ready. The
> biggest new feature is recipient validati
.
>
> Thanks for finding that link, I don't think I would have even looked at a
> function with "tmp" in its name!
>
> -- Sam Clippinger
>
>
>
>
> On Sep 9, 2013, at 3:34 AM, Marc Gregel wrote:
>
> Hi Sam,
>
> is it possible that the problem is
ubstitute your
> ciphers as appropriate):
> openssl s_client -quiet -cipher "EXP-RC4-MD5" -connect localhost:465
> If it connects and you see the "220" greeting banner, it's working. If
> you see an "alert handshake failure", you've probably selec
Hi :-)
These days where the NSA is watching us I decided to make my server as
secure as possible.
For qmail it means to use TLS with strong encryption - openssl with "-
ciphers "EDHS:DE" for example.
The original QMAIL without spamdyke works fine:
openssl s_client -starttls smtp -connect localhos
12 matches
Mail list logo