Hi,
I may be coming into this discussion to late. Please take me with a
grain of salt, I'm vocal about this topic.
We've used vendor products as adjunct machines for spam and virus
filtering. We thought the other products would bring value and give us
some more time. That just didn't happen. We spent all the time we were
supposed to save (and more) managing the vendor relationship. Trying to
get features added to the product was a pain in the keester. Vendors can
make some broad brushed assumptions about spam, I'm only interested in
blocking authentic UCE; local practice should define UCE, not a vendor.
We are now using postfix+amavisd-new+clamd...works awesome. We are a
small shop and only process 80k to 150k messages per day. Less than 15k
messages each day are legit mail and we've had less than 10 user
complaints of false positives in 8 months...awesome, awesome, awesome
results.
My experiential talking points for not using an appliance for spam and
virus scanning:
+ A vendor product can never give the quick reaction time that an
open platform can bring.
+ The larger and more popular the vendor the worse it gets.
+ Leave the "standard" packages and higher pricing usually offsets
any savings.
+ Leave the "standard" configuration and it probably won't be as
reliable.
+ The fine people on this list can provide more real world
experience that a corporate R/D department.
+ If decision makers want to compare apples to apples then they need
to go through the history of lists like this and make and understand all
the cool/effective/creative solutions provided here.
+ When a vendor discontinues a product you essentially lose the
value you purchased. If you use an open product you can recycle the
experience and knowledge. Hands on knowledge never depreciates.
Granted, open source projects/applications have a steep learning curve.
The best efficiencies are always realized with familiarity and more
knowledge, not less knowledge. Unfortunately, everybody wants something
for nothing and sales people are trained to sell...I've been one, don't
flame me. :)
Take this for what its worth. I find that if I talk about open source
implementation challenges people get nervous quick. As a geek, its best
to keep the engineering/implementation challenges and associated
discussions in the right arena. The "big office" types only like to hear
about solutions.
Outsourcing spam and virus scanning is a false economy. Don't drink the
cool aid.
Andy
Rocco Scappatura wrote:
Hello,
During this days my company starts to investigate about the possibility to
adopt an appliance to replace amavisd-new... :(
The main reason is the difficult to manage spam traffic with SA. I have
faith and I don't think that the appliance that we choice for test purpouse
(Netasq f100) wouldn't be better...
Is there anyone who can explain me some good reason to continue to use
Amavisd-new in place of every other appliance that perform virus and spam
scanning?
Many thanx,
rocsca
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
