nicole thomson wrote:
I'll believe it when I see it. Will you post a log message showing
DENIED_RBLMATCH with this address? Perhaps that would shed some light on
your trouble.

# qmlog -lc 165.21.21.188 smtp
should find where this happened in your log.

smtp]# grep "DENIED" * |grep 165.21.21.188
@400000004b14ebc31b052aec.s:@400000004b1370d9356f6ba4 spamdyke[21904]: DENIED_RBL_MATCH from: [email protected] to: [email protected] origin_ip: 165.21.21.188 origin_rdns: lisa.clientdomain.com auth: (unknown)

 165.21.21.188 is not listed in the XBL

Unfortunately, spamdyke doesn't yet show *which* RBL it hit on (an upgrade for this is in the works). Did you check to see if it's listed at bl.spamcop.net? If it's not listed in either place (spamhaus or spamcop), then my conclusion is that it's been delisted since this log message was generated. (FWIW, qmlog will show a more meaningful time stamp)


if it is blocking valid spam mails I will be the happiest in world, but vendors keep complaining that their mails are bouncing back with spamhaus url, when I grep their domain and check their ip in spamhaus spamhaus.org/zen/index.lasso <http://spamhaus.org/zen/index.lasso> , it shows this ip is not listed.

now at current scenario with your help I want to achieve the incoming good mails has to reach us without any issues, and bad mails have tobe blocked

here I followed your instructions, now the results from dig is pretty neat.

rpm -e djbdns-localcache-1.05-1.0.5

# yum install caching-nameserver bind-chroot

and that's it. There should be nothing more to do.

(1/5): bind-chroot-9.3.6- 100% |=========================|  44 kB    00:01

(2/5): bind-9.3.6-4.P1.el 100% |=========================| 978 kB    00:07

(3/5): bind-utils-9.3.6-4 100% |=========================| 170 kB    00:02

(4/5): bind-libs-9.3.6-4. 100% |=========================| 857 kB    00:08

(5/5): caching-nameserver 100% |=========================|  60 kB    00:01

Running rpm_check_debug

Running Transaction Test

Finished Transaction Test

Transaction Test Succeeded

Running Transaction

  Updating  : bind-libs                    ######################### [1/7]

  Installing: bind                         ######################### [2/7]

  Installing: caching-nameserver           ######################### [3/7]

  Updating  : bind-utils                   ######################### [4/7]

  Installing: bind-chroot                  ######################### [5/7]

  Cleanup   : bind-libs                    ######################### [6/7]

  Cleanup   : bind-utils                   ######################### [7/7]

Installed: bind-chroot.i386 30:9.3.6-4.P1.el5 caching-nameserver.i386 30:9.3.6-4.P1.el5

Dependency Installed: bind.i386 30:9.3.6-4.P1.el5

Updated: bind-libs.i386 30:9.3.6-4.P1.el5

Dependency Updated: bind-utils.i386 30:9.3.6-4.P1.el5

Complete!

/etc/init.d/named restart

 /etc/init.d/named status

number of zones: 6

debug level: 0

xfers running: 0

xfers deferred: 0

soa queries in progress: 0

query logging is OFF

recursive clients: 0/1000

tcp clients: 0/100

server is up and running

named (pid  382) is running...

vow

dig @127.0.0.1 google.com

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5 <<>> @127.0.0.1 google.com

; (1 server found)

;; global options:  printcmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58901

;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 0

;; QUESTION SECTION:

;google.com.                    IN      A

;; ANSWER SECTION:

google.com.             300     IN      A       74.125.45.100

google.com.             300     IN      A       74.125.53.100

google.com.             300     IN      A       74.125.67.100

;; AUTHORITY SECTION:

google.com.             172800  IN      NS      ns2.google.com.

google.com.             172800  IN      NS      ns3.google.com.

google.com.             172800  IN      NS      ns4.google.com.

google.com.             172800  IN      NS      ns1.google.com.

;; Query time: 726 msec

;; SERVER: 127.0.0.1#53(127.0.0.1)

;; WHEN: Thu Dec  3 11:26:58 2009

;; MSG SIZE  rcvd: 148


--Nic


That looks good. You should change your /etc/resolv.conf file now so that
nameserver 127.0.0.1
is the first nameserver listed, if it's not already.

So at this point, I think you're ready to install spamdyke again. Please run qtp-install-spamdyke (you've installed the current qmailtoaster-plus package, right?) and we'll go from there.

Please start a new thread/message with your next email. This one has gotten pretty big.

--
-Eric 'shubes'


---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
     If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
    Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
    For additional commands, e-mail: [email protected]


Reply via email to