Googles free apps, like gmail, do have free options, but they also have limits - unless you want to pay $50 per year per user. That's still not unreasonable, but it's not quite the same as hosting your own server.
Fighting spam by handing it over to Google, is like firing your IT staff and telling employees to take their PC's to CompUSA or calling the Geek Squad. It will be cheaper, but the service isn't as good.
There are major privacy concerns when a company hands over core operations to other companies. Smaller organizations, like Banks, Credit Unions, and even small hospitals and medical offices can't do that or trust them without taking some major hits on their IT audits, and can't do this legally without going to the larger hosted mail handling firms, and they charge more like $15/user/month at the low end - more if you want anti-spam too.
Bringing spam fighting in house is not that hard, and depending on what you want to do/pay is up to you.
Most anti-virus programs have anti-virus aspects - programs like Zone Alarm Internet Security Suite are actually pretty good at it in fact.
For a network, on the low end you can roll your own using Linux or Windows, or buy a low-cost how-to like from
Piratefish.org for $67 - even gets some support too, and build it yourself using Linux.
On the mid-end, you can add in Anti-Spam software to most email servers, like Microsoft Exchange, or
Kerio Mail Server and even the free
Centos+BlueQuartz os that I use for hosting and email.
On the appliance solution side, you can run with a low cost
Barracuda 100 appliance for under $1000 and have the nice gui, phone support, Etc.
As for best practices, there's lots of things people should do:
* Never pass on that email from your Aunt Adele that has 50-60 other email addresses in it without cleaning all that crap up first.
* Never post your email address online unless you're ready to get spammed.
* Never enter an online contest with your real email address - make throw-away aliases on your mail server for that stuff. You'd never believe it if you won anyway.
* On business websites, don't post personal email addresses unless you encode them into an image - putting them directly into the HTML page makes them indexable and findable using search engines and spider programs.
* Be sure that your network has a proper SPF record. Without it, people will be able to send emails in your name from any server on the Internet. Inbound SPF filtering will prevent many of the emails from phishermen from getting to your users. The Piratefish and Barracuda have this.
* Use filtering technology on your email to prevent you from seeing non-related website links without warning text. If someone from aol.com sends me a link to banking.com, those links are highlighted with phishing warnings since only people@banking.com should be directing me to their site. The Piratefish and Barracuda do this.
* Setup your email filtering to include PDF and image scanning. This way, spammy language can be detected in pictures contained in email attachements. The Piratefish does this.
* Use DNS blacklists to prevent known high-volume emailers from getting junk into your inbox. Just about every spam filter on the planet does this.
* Secure the process of receiving email and sending email using SSL and TLS if possible. This helps prevent exposure of message content on potentially unprotected networks.
* Be wary of using shared hosting services that offer Linux shell accounts to users. If the hosting company offers that level of access, ask them specifically if those servers have "jails" for each website. If they do not, don't use them.
Hosting without jails leaves all content on the server ultimately accessible from any Linux command line.
* Clean your PC. Spammers can spam because people in the world don't know how to clean up their mess, and leave it connected. Those machines contribute to the mess. Use Spybot S&D, install JavaCool Software's SpywareBlaster (a good preventative). Free anti-virus like AVG Free work, but right now Kaspersky and Zone Alarm Internet Security Suite are the best - they both use Kaspersky's AV engine - and it protects against new threats faster than anyone elses solutions.
* If you run a network firewall, be sure to limit outbound access on port 25 to your mail server only. Large businesses should not be permitting port 25 outbound from workstations - since that's an email delivery port, only email servers should be using it. All firewalls should be configured to control the outbound traffic - and not just block inbound traffic, and let all outbound out. It's this type of "security" which has led to the situation we're in today. If you need help here, contact my employer about getting protected.
Cadamier Corp.
* Consider suing the senders of spam. This sounds crazy, but in the USA, if the sender is here in the US, they must abide by the CAN-SPAM act, and there's some people who have taken up the practice of suing spammers. I actually have a good case against CMP networks myself right now, and all it takes is a small claims court setup, a form letter sent via certified mail, and you're set. Present evidence that you've asked and asked them to remove you, and show them your most recent messages. In Colorado, I can sue for $1500 and they won't even fly their lawyers out for it - and that's $1500 in your pocket. Others have done it, you can too - just be sure not to bite off more than you can chew.