Hi David,
Just a quick note from a fellow Plesk-user.
I'm using spamdyke as well on several Plesk (Linux) versions and no
complaints and no problems using webmail.
I'm just wondering whether you've got localhost (127.0.0.1) on your
whitelist inside Plesk?
Settings can be found by logging in
It means spamdyke is attempting to write data to the remote server but
the remote server has already disconnected, probably when it received a
rejection message.
Don't worry about it, this message is just informational. With spamdyke
version 3.1.0 or later, you can hide this message by turning
This is very strange. When the messages remain in the queue, are you
seeing any errors in the qmail logs? Can you enable spamdyke's full
logging on the receiving server and send me a log of a failed delivery?
-- Sam Clippinger
david boh wrote:
> Hi Sam,
>
> Test Step:
> 1. Re-install spamdyk
Yes. I'm already planning to make the DNS behavior completely
configurable in the next version, so this would be an easy thing to add.
I'll put it on the list.
-- Sam Clippinger
Steve Cole wrote:
> For those of us not using any of the DNS/reverse DNS features of spamdyke, is
> it possible to
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 suppl
Hello ,
I have spamdyke installed on a server with a huge number of spamsĀ per
day . Since I've installed spamdyke (96 hours) i have a number of 16859
emails blocked ( until now, when i'm writing) . The problem i have is
this one:
spamdyke[2731]: ERROR: unable to write 27 bytes to file desc
Hi Sam,
Test Step:
1. Re-install spamdyke 3.1.1 in both server
2. Place the spamdyke before relaylock pipe in xinetd.d
3. Restart xinetd
4. Repeat 2 and 3 of the other server.
5. Did the test, using webmail and send from server A to server B. Did the same
on the other end.
Both email did not le