Hi Sam,
i wasn't able to resolve the issue, so i switched back to 4.3.1. I have
"smtp-auth-command" 1:1 in my spamdyke4.conf and it works, but i have
splitted it into 2 lines now.
Users mays authenticate with short or long username, so both versions
will work. Most use the short version.
I
I've considered doing this for a while now, if I can find a good balance
between helpful diagnostics and exposing too much information to the recipient.
My first impulse is to just find a way to output the spamdyke "ALLOWED" log
message into the message headers, since it contains pretty much ev
I'm really sorry I haven't been able to get to spamdyke issues lately, let me
see if I can catch up...
I'll update the docs, thanks for the tip!
As for how the key size of the DH key relates to well, anything at all, I
honestly have no idea. The OpenSSL documentation is extremely frustrating t
I'm really sorry I haven't been able to get to spamdyke issues lately, let me
see if I can catch up...
Is "*@domain.tld" being logged as the recipient in the spamdyke logs? Or are
you seeing that as the "To" line in the message header? If it's in the logs,
you should be able to just add "*@do
I'm really sorry I haven't been able to get to spamdyke issues lately, let me
see if I can catch up...
Did you ever get this issue resolved? The only thing that jumps out to me is
the way you've formatted your "smtp-auth-command" option -- you've got two
commands on a single line, which means
I'm really sorry I haven't been able to get to spamdyke issues lately, let me
see if I can catch up...
When I test the earlytalker filter by itself from the command line, it appears
to work:
root@patched:/usr/local/src/spamdyke-5.0.0/spamdyke# ./spamdyke --log-target
stderr -linfo -e 10 ../tes
