Archive for December, 2007

Good Advice for dealing with an Incorrect Spam Suspension Warning???

Sometimes website owners will incorrectly be associated and reported as a spammer.  (I’m talking email spam here.)

Unfortunately it is all to easy for an email spammer to simply code your email address into the header of an email, even though they are actually sending the email from some other email account and then your email account gets associated with grand titles like term life insurance quotes or the latest Brittany Spears viral image teaser of the day or sometimes it is used in PayPal or Ebay phishing emails.

I’m sure you have probably seen an email that appears to be coming from someone or some site that you know, but if you dig into the properties of the email address, the real email address is something entirely different.

The issue is that some hosting companies will receive a spam complaint and simply shut down your account without doing the appropriate level of due diligence.

This afternoon, I came across some good technical advice to both help you prevent this from happening in the first place and the right responses to que your webhost up with to defend against your account being shut down inappropriately on a forum at Lunar Pages.

You may not be doing anything that can be reasonably construed as spam, but are you absolutely certain that your account and site haven’t been hacked? Could code have been inserted into your site to generate spam? Have you confirmed that there are no changes to your files that were not made by you, or without your knowledge and consent? You’re going to have to go through your files with a fine tooth comb looking for unexplained changes. I find it handy to do a weekly ls -alR of all my files (via cron) to flag changes — if you haven’t been doing that, it’s a lot more work for you to find what’s changed.
You should ask LP if they have any logs of outgoing mail from your account, which might give you a hint as to what got hacked. It’s also very possible that some jackass has simply forged your email address to their spam, and you’re paying the price (even though the spam never went through your account). Demand that LP produce the “spam” emails, with full headers, so they can be examined to find out exactly where they came from. If they won’t, tell them you’ll see them in court if they try to close your account. They need to learn that some twit claiming you’re spamming is not sufficient grounds to disrupt your business — they need to prove it’s originating from your account. It may or may not cut any ice with them that you didn’t know about it, but if you can show you’re taking steps to stop it and prevent future problems, they should relent.

Spam Suspension Warning???  from the Lunar Forums

Latest WordPress Upgrade Fixes Very Annoying WindowsLiveWriter Publishing error!

I mentioned yesterday that WordPress had issued a new upgrade and they were strongly recommending that people should Upgrade their WordPress Software to 2.3.2 Now.  I was very happy to see that after I updated one of my sites a publishing bug went away completely!

I had repeatedly run into an error on one of my sites that enabled women to write reviews about sexy boots and other skimpy products.  The error manifested in several nasty ways:

  • Publishing with WindowsLiveWriter would publish, but would always generate an error and WLW would not be able to save a link to the published post for future changes
  • There were multiple code errors present when ever I navigated around in WordPress, tried to make changes, approve comments a host of issues.

I had run a number of upgrades on this site and another impacted by the problem (saw this on about 10% of my WordPress sites).  I restarted MySQL, repaired databases, upgraded WordPress, upgraded WLW but nothing fixed it until this latest WordPress upgrade.

I’m very happy that that problem is fixed!

Upgrade Your WordPress Software to 2.3.2 Now

That is the message coming from WordPress.org.  The former version of WordPress, version 2.3.2, had some serious security issues that are supposedly addressed in 2.3.2.

Here is the note from the WordPress Development team

WordPress 2.3.2 is an urgent security release that fixes a bug that can be used to expose your draft posts. 2.3.2 also suppresses some error messages that can give away information about your database table structure and limits and stops some information leaks in the XML-RPC and APP implementations. Get 2.3.2 now to protect your blog from these disclosures.

As a little bonus, 2.3.2 allows you to define a custom DB error page. Place your custom template at wp-content/db-error.php. If WP has a problem connecting to your database, this page will displayed rather than the default error message.

For more detail on what’s new in 2.3.2, view the list of fixed bugs and see the changes between 2.3.1 and 2.3.2.

This latest release sounds a little more ominous than usual and so I’m walking through each of my blogs pushing out an update/upgrade as this sounds like more of a fix than the typical call for vitamins for women and men that usually seems to be pushed out from WordPress.org where so many upgrades and updates are offered that it almost seems as if they are having you update just for the sake of checking their site on a regular basis (I know that that is not the case, but the sheer number seems nuts sometimes.)