Recently in Tech Category

Rock. Suck it, spammers.

| | Comments (1)

After a few hours of running the anti-spam setup described in the previous post, the proxy logs go something like this:

Date IP Address Log Message
2005.02.05 16:15:02 203.90.124.135 Proxy Comment Submission from 203.90.124.135 denied. Reason: listed in opm.blitzed.org
2005.02.05 18:29:29 211.46.197.60 Proxy Comment Submission from 211.46.197.60 denied. Reason: listed in opm.blitzed.org
2005.02.05 21:04:32 211.46.197.60 Proxy Comment Submission from 211.46.197.60 denied. Reason: listed in opm.blitzed.org
2005.02.05 21:04:34 211.46.197.60 Proxy Comment Submission from 211.46.197.60 denied. Reason: listed in opm.blitzed.org
2005.02.05 21:36:27 203.197.169.19 Proxy Comment Submission from 203.197.169.19 denied. Reason: listed in opm.blitzed.org
2005.02.05 22:59:29 211.46.197.60 Proxy Comment Submission from 211.46.197.60 denied. Reason: listed in opm.blitzed.org
2005.02.05 23:14:32 203.197.169.19 Proxy Comment Submission from 203.197.169.19 denied. Reason: listed in opm.blitzed.org
2005.02.06 00:00:06 65.26.219.58 Proxy Comment Submission from 65.26.219.58 denied. Reason: listed in opm.blitzed.org

... and the server logs go something like this (of course, 192.168 IP is my testing, and real emails are munged):

[Sat Feb  5 11:21:01 2005] spam False from Kyle/kyle@example.org/24.236.224.237: score 0.0 (limit 5.0)
[Sat Feb  5 12:21:59 2005] spam True from spamtard/ralsky@spamtard.biz/192.168.192.39: score 8.8 (limit 5.0)
[Sat Feb  5 12:22:22 2005] spam True from spamtard/ralsky@spamtard.biz/192.168.192.39: score 8.8 (limit 5.0)
[Sat Feb  5 15:23:53 2005] spam True from texas-hold`em/huy_lo5925@mail.me/66.144.4.8: score 15.5 (limit 5.0)
[Sat Feb  5 19:32:26 2005] spam False from Joe Gasiorek/joe.something@example.com/66.227.166.171: score 0.0 (limit 5.0)
[Sat Feb  5 19:50:37 2005] spam False from Tim Miley (playing evil spammer)/t@brokenisp.net/67.177.157.65: score 0.0 (limit 5.0)
[Sat Feb  5 19:53:37 2005] spam True from jg/bob@net.com/66.227.166.171: score 8.4 (limit 5.0)

After running through my DB of comments, I find two or three that have a score high enough to be moderated (but not outright blocked.) I think they hit on the comment author's email ending in a number.

All in all, I'd just like to say... suck it, spamtards.

Spam me. Spam me hard

| | Comments (3)

I've been playing with two anti-spam plugins, from Kahuna Burger, and I think they're nearly ready for primetime.

The first is mt-proxyplug, which seems to be stopping a fair number of attempts right at the start. I needed to hack it a little bit, though, because I run a mod_perl proxy setup. This gets me a lot of speed, and keeps most things from hitting the heavy mod_perl apache on the backend. And with it under mod_perl 1, things actually work right. That is, things besides MT-Blacklist. While MT-Blacklist is an awesome program, it is rather... unsupported under mod_perl. Oh well.

The second plugin I'm using now is mt-spamassassin (the lower-case one, not to be confused with MT-SpamAssassin. The latter is very nice and full featured, however, I'm looking for simple, run it, and it's so simple it doesn't break when run under mod_perl. Maybe I want too much. I did use the rule sets from the second one, and added a few of my own.

The one I'm using is very simple, just slightly above proof of concept stage. I run SpamAssassin as a daemon on the same machine, and pass comments to that. The latter MT-SpamAssassin actually imports the SA perl module, which is probably a good way to go for a lot of things, but I want to keep my mod_perl processes a bit smaller than that. SpamAssassin imported into apache/mod_perl does not strike me as a small solution.

The good thing is, the latter heavy-weight plugin author has already gone through and made a rule set out of the MT-Blacklist rules, and that's what I'm using as a base. I added a few rules to that, and I think with a bit of keeping up on it, it'll work.

I still have to hack trackback support into these. It seems that trackbacks are the red-headed step-child in MT.

After I think this has been working reasonably for a little bit, and I'm not getting errors out of it, I'll deploy it on the Mises Institute blog.

Maybe time to write a simple script to go through the MT DB and see if anything would be moderated or blocked that shouldn't be... oh, and there is no message if it gets all-out denied.

So Spam me. Spam me hard. I want lots of attempted messages, and I want to know if legitimate comments get blocked.


Posted with mod_perl 2?

| | Comments (0)

This post courtesy of MT running on Apache/mod_perl 2...

Mason and MT

| | Comments (3)

So, I'm getting closer to making this look how I want, although I've made some grievous hacks to get here, so I'll wind up overwriting some important stuff, I'm sure.

I'm planning on having another box towards the bottom -- under the article part, with probably 4 items accross, around the same width as the current nav/sidebar. I'm not yet sure whether I'll put the MT stuff there, or in the sidebar... at least Mason makes this stuff dead-simple to change.

I'll probably do a bit more reworking on the Mason components that I'm outputting from MT -- they could even take arguements and such without much effort, although I still haven't found any thing that would be worth passing as an arguement.

I also need to clean everything up -- and make sure that the MT links and such actually work. I'm quite sure that at this point it is still impossible to post comments.

I love the way Mason lets me put this together, now that I've got everything broken up into components. I can't actually figure out how to show HTML in here and have it not be interpreted, so we'll just leave that off for the moment... and some point I'll figure out a good way, and show that and some other stuff.