Quoting Sam Clippinger s...@silence.org:
Very nicely done, thanks for the patch! I'll get this added to the
codebase.
Please add a note in the sample spamdyke.conf that enabling this is
likely to result in your not being able to send/receive mail from some
legitimate mail servers (see my
I'd say the majority of people would only use it for authenticated
mail, as that's where you *really* want TLS/SSL.
For example we disable authentication,TLS/SSL on port 25 and relaying.
We leave TLS/SSL, authentication and relaying enabled on 465 and 587.
Sent from my iPad
On 16/07/2010, at
Quoting Chris Boulton chris.boul...@interspire.com:
I'd say the majority of people would only use it for authenticated
mail, as that's where you *really* want TLS/SSL.
For example we disable authentication,TLS/SSL on port 25 and relaying.
We leave TLS/SSL, authentication and relaying enabled
I imagine I'll add a large note that changing the cipher list is not
recommended unless you really, really know what you're doing AND you
have a good reason to do so.
-- Sam Clippinger
On 7/16/10 3:21 AM, t...@uncon.org wrote:
Quoting Sam Clippingers...@silence.org:
Very nicely done,
Quoting Chris Boulton ch...@bigcommerce.com:
We're rolling out spamdyke across our Qmail servers, and for PCI
compliance we need to ensure that no low/weak ciphers are being used
for TLS/SSL communication. I noticed spamdyke doesn't have a way to
configure the available ciphers, so I've built
Very nicely done, thanks for the patch! I'll get this added to the
codebase.
-- Sam Clippinger
On 7/14/10 1:32 AM, Chris Boulton wrote:
Hi,
We're rolling out spamdyke across our Qmail servers, and for PCI
compliance we need to ensure that no low/weak ciphers are being used
for TLS/SSL
Way to go Chris! Outstanding work. Thanks.
Faris.
-Original Message-
From: spamdyke-users-boun...@spamdyke.org [mailto:spamdyke-users-
boun...@spamdyke.org] On Behalf Of Chris Boulton
Sent: 14 July 2010 7:33 AM
To: spamdyke users
Subject: [spamdyke-users] [patch] Configurable TLS
