Re: [spamdyke-users] Problem in v3.1.1 make it un-usable.
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 leave the server just hang in qmail queue.
So I revert both spamdyke to 3.0.1. (position of spamdyke still before
relaylock)
Force qmail to send qmail queue. All email goes without any problem.
So pipe spamdyke before relaylock works. But spamdyke 3.1.1 still have problem
with mail send via webmail.
Through-out this test no configuration change for spamdyke.conf, whitelist,
blacklist all configure file is the same.
- Original Message
From: Sam Clippinger [EMAIL PROTECTED]
To: spamdyke users spamdyke-users@spamdyke.org
Sent: Thursday, November 15, 2007 2:09:29 AM
Subject: Re: [spamdyke-users] Problem in v3.1.1 make it un-usable.
I got a tip a while back from another Plesk user that you have to run
spamdyke before relaylock to avoid these errors. So in your
/etc/xinetd.d/smtp_psa file, try changing the server_args line to:
server_args = -Rt0 /usr/local/bin/spamdyke --config-file
/var/qmail/spamdyke/spamdyke.conf /var/qmail/bin/relaylock
/var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true
/var/qmail/bin/cmd5checkpw /var/qmail/bin/true
I need to update the documentation to include this.
-- Sam Clippinger
david boh wrote:
Sure my friend.
Both server has the same smtp_psa and configure ( both server have
3.0.1
and duplicate/mirror setting)
SMTP_PSA
{
socket_type = stream
protocol= tcp
wait= no
disable = no
user= root
instances = UNLIMITED
server = /var/qmail/bin/tcp-env
server_args = -Rt0 /var/qmail/bin/relaylock
/usr/local/bin/spamdyke --config-file
/var/qmail/spamdyke/spamdyke.conf
/var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth
/var/qmail/bin/true
/var/qmail/bin/cmd5checkpw /var/qmail/bin/true
}
SPAMDYKE.CONF
log-level=2
local-domains-file=/var/qmail/control/rcpthosts
max-recipients=30
idle-timeout-secs=300
graylist-dir=/var/qmail/spamdyke/graylist
graylist-min-secs=120
graylist-max-secs=1814400
#greeting-delay-secs = 1
sender-blacklist-file=/var/qmail/spamdyke/blacklist_senders
recipient-blacklist-file=/var/qmail/spamdyke/blacklist_recipients
# ip-in-rdns-keyword-file=/var/qmail/spamdyke/blacklist_keywords
ip-blacklist-file=/var/qmail/spamdyke/blacklist_ip
# rdns-blacklist-dir=/var/qmail/spamdyke/blacklist_rdns.d
sender-whitelist-file=/var/qmail/spamdyke/whitelist_recipients
# reject-empty-rdns
# reject-unresolvable-rdns
# reject-ip-in-cc-rdns
# rdns-whitelist-file=/var/qmail/spamdyke/whitelist_rdns
ip-whitelist-file=/var/qmail/spamdyke/whitelist_ip
reject-missing-sender-mx
check-dnsrbl=dul.dnsbl.sorbs.net
#check-dnsrbl=sbl.spamhaus.org
- Original Message
From: Sam Clippinger [EMAIL PROTECTED]
To: spamdyke users spamdyke-users@spamdyke.org
Sent: Wednesday, November 14, 2007 12:13:44 AM
Subject: Re: [spamdyke-users] Problem in v3.1.1 make it un-usable.
Can you send more information about your setup? Could you send the
contents of your /etc/xinetd.d/smtp_psa file and your spamdyke
configuration file (if you have one)?
-- Sam Clippinger
david boh wrote:
I would like to report that v3.1.0 also suffer from the same issue
as
described below.
So now I am back to v3.0.1, I think many mail will be missing if I
continue to test.
I believei it should be able to resolve quickly.
- Original Message
From: david boh [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
To: spamdyke-users@spamdyke.org
mailto:spamdyke-users@spamdyke.org
Sent: Tuesday, November 13, 2007 11:22:01 PM
Subject: [spamdyke-users] Problem in v3.1.1 make it un-usable.
I have two server. One I install the latest spamdyke v3.1.1, let's
call
this server A and the other server B.
Both have spamdyke v3.1.1, using plesk. But when I send email via
webmail from server A to the server B email, some how the email
cannot
be delivered.
When I check server B the log shows a lot of Broken pipe. How I
know as
all the email was trap in server A queue, so I force qmail to send
and
immediately check the server log in server B.
Nov 13 22:19:52 manna spamdyke[19583]: ERROR: unable to write 36
bytes
to file descriptor 1: Broken pipe
Nov 13 22:19:52 manna spamdyke[19585]: ERROR: unable to write 1542
bytes
to file descriptor 1: Broken pipe
Nov 13 22:19:52 manna spamdyke[19585]: ERROR: unable to write 36
bytes
to file descriptor 1: Broken pipe
Nov 13 22:19:52 manna spamdyke[19580]: ERROR: unable to write 1542
bytes
to file descriptor 1: Broken pipe
Nov 13 22:19:52 manna spamdyke[19580]: ERROR: unable to write
[spamdyke-users] Strange error
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 descriptor 1: Broken pipe slackware 12 + qmail i don't know what is causing this problem and what is meaning. Please help Thanks in advance ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
[spamdyke-users] option to not look up any dns information on connections?
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 a patch. :/ -- -- Cheers, Steve ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Problem in v3.1.1 make it un-usable.
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 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 leave the server just hang in qmail queue.
So I revert both spamdyke to 3.0.1. (position of spamdyke still before
relaylock)
Force qmail to send qmail queue. All email goes without any problem.
So pipe spamdyke before relaylock works. But spamdyke 3.1.1 still have
problem with mail send via webmail.
Through-out this test no configuration change for spamdyke.conf,
whitelist, blacklist all configure file is the same.
- Original Message
From: Sam Clippinger [EMAIL PROTECTED]
To: spamdyke users spamdyke-users@spamdyke.org
Sent: Thursday, November 15, 2007 2:09:29 AM
Subject: Re: [spamdyke-users] Problem in v3.1.1 make it un-usable.
I got a tip a while back from another Plesk user that you have to run
spamdyke before relaylock to avoid these errors. So in your
/etc/xinetd.d/smtp_psa file, try changing the server_args line to:
server_args= -Rt0 /usr/local/bin/spamdyke --config-file
/var/qmail/spamdyke/spamdyke.conf /var/qmail/bin/relaylock
/var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true
/var/qmail/bin/cmd5checkpw /var/qmail/bin/true
I need to update the documentation to include this.
-- Sam Clippinger
david boh wrote:
Sure my friend.
Both server has the same smtp_psa and configure ( both server have 3.0.1
and duplicate/mirror setting)
SMTP_PSA
{
socket_type= stream
protocol= tcp
wait= no
disable= no
user= root
instances = UNLIMITED
server = /var/qmail/bin/tcp-env
server_args= -Rt0 /var/qmail/bin/relaylock
/usr/local/bin/spamdyke --config-file /var/qmail/spamdyke/spamdyke.conf
/var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true
/var/qmail/bin/cmd5checkpw /var/qmail/bin/true
}
SPAMDYKE.CONF
log-level=2
local-domains-file=/var/qmail/control/rcpthosts
max-recipients=30
idle-timeout-secs=300
graylist-dir=/var/qmail/spamdyke/graylist
graylist-min-secs=120
graylist-max-secs=1814400
#greeting-delay-secs = 1
sender-blacklist-file=/var/qmail/spamdyke/blacklist_senders
recipient-blacklist-file=/var/qmail/spamdyke/blacklist_recipients
# ip-in-rdns-keyword-file=/var/qmail/spamdyke/blacklist_keywords
ip-blacklist-file=/var/qmail/spamdyke/blacklist_ip
# rdns-blacklist-dir=/var/qmail/spamdyke/blacklist_rdns.d
sender-whitelist-file=/var/qmail/spamdyke/whitelist_recipients
# reject-empty-rdns
# reject-unresolvable-rdns
# reject-ip-in-cc-rdns
# rdns-whitelist-file=/var/qmail/spamdyke/whitelist_rdns
ip-whitelist-file=/var/qmail/spamdyke/whitelist_ip
reject-missing-sender-mx
check-dnsrbl=dul.dnsbl.sorbs.net
#check-dnsrbl=sbl.spamhaus.org
- Original Message
From: Sam Clippinger [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
To: spamdyke users spamdyke-users@spamdyke.org
mailto:spamdyke-users@spamdyke.org
Sent: Wednesday, November 14, 2007 12:13:44 AM
Subject: Re: [spamdyke-users] Problem in v3.1.1 make it un-usable.
Can you send more information about your setup? Could you send the
contents of your /etc/xinetd.d/smtp_psa file and your spamdyke
configuration file (if you have one)?
-- Sam Clippinger
david boh wrote:
I would like to report that v3.1.0 also suffer from the same issue as
described below.
So now I am back to v3.0.1, I think many mail will be missing if I
continue to test.
I believei it should be able to resolve quickly.
- Original Message
From: david boh [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
To: spamdyke-users@spamdyke.org
mailto:spamdyke-users@spamdyke.org mailto:spamdyke-users@spamdyke.org
mailto:spamdyke-users@spamdyke.org
Sent: Tuesday, November 13, 2007 11:22:01 PM
Subject: [spamdyke-users] Problem in v3.1.1 make it un-usable.
I have two server. One I install the latest spamdyke v3.1.1, let's
call
this server A and the other server B.
Both have spamdyke v3.1.1, using plesk. But when I send email via
webmail from server A to the server B email, some how the email cannot
be delivered.
When I check server B the log shows a lot of Broken pipe. How I
know as
all the email was trap in server A
Re: [spamdyke-users] option to not look up any dns information on connections?
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 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 a patch. :/ ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Strange error
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 down your log-level to 2 or less. -- Sam Clippinger George Zica wrote: 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 descriptor 1: Broken pipe slackware 12 + qmail i don't know what is causing this problem and what is meaning. Please help Thanks in advance ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Problem in v3.1.1 make it un-usable.
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 with admin credentials via: Server
- Mail - tab White List
Ton
david boh schreef:
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 leave the server just hang in qmail queue.
So I revert both spamdyke to 3.0.1. (position of spamdyke still before
relaylock)
Force qmail to send qmail queue. All email goes without any problem.
So pipe spamdyke before relaylock works. But spamdyke 3.1.1 still have
problem with mail send via webmail.
Through-out this test no configuration change for spamdyke.conf,
whitelist, blacklist all configure file is the same.
-
Original Message
From: Sam Clippinger [EMAIL PROTECTED]
To: spamdyke users spamdyke-users@spamdyke.org
Sent: Thursday, November 15, 2007 2:09:29 AM
Subject: Re: [spamdyke-users] Problem in v3.1.1 make it un-usable.
I got a tip a while back from another Plesk user that you have to run
spamdyke before relaylock to avoid these errors. So in your
/etc/xinetd.d/smtp_psa file, try changing the "server_args" line to:
server_args = -Rt0 /usr/local/bin/spamdyke --config-file
/var/qmail/spamdyke/spamdyke.conf /var/qmail/bin/relaylock
/var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true
/var/qmail/bin/cmd5checkpw /var/qmail/bin/true
I need to update the documentation to include this.
-- Sam Clippinger
david boh wrote:
Sure my friend.
Both server has the same smtp_psa and configure ( both server have
3.0.1
and duplicate/mirror setting)
SMTP_PSA
{
socket_type = stream
protocol = tcp
wait = no
disable = no
user = root
instances = UNLIMITED
server = /var/qmail/bin/tcp-env
server_args = -Rt0 /var/qmail/bin/relaylock
/usr/local/bin/spamdyke --config-file
/var/qmail/spamdyke/spamdyke.conf
/var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth
/var/qmail/bin/true
/var/qmail/bin/cmd5checkpw /var/qmail/bin/true
}
SPAMDYKE.CONF
log-level=2
local-domains-file=/var/qmail/control/rcpthosts
max-recipients=30
idle-timeout-secs=300
graylist-dir=/var/qmail/spamdyke/graylist
graylist-min-secs=120
graylist-max-secs=1814400
#greeting-delay-secs = 1
sender-blacklist-file=/var/qmail/spamdyke/blacklist_senders
recipient-blacklist-file=/var/qmail/spamdyke/blacklist_recipients
# ip-in-rdns-keyword-file=/var/qmail/spamdyke/blacklist_keywords
ip-blacklist-file=/var/qmail/spamdyke/blacklist_ip
# rdns-blacklist-dir=/var/qmail/spamdyke/blacklist_rdns.d
sender-whitelist-file=/var/qmail/spamdyke/whitelist_recipients
# reject-empty-rdns
# reject-unresolvable-rdns
# reject-ip-in-cc-rdns
# rdns-whitelist-file=/var/qmail/spamdyke/whitelist_rdns
ip-whitelist-file=/var/qmail/spamdyke/whitelist_ip
reject-missing-sender-mx
check-dnsrbl=dul.dnsbl.sorbs.net
#check-dnsrbl=sbl.spamhaus.org
- Original Message
From: Sam Clippinger [EMAIL PROTECTED]
To: spamdyke users spamdyke-users@spamdyke.org
Sent: Wednesday, November 14, 2007 12:13:44 AM
Subject: Re: [spamdyke-users] Problem in v3.1.1 make it un-usable.
Can you send more information about your setup? Could you send the
contents of your /etc/xinetd.d/smtp_psa file and your spamdyke
configuration file (if you have one)?
-- Sam Clippinger
david boh wrote:
I would like to report that v3.1.0 also suffer from the same
issue as
described below.
So now I am back to v3.0.1, I think many mail will be
missing if I
continue to test.
I believei it should be able to resolve quickly.
- Original Message
From: david boh [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
To: spamdyke-users@spamdyke.org
mailto:spamdyke-users@spamdyke.org
Sent: Tuesday, November 13, 2007 11:22:01 PM
Subject: [spamdyke-users] Problem in v3.1.1 make it
un-usable.
I have two server. One I install the latest spamdyke v3.1.1,
let's call
this server A and the other server B.
Both have spamdyke v3.1.1, using plesk. But when I send
email via
webmail from server A to the server B email, some how the
email cannot
be delivered.
When I check server B the log shows a lot of Broken pipe.
How I know as
all the email was trap in server A queue, so I force qmail
to send and
immediately check the server log in server B.
Nov 13 22:19:52 manna spamdyke[19583]: ERROR: unable to
write 36 bytes
to file descriptor 1: Broken pipe
Nov 13
