I asked in the Imail list for IMgate + (Declude or Sniffer) users to tell
us how many each rejects. NO response.
But I've just installed an IMGate for a Sniffer user in South America (no,
it was not me flying to Rio to watch the Girls from Ipanema).
ssh really has no tillilation value. :))
For Wednesday, the IMGate admin reports:
> >Sniffer detect as spam?
>
>911.
and IMGate did this on Wed:
Grand Totals
------------
messages
36769 received
24682 delivered
12 forwarded
199 deferred (1456 deferrals)
197 bounced
27192 rejected (52%)
911 Sniffer rejects / (911 + 27192) = 3.24% of total rejects.
So, assuming IMgate + Sniffer rejects equals 100% of spam, IMGate is only
missing 3.25%. Not bad ... for the price. :))
and sniffer has 50% less traffic to sniff, greatly reducing the load on the
Imail box.
I think it's worth harvesting the @sender.domain and ip+PTR of those
Sniffer rejects in the Sniffer logs to see if the any one is numerous
enough to feed forward to IMGate, to turn the "content-filtering rejects"
by Sniffer into "envelope rejects" by IMGate.
The IMGate client also has a Sniffer FreeBSD binary so I'm looking into how
to set that up on IMGate "behind" the IMGate filtering, and remove all that
work from IMail.
Postfix content-filters like SpamAssassin are typically set up in front of
what IMGate does. That's @ss-backwards. You want to do all envelope
rejects before any content-filtering.
MadScientist at Microneil tells me he's got some big improvements for
Sniffer coming up, so that bears watching. I'm feeling really sorry for
that 3.25%. :))
Len
