- Get a grip or you don't get the job
- Desktops of the future here today
- Researcher hides IE attack on Web
- Cisco third quarter 2008 channel stuffing
- Sci-Fi's goofiest gadgets and technology
Crackin' the Kraken bot. Listen now!
Wireless dangers at airports. Listen now!
Most companies have a solid disaster recovery plan in place to handle a "complete failure" of its Active Directory, which is really quite rare. What most recovery plans are missing, and the most common scenario, is a means to efficiently restore single directory objects. In this paper, we'll explore what most disaster recovery plans already address, highlight potential weak points, and suggest solutions that help fill those gaps-without requiring you to completely re-do your existing plan.
Get the latest on storage technologies that allow IT professionals to better cope with new IT demands. Learn how storage technologies can help you successfully tackle e-Discover, regulatory compliance, green data center initiatives and the data explosion. Get all the details now.
Watch Raven Zachary, Research Director for Open Source at the 451 Group, an independent IT analyst firm, discuss the emergence of enterprise Linux and the role of Oracle Unbreakable Linux support.
It's amazing that network management goes open source. Realy.
http://altiores.com- exploder
We have a Solaris Sparc machine configured with sendmail. Currently a lot of spam is coming to our server. Can you please
suggest me how to control spam.
-- Manjunath
There are several ways to do it, but I'd suggest starting with a spam-control solution on a separate server. This takes the processing load off of your mail server in dealing with the spam and gives you a fallback option if something happens to where you can reroute email to the Solaris box.
The most popular option is to build your solution using Spamassassin. But also consider using Postfix as a replacement for sendmail. Out of the box it does quite a bit of spam control on its own by checking for valid domain existence, valid A or MX record for the sending domain, etc. You can add more spam hurdles by checking against several realtime blacklists that look for known sites that are currently sending spam and IP address ranges assigned to Internet providers. You can do this with Sendmail as well, so it's partly a matter of what you are the most comfortable with. There are several "cookbook" solutions you can find using Google that will show you how to put together a system using a variety of components.
There are "add-ons" such as Razor that supplement and enhance SpamAssassin. While Spamassassin comes with quite a number of built in, there are even more for the picking. One of the best sites for finding rule sets is www.rulesemporium.com.
However, don't just set and forget - the spammers certainly aren't doing that. This is an ongoing process that you will have to monitor, tweaking it over time as the spammers adjust their assault tactics to keep the wolves at the gate. Check this site often as the rules sets can often be updated on a daily basis based on what is being seen in the wild.
Depending on your volume of e-mail, you may find that you need to have a gigabyte or more of RAM installed in the system running Spamassassin. Periodically checking for new versions of SpamAssassin and the other modules will give you the the best chance of keeping spam out of your mail system.
Most spam appliances work fine on a UNIX systemBy stk on July 22, 2007, 4:30 pmMost spam appliances act as a SMTP proxy so they are transparent to the operating system you use. My company Abaca offers a 99% spam accuracy guarantee where...
Reply | Read entire comment
RE: Blocking spam on a Unix systemBy peterls on July 22, 2007, 4:04 pmWhy going to spend a few hours on implementing SA, changing your set up and when everything is installed check and maintain the anti spam solution on a daily base?...
Reply | Read entire comment
Why SpamAssassin?By Anonymous on July 17, 2007, 10:15 pmI would not recommend SpamAssassin. SA is a great product but it is slower than other open source products and requires substantialy more maintenance (updating rules,...
Reply | Read entire comment
RE: Blocking spam on a Unix systemBy Nat on July 16, 2007, 8:22 pmGreat article Ron. I have two additional thoughts you might choose to share. First, SpamAssassin can be DNS intensive, so I highly recommend installing a local caching...
Reply | Read entire comment
View all comments