I had nothing in my access file.
It appears to work in this case when :allow is in the access-file. The
documentation isn't too clear on this, although I would *SWEAR* that I
tried this beforehand. Perhaps I was adding -x to the tcpserver command,
I know I did throw that in for kicks at one
qsheff hasn't been updated in about a year, and the last released version will
kill your mail server (literally) with e-mail eating bugs. if someone was
willing to take this under their wing and maybe just rip out the
functionality other than anti-virus, that would be cool ;)
in all
On Tuesday 30 October 2007, Sam Clippinger wrote:
I'm not familiar with qsheff, so I hadn't given any thought to trying to
replace it. Personally, I use qmail-scanner
(qmail-scanner.sourceforge.net).
Yes, but the issue we have with qmail-scanner is that our e-mail system moves
around 1.2M
I need to offer SMTP-Auth on one server which was previously using
POP-before-SMTP and the issue I am running into is this: I'd like to give
them 90 days to get themselves moved over to SMTP-Auth, while continuing to
use the existing configuration. I am handling the RELAYCLIENT additions in
For those of us not using any of the DNS/reverse DNS features of spamdyke, is
it possible to add a bypass all DNS checks feature? This would be useful
for those of us using spamdyke only for AUTH/TLS capabilities and an IP
address accept/deny list.
I wish I had the programming skill to supply
From the config:
configure: error: Unable to compile without struct option for getopt_long()
See `config.log' for more details.
gcc:
gcc version 4.6.1 (Debian 4.6.1-4)
ld:
GNU ld (GNU Binutils for Debian) 2.21.52.20110606
c-lib:
libc62.13-10
Still an issue on Debian Stable Wheezy:
Straight-up ./configure used
-- cut
checking whether anonymous inner functions are supported by default... yes
checking whether struct option is defined in getopt.h... no
checking whether struct option is defined in unistd.h... no
configure: error:
On 14-03-07 03:53 PM, Sam Clippinger wrote:
What OS are you on? Does this happen every time, or just for some
connections? If you can
It appears to happen every time. I'm using Debian Linux x86_64.
Spamdyke 4.3.1 continues to work fine.
(./configure --with-excessive-output) and run it with
