mt.cfg dark matter: OneHourMaxPings and OneDayMaxPings

As John Gruber pointed out the other day (and as many people have pointed out, many times in many fora), there are quite a few things that you can stick in Movable Type’s mt.cfg file that are either lightly (or confusingly) documented, in the file itself or the manual, or just aren’t documented at all, anywhere. As a stopgap (and a spur), I’m going to document my understanding of some of them, starting with a pair that are partly my fault, anyway: OneHourMaxPings and OneDayMaxPings.

MT 2.66 added a throttle for comments, based on IP address. MT 3.01D extended that throttle to TrackBack pings, still based on IP address. Oops, that meant that if you received more than one ping in ThrottleSeconds (20, by default) from the same IP address, it would be refused, even though the most likely source of two pings from the same IP address would be one legitimate post on another weblog, legitimately pinging two of your entries (“A response to Jane’s ‘Foo’ and ‘Foo, part deux'”). TrackBack spammers and flooders, of course, know about using anonymous proxies, so they don’t have any need to deliver more than one ping from a single IP address, and were unaffected.

MT 3.1x switches the TrackBack throttle from being IP address based to being simply a throttle on the number of pings: when you receive a new ping, MT looks up how many pings that weblog has received in the last hour, and in the last 24 hours, and if the number is over OneHourMaxPings or OneDayMaxPings, the ping is refused with a “403 Throttled” response. By default, if you don’t set it in mt.cfg, you get OneHourMaxPings 10 and OneDayMaxPings 50.

Those numbers ought to work just fine for lots of people, though I’ve noticed that in warblogger circles there’s quite a bit of use of automatic TrackBack to anything anyone links to, and quite a bit of heavy-linking, where everybody links to interesting posts, unlike a typical techblogger who would probably skip linking when she had already seen five or ten links to something. Where it’s really likely to trip people up is when they TrackBack outside the box, setting up a category to aggregate pings on a subject, like a conference or a recipe aggregator. They may need to up the numbers a bit, and a little documentation (along with moving it the hell out of a confusing text file and into a web interface) would probably come in handy.


Comment by Anil #
2004-09-13 02:21:37

Just so you know, Phil, I’ve got ”doc all the mt.cfg settings” and ”give phil’s request for a web interface” on my list. Once we get those done, I’m gonna give you the ”more flies with honey” speech. :)

Seriously, though, we appreciate the feedback and I’ve got a soft spot for curmudgeonry anyway.

Comment by Phil Ringnalda #
2004-09-13 09:50:30

And I’ll smile and nod and not believe a word you are saying ;)

Honey? My honey is in bugs #1515, #1298, #1568 and #1577. The only flies it’s going to catch are once the patch-rot sets in. (Yeah, I know, I probably didn’t beat a code freeze I didn’t even know about.)

Now, tell me, and be persuasive: am I really more likely to see a fix for the way that the bookmarklet puts invalid data in the database, and then the resulting errors are only partly papered over, if I just keep updating that patch as I get my hands on new releases, or if I put that patch out for public use, along with the sort of post I’ll just naturally write about having something as simple as deciding between a checkbox and a select menu left broken for five and a half months now (starting with #663)?

Comment by Evan #
2004-09-13 10:21:44

This lack of documentation has been frustrating to me. I’m trying to figure out whether MT 3.1 has the features that I’m looking for. The ”Features List” on the Moveable Type website is somewhat helpful, but my main method for getting the real details is to look through the manual and see what’s new/changed in the configuration parameters and template tags.

If those parameters are underdocumented, that’s not exactly going to speed up my decision to upgrade from MT 2.6.

Comment by backlon #
2005-05-05 14:24:23


Oh boy do I feel stupid. I assumed that the throttling was happening somewhere deep in the server. I’ve been bugging the sysadmins at my university for a month now. I found this page and now I’ve offered them makeup beers. Sigh.

thanks so much for having this info up and findable in google!

Name (required)
E-mail (required - never shown publicly)
Your Comment (smaller size | larger size)
You may use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <del datetime="" cite=""> <dd> <dl> <dt> <em> <i> <ins datetime="" cite=""> <kbd> <li> <ol> <p> <pre> <q cite=""> <samp> <strong> <sub> <sup> <ul> in your comment.