Re: [spamdyke-users] denied rdns filter messages

Thanks Sam >You're right about the first one (164.177.131.207) -- the rDNS name exists, so >the "reject-empty-rdns" filter doesn't stop it. But the rDNS name doesn't >have an A record, so the "reject-unresolvable-rdns" filter blocks it. Unless >I'm missing something, this is how those filters

[spamdyke-users] The order of things

Morning Sam What order do the filters run in? your set order? or do they get processed in the order they are in the config file? The reason I ask is that I would like to to process the blacklists first before the rbl's as it will save some time. Regards Lawrence ___

Re: [spamdyke-users] No TLS with openssl "elliptic curve" cipher suites / pfs "perfect forward secrecy"

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 think you're exactly right -- I'll need

Re: [spamdyke-users] The order of things

That's a tricky issue. The short answer is the list given here: http://spamdyke.org/documentation/FAQ.html#FEATURE1 The longer answer is that spamdyke will continue running as long as it needs to, in order to determine that no whitelists are going to be matched. For example, if you use