Resources
Blog
A Quick Way to Update Plesk’s Spamassassin Rules to Fix 2010 Issue
Posted by Jeff H. on February 08, 2010
Recently, I’ve been seeing more and more reports of users saying that good email are getting marked as spam. This issue is due to a bug in SpamAssassin that treats dates past 20xx as far future dates. Fortunately, you can easily update your spam assassin rules to fix this issue.
To be a Good Sysadmin Never Forget the Big Picture
Posted by Jeff H. on February 05, 2010
Today, we were to get started on a Plesk migration, but there's a problem. The new server lacks enough IPs to migrate the sites; this fact was unfortunately missed in my pre-migration screen. I don't want to delay migrating while we wait on the server provider to get us additional IP addresses, so what do we do?
Does Long Server Uptime Reveal Management Failure?
Posted by Jeff H. on February 04, 2010
While perusing some sysadmin blogs, I caught an older post by Sam Pointer regarding server uptimes that struck a chord with me. Too often I find people touting high server uptimes as evidence of success when it actually means you have failed as an IT manager.
7 Easy Steps to Improve Email Service on Plesk
Posted by Jeff H. on January 29, 2010
If you use Plesk, you can better protect your email service from spam, message overload and user password problems with a few simple tweaks.
How to Harden and Secure SSH for Improved Security
Posted by Jeff H. on January 29, 2010
With the sudden rise in SSH brute force attacks, securing SSH is more important than ever. In a shared hosting environment, you options are somewhat limited, but if you have a well defined user group, you can really lock down SSH such that brute-force attacks are no longer a threat. Here are a few methods you can employ to further harden your SSH installation.
How to Add Protective Measures Against SSH Attacks
Posted by Jeff H. on January 28, 2010
Earlier this week, I noted that ssh brute force attacks are on the rise. These attacks attempt to guess SSH passwords by repeatedly accessing your server. Often these attacks can disrupt SSH services. As I noted yesterday, you can use IPtables to rate-limit or throttle ssh connections. Today, I want to expand on that protection by adding some more security to SSH directly.
