To avoid this problem I’ve created the following patch:
> --- spamdyke-5.0.0.orig/spamdyke/spamdyke.c
> +++ spamdyke-5.0.0/spamdyke/spamdyke.c
> @@ -2368,6 +2368,11 @@ void middleman(int *inbound_fd, int *out
> output_writeln(current_settings, LOG_ACTION_FILTER_FROM,
> STDOUT_
Sam,
I tripped over this bug but thought I didn't set things up properly.
You've been teasing us with the next release for a while. Thanks for
letting us know it's still on it's way.
Gary
On 02/03/2015 08:04 PM, Sam Clippinger via spamdyke-users wrote:
You're quite correct -- this is a bug
You're quite correct -- this is a bug in version 5.0.0. I've got it fixed in
the next version, hopefully to be released very soon.
-- Sam Clippinger
On Feb 2, 2015, at 1:38 PM, Heiko Bornholdt via spamdyke-users
wrote:
> Hi,
>
> I’m trying to replace my Spamdyke 4.3 with 5.0. I want to d
Hi,
I’m trying to replace my Spamdyke 4.3 with 5.0. I want to disable SSLv3 because
of POODLE.
I’m using Ubuntu 12.04 LTS and have Spamdyke compiled from source without any
special configuration.
> root@andromeda:~# spamdyke --version
> spamdyke 5.0.0+TLS+CONFIGTEST+DEBUG (C)2014 Sam Clippinge
