Bill said:
I tested a Barracuda Spam Firewall here at work as a demo unit, and
we were not impressed at all. We eneded up going with another
solution. My main complaint about the Barracuda was that half of its
spam filtering work was being done by blacklists like spamhaus and
spamcop, which can eaisly be done with any MTA that supports
blacklists.
I don't understand this objection!
Firstly, Barracuda products are advertised as consisting of open-source
software; I haven't seen anything to suggest they have any custom
software components at all, except for the GUI and some bug-fixes.
Therefore I wouldn't expect Barracuda to be able to do anything that
can't be done with off-the-shelf free software. I don't see why that
would be an objection, in itself, unless the price of Barracuda products
is such that one would expect to see custom, commercial code in the product.
As far as the use of public blocklists is concerned, different
blocklists obviously have different data-collection strategies and
listing policies. Many of the major public blocklists ocupy a 'niche'
that it would be difficult for a private operator to fill; spamcop, for
example, relies on a large network of volunteer reporters.
Are you objecting to the fact that a commercial product is profiting
from resources offered for free? I can dig that, but I'm not sure that I
could sell that objection to an employer. And I don't know what
arrangements Barracuda might have made with those lists.
Or is it your case that a greater proportion of Barracuda's work should
be done using some other method than blocklists? If so, then I'm not
sure why you would say so; I would have thought that whatever works
best, is the best way to make it work.
I presumed that the USP of the Barracuda line is not that they
incorporate any unique technology; but on the contrary, that their
offerings are made exclusively from industry-standard FOSS components,
offered as fully-supported appliance solutions. Assuming they've set the
price right, I'd suppose that would be an attractive offering. Why
dicker around configuring Sendmail, SpamAssassin, ClamAV, Sophos,
Kapersky and so on, if Barracuda have already done it, and are willing
to support it?
They no doubt have made some improvements since our Demo was over a
year ago, but I do know a couple places using the Barracuda and they
confirm that half of the filtering is still done by blacklists. On
top of that it would have taken 15 of them to handle our mail load.
OK, so I still don't know what's wrong with using blocklists to block spam.
"It would have taken over 15 of them" - are you saying that your site
handles in the region of 15 x 15 (=225) million messages per day? Or are
you reporting that Barracuda are over-rating their product's
performance? (That's one of the questions the OP was asking).
Our solution ended up be ing a very heavily customized version of
CanIT from roaring penguin software. Of course we are a *NIX/BSD
shop, and CanIT depends heavily on *NIX resources.
OK, so it seems that Barracuda's fully-supported appliance-style
offering has no special attractions for you; you can evidently support a
heavily-customised solution in-house. My reading of their bumph was that
their main selling point is that Barracuda is a plug-and-go thing -
that's what I understand by "appliance".
By the way: what proportion of the spam that your custom CanIT solution
blocks, is blocked by reference to public blocklists?