<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Virtual Appliance on Evan Hoffman</title><link>https://evan.wtf/tags/virtual-appliance/</link><description>Recent content in Virtual Appliance on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Mon, 04 Oct 2010 18:24:12 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/virtual-appliance/index.xml" rel="self" type="application/rss+xml"/><item><title>The Barracuda Spam Firewall VMware Appliance (Vx) finally exists!</title><link>https://evan.wtf/2010/10/04/the-barracuda-spam-firewall-vmware-appliance-vx-finally-exists/</link><pubDate>Mon, 04 Oct 2010 18:24:12 +0000</pubDate><guid>https://evan.wtf/2010/10/04/the-barracuda-spam-firewall-vmware-appliance-vx-finally-exists/</guid><description>&lt;p&gt;When I started at my current company, spam was handled with a separate server running SpamAssassin and a few other services. This sort of got the job done but required babysitting. I wasn&amp;rsquo;t part of the Sysadmin team at that point but I know they had to restart SpamAssassin relatively frequently, manually clear out the email queue when people noticed they weren&amp;rsquo;t receiving email, etc.&lt;/p&gt;&#10;&lt;p&gt;After a few months, someone wised up and purchased a Barracuda Spam Firewall. I assumed this was basically a pretty GUI wrapper around the same tools we had already been using, but it was certainly worth the money. In addition to the basic filtering of spam it filtered for viruses, performed recipient verification against AD via LDAP, had nice graphing and reporting.&lt;/p&gt;</description></item></channel></rss>