[milters] Archive

Lists Index Date Thread Search

Article: 766
From: Anthony Howe
Date: 2010-06-25 05:06:48 -0400
Subject: More about BarricadeMX (was Re: Comments on this backscatterer.org?

On 11/06/2010 17:30, Grant Taylor whispered from the shadows...:
> On 06/08/10 02:56, Anthony Howe wrote:
>> It was a hard choice to make. milter-sender was my first milter and
>> one of the best implementations of call-back IMO. But after seven
>> years, it was getting a little long in the tooth. BarricadeMX came
>> along as my flag ship product, a comprehensive SMTP proxy filter that
>> is a fusion of all the milters, plus many more tests.
> 
> For me this is a disappointing turn of events.  I understand why you did
> what you did, but that does not mean that I like it.  :-(
> 
>> milter-sender comprises of three techniques: call-back, call-ahead,
>> and grey-listing. Trying to keep it up to date with respect to
>> BarricadeMX advances, which does all that and more, involves lots of
>> work.
> 
> milter-sender worked exceptionally well as a piece of a larger solution
>  that I rolled my self.  I will have to investigate BarricadeMX to see
> if      it can suffice, or if I will have find an alternative gray list
> / call  back filtering option.

BarricadeMX is a great solution, but more expensive and typically out of
the budget of small sites and hobbyists. The people at
http://www.fsl.com/ handle sales. 30 day
demo license are available.

> Nothing against a comprehensive product, it is just that it does not
> match my current environment (as is currently configured).

Documentation http://www.snertsoft.com/smtp/smtpf/

With BarricadeMX, you'd probably replace you anti-spam configuration
completely with BarricadeMX. It hooks into SpamAssassin and support four
different anti-virus products currently.

> I understand and agree that this is (partially) a political decision.
> However, in making said decision, you also made the decision for your
> milter-sender users.  So the impact was fairly sizable.

Existing users can continue to use the software. However, the software
won't be updated with the latest bells & whistles found in BarricadeMX
such as the Grey Listing Optimisations (GLO), Multicast/Unicast Cache
API (shared cache), the Parallel Domain Query (PDQ) API (better DNS
handling), grey-content option, etc.

Much of these changes will eventually go into milter-gris, but
maintaining a 3rd title with grey-listing features, just becomes too
much duplication.

> I don't think I missed an email to the mailing list (but I may have)
> discussing milter-sender's lack of continuing development.  Had I seen a
>  discussion, I would have definitely chimed in (like now).

There was no discussion about it. The slow down in development was only
natural given the limited resources and focus on BarricadeMX in
partnership with Fort Systems Ltd.

>> Essentially it boils down to a low ROI for milter-sender vs. a more
>> comprehensive product like BarricadeMX.
> 
> Unfortunately it's that "more comprehensive(ness)" that make make it
> such that BarricadeMX is not a suitable replacement for milter-sender.

I'd beg to differ functionality wise it is a great replacement. Cost
wise, it might be too expensive, though several clients have actually
saved money by replacing Barracuda or Symantec boxes with BarricadeMX;
one client found that after installing BarricadeMX, they reduced their
machine load and thus they could reduce their MX cluster from five to
three machines.

> If all I want in a pocket knife is a knife blade (or two) and all I have
>  room for is such, then a larger more comprehensive Swiss Army Knife
> with  many more options may not fit.  :-(

At the end of this message I've included raw BarricadeMX stats from my
own server.

> Would it be possible to set up a test sub-domain that has MX records
> pointing to an install of BarricadeMX and make the administration
> interface publicly available?
> 
> To prevent others from using it illicitly, MX to a relay, have said
> relay pass the (sub)domain on to BarricadeMX, have BarricadeMX do what
> it does.
> 
> Or, could you provide access to the BarricadeMX administration interface
>  (with out access to the SMTP path) so that we can see the glory that is
> BarricadeMX?  ;-)

I'll see what can be done. I do know that FSL will sometimes do a
conference call and demo for a prospective client. Maybe a group demo
might be possible. I'll discuss this with FSL. Maybe we can make a demo
and explanation video for download.


---- ps snapshot ----

VSZ 5508  RSS 6688  smtpf: th=10 cn=3 cs=2 (smtpf)

th: worker threads available,
cn: active connections
cs: connections / second


---- smtpf supported commands ----

Note that admin. commands can only be issued from the localhost for
security reasons.

help
214-2.0.0 ESMTP RFC 1985, 2821, 4954 supported commands:
214-2.0.0     AUTH    DATA    EHLO    ETRN    HELO    HELP
214-2.0.0     NOOP    MAIL    RCPT    RSET    QUIT
214-2.0.0
214-2.0.0 ESMTP RFC 2821 not implemented:
214-2.0.0     EXPN    TURN    VRFY
214-2.0.0
214-2.0.0 Administration commands:
214-2.0.0     CONN    CACHE   INFO    KILL    LKEY    OPTN
214-2.0.0     STAT    VERB    XCLIENT
214-2.0.0
214 2.0.0 End

---- smtpf logging ----

Assorted logging flags can be turned on/off without having to restart
the process. This is very handy if you need to diagnose a delivery
problem related to a particular set of tests.

verb
214-2.0.0 -access +attachment -auth -avastd -cache +clamd +connect
214-2.0.0 +ctasd -data -db -debug -digest -dns -dupmsg +emew -fpscand +grey
214-2.0.0 -headers -helo +info -kvm -mail -mutex -noop -p0f -rate -rbl
214-2.0.0 -rcpt -reply -rset -sav -savdid +save -siq -size +smtp
214-2.0.0 -smtp-data -smtp-dot -socket-fd +spamd -spf -stats +subject
214-2.0.0 -timelimitrcpt -timers -trace -uri +warn
214 2.0.0 End.

---- smtpf raw stats ----

1st field overall runtime count & percentage
2nd field current hour count & percentage
3rd field last 60m count & percentage

Lines with all capital title denotes the section; percentages are
computed against the section title counts.

These stats are used by the web interface to provide server performance
graphs. There are also per-route (domain or address) stats that track
reject, accept, and data volume that are also graphed by the web interface.

The numbers vary depending on which tests you enable and which
blacklists you use. By disabling IP blacklists, you see more hits on
later test thus BMX has internally layered defense.

stat
214-2.0.0 smtpf/2.3.20
214-2.0.0 start-time=Wed, 16 Jun 2010 12:12:06 +0200
214-2.0.0 age=772831 (08 22:40:31)
214-2.0.0 active-connections=6
214-2.0.0 sqlite-memory=1MB
214-2.0.0 sqlite-high-memory=6MB
214-2.0.0 000 route-accounts=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 001 route-addresses=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 002 route-domains=21 100.00%; 0 0.00%; 0 0.00%
214-2.0.0 003 route-unique-domains=21 100.00%; 0 0.00%; 0 0.00%
214-2.0.0 004 high-load-avg-1=22328 100.00%; 321 100.00%; 400 100.00%
214-2.0.0 005 high-load-avg-5=9515 100.00%; 294 100.00%; 294 100.00%
214-2.0.0 006 high-load-avg-15=4001 100.00%; 228 100.00%; 228 100.00%
214-2.0.0 007 load-avg-1=183 100.00%; 183 100.00%; 0 0.00%
214-2.0.0 008 load-avg-5=199 100.00%; 199 100.00%; 0 0.00%
214-2.0.0 009 load-avg-15=191 100.00%; 191 100.00%; 0 0.00%
214-2.0.0 010 high-connections=52 100.00%; 17 100.00%; 9 100.00%
214-2.0.0 011 high-connections-per-second=20 100.00%; 3 100.00%; 3 100.00%
214-2.0.0 012 high-connections-per-minute=396 100.00%; 36 100.00%; 23
100.00%
214-2.0.0 013 high-session-time=4261 100.00%; 191 100.00%; 191 100.00%
214-2.0.0 014 connections-per-minute=22 100.00%; 22 100.00%; 0 0.00%
214-2.0.0 015 total-KB=1270859 100.00%; 5133 100.00%; 6134 100.00%
214-2.0.0 016 open-files=27 100.00%; 27 100.00%; 0 0.00%
214-2.0.0 017 high-open-files=95 100.00%; 39 100.00%; 29 100.00%
214-2.0.0 018 grey-temp-expire=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 019 CLIENTS=197366 100.00%; 778 100.00%; 942 100.00%
214-2.0.0 020 dropped=170423 86.35%; 650 83.55%; 782 83.01%
214-2.0.0 021 clean-quit=26937 13.65%; 123 15.81%; 159 16.88%
214-2.0.0 022 client-io-error=18262 9.25%; 72 9.25%; 85 9.02%
214-2.0.0 023 client-timeout=2799 1.42%; 5 0.64%; 8 0.85%
214-2.0.0 024 client-is-2nd-mx=2076 1.05%; 9 1.16%; 11 1.17%
214-2.0.0 025 client-pipelining-seen=614 0.31%; 12 1.54%; 12 1.27%
214-2.0.0 026 server-io-error=471 0.24%; 1 0.13%; 2 0.21%
214-2.0.0 027 admin-commands=3 0.00%; 1 0.13%; 1 0.11%
214-2.0.0 028 auth-pass=4 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 029 auth-fail=11 0.01%; 0 0.00%; 0 0.00%
214-2.0.0 030 ehlo-no-helo=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 031 helo-schizophrenic=56 0.03%; 1 0.13%; 1 0.11%
214-2.0.0 032 rfc2821-command-length=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 033 smtp-command-non-ascii=246 0.12%; 1 0.13%; 1 0.11%
214-2.0.0 034 smtp-drop-after=151 0.08%; 1 0.13%; 2 0.21%
214-2.0.0 035 smtp-drop-unknown=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 036 quit-after-ehlo=9089 4.61%; 11 1.41%; 20 2.12%
214-2.0.0 037 quit-after-helo=12530 6.35%; 90 11.57%; 112 11.89%
214-2.0.0 038 connect-bl=35 0.02%; 0 0.00%; 0 0.00%
214-2.0.0 039 connect-gl=194 0.10%; 0 0.00%; 0 0.00%
214-2.0.0 040 connect-wl=179 0.09%; 1 0.13%; 1 0.11%
214-2.0.0 041 helo-bl=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 042 helo-gl=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 043 helo-wl=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 044 concurrent=255 0.13%; 0 0.00%; 0 0.00%
214-2.0.0 045 dns-bl=108954 55.20%; 431 55.40%; 517 54.88%
214-2.0.0 046 dns-gl=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 047 dns-wl=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 048 idle-retest-timer=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 049 bogus-helo=44 0.02%; 0 0.00%; 0 0.00%
214-2.0.0 050 client-ip-in-ptr=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 051 client-ptr-required=58517 29.65%; 262 33.68%; 307 32.59%
214-2.0.0 052 client-ptr-required-error=11389 5.77%; 45 5.78%; 52 5.52%
214-2.0.0 053 helo-claims-us=5 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 054 helo-ip-mismatch=5535 2.80%; 11 1.41%; 17 1.80%
214-2.0.0 055 helo-is-ptr=1074 0.54%; 6 0.77%; 6 0.64%
214-2.0.0 056 rfc2821-strict-helo=27064 13.71%; 182 23.39%; 209 22.19%
214-2.0.0 057 smtp-reject-delay=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 058 rate-client=9276 4.70%; 0 0.00%; 0 0.00%
214-2.0.0 059 rate-throttle=7 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 060 ns-bl-ptr=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 061 uri-bl-helo=1306 0.66%; 2 0.26%; 2 0.21%
214-2.0.0 062 uri-bl-ptr=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 063 MAIL=174595 100.00%; 730 100.00%; 890 100.00%
214-2.0.0 064 mail-drop=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 065 mail-parse=13 0.01%; 0 0.00%; 0 0.00%
214-2.0.0 066 mail-reject=116 0.07%; 0 0.00%; 0 0.00%
214-2.0.0 067 mail-tempfail=1648 0.94%; 4 0.55%; 9 1.01%
214-2.0.0 068 null-sender=15019 8.60%; 95 13.01%; 116 13.03%
214-2.0.0 069 connect-mail-bl=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 070 connect-mail-wl=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 071 mail-bl=116 0.07%; 0 0.00%; 0 0.00%
214-2.0.0 072 mail-wl=4769 2.73%; 1 0.14%; 2 0.22%
214-2.0.0 073 click-accept=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 074 mail-strict-fail=358 0.21%; 2 0.27%; 2 0.22%
214-2.0.0 075 client-is-mx=12958 7.42%; 44 6.03%; 53 5.96%
214-2.0.0 076 helo-mail-params=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 077 mail-require-mx=901 0.52%; 6 0.82%; 7 0.79%
214-2.0.0 078 mail-require-mx-error=1648 0.94%; 4 0.55%; 9 1.01%
214-2.0.0 079 one-domain-per-session=247 0.14%; 0 0.00%; 2 0.22%
214-2.0.0 080 siq-query-cache=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 081 siq-query-made=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 082 siq-score-reject=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 083 siq-score-tag=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 084 spf-pass=542 0.31%; 1 0.14%; 1 0.11%
214-2.0.0 085 spf-fail=2530 1.45%; 11 1.51%; 16 1.80%
214-2.0.0 086 spf-softfail=1101 0.63%; 4 0.55%; 4 0.45%
214-2.0.0 087 mail-bl-mail=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 088 ns-bl-mail=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 089 uri-bl-mail=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 090 RCPT=185173 100.00%; 813 100.00%; 980 100.00%
214-2.0.0 091 rcpt-drop=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 092 rcpt-parse=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 093 rcpt-reject=163240 88.16%; 714 87.82%; 856 87.35%
214-2.0.0 094 rcpt-tempfail=19 0.01%; 0 0.00%; 0 0.00%
214-2.0.0 095 rcpt-relay-denied=202 0.11%; 0 0.00%; 0 0.00%
214-2.0.0 096 rcpt-unknown=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 097 msg-queue=146 0.08%; 0 0.00%; 0 0.00%
214-2.0.0 098 quit-after-rcpt=213 0.12%; 0 0.00%; 0 0.00%
214-2.0.0 099 forward-helo-tempfail=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 100 forward-helo-reject=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 101 forward-mail-tempfail=2 0.00%; 1 0.12%; 1 0.10%
214-2.0.0 102 forward-mail-reject=163 0.09%; 1 0.12%; 1 0.10%
214-2.0.0 103 forward-rcpt-tempfail=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 104 forward-rcpt-reject=1223 0.66%; 4 0.49%; 6 0.61%
214-2.0.0 105 connect-rcpt-bl=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 106 connect-rcpt-wl=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 107 mail-rcpt-bl=28 0.02%; 0 0.00%; 0 0.00%
214-2.0.0 108 mail-rcpt-wl=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 109 rcpt-bl=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 110 rcpt-wl=13963 7.54%; 93 11.44%; 117 11.94%
214-2.0.0 111 click-pass=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 112 click-fail=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 113 click-ttl=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 114 helo-rcpt-params=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 115 one-rcpt-per-null=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 116 null-rate-to=104 0.06%; 0 0.00%; 0 0.00%
214-2.0.0 117 time-limited-rcpt=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 118 DATA=146433 100.00%; 600 100.00%; 732 100.00%
214-2.0.0 119 data-accept=18178 12.41%; 93 15.50%; 118 16.12%
214-2.0.0 120 data-drop=126 0.09%; 0 0.00%; 0 0.00%
214-2.0.0 121 data-reject=104 0.07%; 0 0.00%; 0 0.00%
214-2.0.0 122 data-tempfail=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 123 data-354=146203 99.84%; 600 100.00%; 732 100.00%
214-2.0.0 124 grey-continue=1496 1.02%; 2 0.33%; 2 0.27%
214-2.0.0 125 grey-tempfail=126 0.09%; 0 0.00%; 0 0.00%
214-2.0.0 126 grey-reject=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 127 call-back-made=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 128 call-back-skip=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 129 call-back-cache=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 130 call-back-accept=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 131 call-back-reject=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 132 call-back-tempfail=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 133 call-back-strict-greeting=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 134 call-back-uri-greeting=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 135 MESSAGES=146203 100.00%; 600 100.00%; 732 100.00%
214-2.0.0 136 msg-accept=15732 10.76%; 93 15.50%; 118 16.12%
214-2.0.0 137 msg-discard=3280 2.24%; 0 0.00%; 0 0.00%
214-2.0.0 138 msg-drop=784 0.54%; 11 1.83%; 11 1.50%
214-2.0.0 139 msg-reject=124859 85.40%; 492 82.00%; 599 81.83%
214-2.0.0 140 msg-tempfail=18 0.01%; 0 0.00%; 0 0.00%
214-2.0.0 141 msg-trap=123607 84.54%; 489 81.50%; 596 81.42%
214-2.0.0 142 dsn-sent=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 143 disconnect-after-dot=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 144 line-length=355 0.24%; 10 1.67%; 10 1.37%
214-2.0.0 145 strict-dot=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 146 virus-infected=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 147 msg-tagged=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 148 ctasd-spam-reject=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 149 ctasd-spam-suspect=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 150 ctasd-spam-tag=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 151 ctasd-vod-reject=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 152 ctasd-vod-tempfail=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 153 digest-bl=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 154 dns-bl-headers=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 155 dupmsg-cached=507 0.35%; 1 0.17%; 2 0.27%
214-2.0.0 156 dupmsg-hit=3280 2.24%; 0 0.00%; 0 0.00%
214-2.0.0 157 emew-pass=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 158 emew-fail=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 159 emew-ttl=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 160 deny-top-content-type=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 161 deny-content-type=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 162 deny-content-name=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 163 deny-compressed-name=9 0.01%; 0 0.00%; 0 0.00%
214-2.0.0 164 grey-content=447 0.31%; 1 0.17%; 1 0.14%
214-2.0.0 165 grey-hash-mismatch=18 0.01%; 0 0.00%; 0 0.00%
214-2.0.0 166 grey-hash-replaced=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 167 rfc2822-7bit-headers=41 0.03%; 0 0.00%; 0 0.00%
214-2.0.0 168 rfc2822-min-headers=157 0.11%; 0 0.00%; 0 0.00%
214-2.0.0 169 rfc2822-missing-eoh=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 170 rfc2822-strict-date=18 0.01%; 0 0.00%; 0 0.00%
214-2.0.0 171 message-limit=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 172 message-size=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 173 spamd-connect=1462 1.00%; 3 0.50%; 3 0.41%
214-2.0.0 174 spamd-connect-error=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 175 spamd-reject=609 0.42%; 3 0.50%; 3 0.41%
214-2.0.0 176 spamd-sender-marked-spam=5 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 177 spamd-tag=28 0.02%; 0 0.00%; 0 0.00%
214-2.0.0 178 domain-bl-body=301 0.21%; 0 0.00%; 0 0.00%
214-2.0.0 179 mail-bl-hdr=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 180 mail-bl-body=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 181 ns-bl-body=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 182 uri-bl=68 0.05%; 0 0.00%; 0 0.00%
214-2.0.0 183 uri-dns-bl=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 184 uri-implicit=30 0.02%; 0 0.00%; 0 0.00%
214-2.0.0 185 uri-ip-in-name=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 186 _uri-ip-in-ns=1 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 187 uri-links-policy=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 188 uri-max-test=472 0.32%; 0 0.00%; 0 0.00%
214-2.0.0 189 _uri-ns-nxdomain=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 190 uri-reject-on-timeout=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 191 uri-reject-unknown=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 192 uri-require-domain=7 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 193 uri-require-ptr=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 194 uri-valid-soa=0 0.00%; 0 0.00%; 0 0.00%
214-2.0.0 195 uri-soa-error=0 0.00%; 0 0.00%; 0 0.00%
214 2.0.0 end #548 (m5OAqZ192330097400)

-- 
Anthony C Howe            Skype: SirWumpus                  SnertSoft
+33 6 11 89 73 78       Twitter: SirWumpus      BarricadeMX & Milters
http://snert.com/      http://nanozen.info/     http://snertsoft.com/

Lists Index Date Thread Search