This looks like a DNS problem to me. If the spamdyke server can't
find the MX record quickly enough, it will reject the message. By the
time the remote server retries delivery, the MX record is cached by
the spamdyke server's local DNS server and the message is allowed.
spamdyke's DNS-based filters send temporary rejection codes (so the
remote server will retry) for exactly this reason.
Another possibility is that your primary and secondary DNS servers are
out of sync and returning different results. In that case, spamdyke
could be getting different responses each time it's filters run.
If you compile spamdyke with "excessive output" and activate full
logging, the log files will show which DNS servers are being queried
and what responses are received.
On Dec 31, 2008, at 8:59 PM, "Eric C. Broch" <[email protected]>
wrote:
Eric S,
Thanks. Here's the info:
The DNS MX for domain1 has been active for 1.5 years!
For domain0 1.5 days.
Spamdyke version install with QTP:
spamdyke 4.0.9+TLS+CONFIGTEST+DEBUG (C)2008 Sam Clippinger, samc (at)
silence (dot) org
Below is a copy of my spamdyke.conf:
#dns-blacklist-entry=zombie.dnsbl.sorbs.net
#dns-blacklist-entry=dul.dnsbl.sorbs.net
#dns-blacklist-entry=bogons.cymru.com
dns-blacklist-entry=zen.spamhaus.org
dns-blacklist-entry=bl.spamcop.net
graylist-dir=/var/spamdyke/graylist
graylist-level=always
graylist-max-secs=2678400
graylist-min-secs=180
greeting-delay-secs=1
idle-timeout-secs=60
ip-blacklist-file=/etc/spamdyke/blacklist_ip
ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
ip-whitelist-file=/etc/spamdyke/whitelist_ip
local-domains-file=/var/qmail/control/rcpthosts
log-level=debug
log-target=stderr
max-recipients=50
#policy-url=http://my.policy.explanation.url/
rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
recipient-whitelist-file=/etc/spamdyke/whitelist_recipients
reject-empty-rdns
#reject-ip-in-cc-rdns
reject-missing-sender-mx
reject-unresolvable-rdns
sender-blacklist-file=/etc/spamdyke/blacklist_senders
sender-whitelist-file=/etc/spamdyke/whitelist_senders
tls-certificate-file=/var/qmail/control/servercert.pem
This is MX dig on domain0.com qmailtoaster of domain1.com
Domain0.com is the one that yields MX errors in the smtp log for
domain1.com:
[domain0]# dig mx domain1.com
; <<>> DiG 9.3.4-P1 <<>> mx domain1.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35358
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
; domain1.com. IN MX
;; ANSWER SECTION:
domain1.com. 3600 IN MX 0 xx.xxx.xx.xxx.
;; AUTHORITY SECTION:
domain1.com. 3536 IN NS ns55.domaincontrol.com.
domain1.com. 3536 IN NS ns56.domaincontrol.com.
;; Query time: 75 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Dec 31 19:37:02 2008
;; MSG SIZE rcvd: 115
Another question: What is the format, if any, for wildcards in the
spamdyke
'whitelist_sender' file?
I want to specify a whole domain. I don't see an answer on spamdyke
help
I tried these:
domain1.com
*[email protected]
Eric C. Broch
White Horse Technical Consulting
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
