Bluehost and Mac OS X Mail… The “Secret”

OK so here’s what the “Manual Settings” page at Bluehost doesn’t say.

You have to go to Account Information>>Outgoing Mail Server>>Edit SMTP Server List…

EDIT SMTP SERVER LIST
“Edit SMTP Server List” to change the outgoing mail server’s port to 26

[select yours…”box123.bluehost.com”]

Click on the advanced tab and check off  “Use Custom Port” and set it to 26. (no SSL)

Screen shot 2013-04-25 at 2.32.11 PM
This is where you set the Outgoing Mail Server’s Port… I’ve noticed that sometimes the Password on this settings page doesn’t stay… So double check that it’s still there if you still are having trouble sending mail.

 

  Then Quit Mail! and reopen it.

This is how your main Account Information screen should look in Mail's Preferences
This is how your main Account Information screen should look in Mail’s Preferences

 

Screen shot 2013-04-25 at 2.31.48 PM
This is how the Advanced Tab should look

 

…Anyway, here’s what settings are working for me:
Manual Settings
Mail Server Username: name@yourdomain.com
Incoming Mail Server: box123.bluehost.com port 143 (server requires password authentication) (no SSL)
Outgoing Mail Server:  box123.bluehost.com (server requires password authentication) port 26 (no SSL)

April 2013 – Some News Concerning Malware Attacks on WordPress Sites

First off, Here’s Matt Mullenweg‘s blurb about the recent botnet attacks on WordPress sites.  It’s good to listen to him because he’s the “founding developer” of WordPress, and the President of the company Automatic which is behind wordpress.com, among other things.

http://ma.tt/2013/04/passwords-and-brute-force/

From Matt:

supposedly this botnet has over 90,000 IP addresses, so an IP limiting or login throttling plugin isn’t going to be great (they could try from a different IP a second for 24 hours)

I’ve been noticing a few popular shared hosting providers have been having infrastructure problems lately.  I thought it was a coincidence, but after attempting to do some work on a client’s site hosted at Fatcow (not my favorite host, but they’re OK), I got hip to the fact there is actually a bit of internet-wide drama going on at the moment with WordPress sites getting hacked, or at least many attempts at this.

Here’s a message Fatcow sent out to its customers.

Important Information about Protecting Your WordPress Site

Dear [customer’s name],

Do you have a WordPress account with us? If so, we wanted to let you know about an attack on WordPress sites that started earlier this week, what we’ve done to combat it, and what you can do to protect yourself.

On Tuesday, a widespread “brute force” attack against WordPress started impacting sites across the internet. This attack is leveraging a botnet, which looks to have more than one hundred thousand different computers at its disposal. Its intent is very simple: to find and compromise WordPress sites with simple passwords, likely to use them later to distribute malware (and further increase the size of the botnet).

Over the past few days, we’ve made a number of changes to our network and infrastructure designed to mitigate the impact of this attack on our customers’ websites. Continue reading for a detailed account of what we’ve done »

Also, and we can’t stress this enough, we urge you to check your WordPress password and make sure it’s a strong one. The strong password guidelines in our Knowledgebase refer to your FatCow account password, but that advice is good for WordPress passwords, too!

We head into the weekend in good shape, but vigilant against a returning or altered attack. For those of you who have been impacted by these attacks, or our attempts to combat them, we do apologize for any service disruption. We also apologize for a longer-than-normal response time over the last few days while we’ve had “all hands on deck” addressing this issue. We appreciate your patience and understanding.

Sincerely,

The FatCow Team

Bottom Line: Harden your WordPress site a little.

  • Keep your WordPress Core software and plugins and themes up to date!
  • Use Capitals, Lowercase, Numbers and Symbols in your passwords… Avoid guessable/dictionary words
  • If you have a user called “Admin” or “admin,” take a moment to get rid of it.
  • If installing from scratch, modify your database table prefix in wp-config.php to something other than “wp_”
  • Never use any theme, plugin or hosting provider that forces you into leaving folder and file permissions set to be permanently extra lenient (if someone tells you to change a directory to 777, they don’t know what they’re doing or your hosting provider’s server settings are wack…)
  • Stay on top of comment moderation.  If you find yourself with thousands of unmoderated comments waiting for approval, and you don’t want to do the work, perhaps you’re not cut out for participating in that way with the masses, or you just don’t have the time.  Just turn comments off!

There are TONS of free plugins that can help you scrutinize your WordPress install.  I use this from time to time: WP Security Scan.