[IMGate] Re: MXrate?

2006-10-23 Thread Keith Kikta
Are you somehow setting the 127.0.0.3 response to allow instead of reject?

Keith J. Kikta
K2 Colocation
www.k2colocation.com
 
Office: 800.672.4655
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Len Conrad
Sent: Saturday, October 21, 2006 2:49 PM
To: IMGate@mgw2.MEIway.com
Subject: [IMGate] Re: MXrate?


I have been running in warn mode for quite a while and
the results are impressive.

We're evaluating the public mxrate DNS, running the mxrate RBL after:

1)bad recips

2)postgrey and

3) blocked using sbl-xbl.spamhaus.org (total: 49358)
 1768   red-gum.com
 1744   hoazin.com
 1573   rr.com
 1391   verizon.net
 1245   comcast.net



We then follow the above with mxrate in WARN mode would give these 
additional rejects:

   blocked using pub.mxrate.net=127.0.0.2 (total: 21973)
  254   pennirahrnix.com
  216   iexons.com
  203   brizor.com
  197   fixwho.com
  187   lifemetropolis.com
  185   zigpic.com
  181   magaretcelynix.com
  171   luisetarboxnetworks.com
  169   igazes.com
  164   leaderofthereeworldisbush.com
  164   patelate.com

and

blocked using pub.mxrate.net=127.0.0.4 (total: 12660)
  365   lortexmal.com
  209   igazes.com
  198   tshx.coolsavingz.info
  185   beanbe.com
  163   web-uplink.com
  153   vm-mail.com

The above are numbers up to 15:00 hour.

We are inspecting the mxrate 4tuples for legits, but it looks pretty good.

Len






[IMGate] Re: MXrate?

2006-10-19 Thread John Beaver
Len Conrad wrote:
 anybody using this with IMGate?
 
 http://www.mxrate.com/lookup/dns.htm
 

I've used them for about a year with good results.
My volume is ~3000 emails per day.
Weekly stat for last week:
 blocked using combined.njabl.org (total: 268)
 blocked using sbl-xbl.spamhaus.org (total: 857)
 blocked using sub.mxrate.net=127.0.0.2 (total: 632)
 blocked using sub.mxrate.net=127.0.0.4 (total: 32)

They are listed in this order in the restrictions.

I ran in warn mode for about 1 month and only caught SPAM emails.
It does fail lookups occasionally, not sure if the DNS problems are on 
my end or theirs, or somewhere in between.  Not enough to warrant 
removal, but thought I'd mention it.

john