Work In Progress

Brilliant. Today I start getting errors from apache telling me that SecFilterInheritance is not a recognised keyword.

As you may recall (http://phil.abercrombie-family.org/index.php/2006/05/16/prl/), SecFilterInheritance is the key to disabling mod_security and allowing me to submit posts that contain the word p*rl.

Ah well. Somebody at rcthost changed something and didn’t tell me. What’s new.

So, I’ll try removing the .htaccess change and see what is the fallout. If this post succeeds, despite this word: perl ; then I will ignore the problem.

Apparently you can’t use the word p*rl in a WordPress post.

I discovered this the hard way, after writing a long discussion of how to use p*rl to chop up messages extracted from a MS-Exchange IMAP interface. When I submitted, the wordpress script crashed. IN time-honoured software-guy tradition, I tried a couple more times, and the wordpress script crashed each time. Then I had to do the debugging thing, where I narrowed my 400 word post down to one word by binary chop. The word was p*rl. I was quite annoyed. Especially when I found this link: http://wordpress.org/support/topic/64599

What is the point of blogging software that doesn’t allow postings that discuss p*rl? What else would anybody want to write about? I fumed. And I certainly didn’t post anything.

This was a long time ago, and the anger has worn off now. And I found this link:
http://positivefusion.info/archives/2005/02/20/201/ where a web hosting service with a more generous support arrangement documents the work-around to be placed in .htaccess for the wordpress admin directory:

<Files post.php>
SecFilterInheritance Off
</Files>

So now I can say it. perl. Ahhh.

For a while I’ve been subscribing to news alerts (via Google Alerts) for AppIQ and Storage Essentials. I always thought I might gateway these to a weblog sometime.

Now I have an IMAP mail folder full of messages, I’d like to import it into WP. My first thought was to move the messages to a mailbox that WP can POP from. This is only partially successful: the WP POPper doesn’t do a good enough job of decoding the multipart message and i end up with something like the following: