It looks like your comment handling software is glitched. I don't think there is anything you can do on your end.

It looks like it could be a permissions thing. Have you uploaded or updated anything recently?

I haven't done anything, but I think you are right, that it is a permissions thing in MT.

A long time ago my web host moved me to a better server, surely that's when things got messed up.

I was just too ADD to notice until recently.

Make sure your mt-comments.cgi file has chmod permissions of 755. You can do that through your FTP program, or you can do that through your webhost control panel.

Permissions should be set to:

                                       Read           Write          Execute

Owners Permissions:         X                   X                   X

Group Permissions:           X                                        X

Public Permissions:           X                                        X

If that doesn't work and your Raid Server is using Slackware as an api, you'll have to upgrade to MT 3.3.

Oy, I hope this looks right in the comments.

Try what Tony suggests, but if it still doesn't work, the fact that the script is returning a 403 error may mean it's a problem with Apache's (the webserver program) .htaccess configuration file. That should be looked at before you do anything drastic.

Moxie:
I don't think it's you. I've been getting the same error ever since the Microsoft upgrade on Aug. 10th. Very annoying and I haven't had a few spare hours to call MS tech support.

I bet Belinda might be right. Not too long after I downloaded the next to last major Microsoft upgrade,which was Windows Defender, I couldn't access my Firefox browser. So, I had to get onto IE, and from there I had to download Firefox all over again. Luckily, all of my Firefox downloads were still intact. Because of that I haven't even bothered with the latest Microsoft Window Defenders upgrade. Who the hell needs it? I never use IE, unless I absolutely have to. The only thing I really use to any extent is Microsoft Word.

For quite a while now I've been unable to access URL's here, and being geek-challenged always figured that something was disallowing my access because of a deep-rooted hatred for career Marines. Now you admit to the same difficulties, so I'd hazard a guess that I was in error. Hope this helps.

This is a known problem at your host, related to a mod_security rule, that they have in place, with a solution.

Too many, commas.

I buzzed over to I hate that shit and sure enough the link to The Wine Commonsewer doesn't give anything but some goofy no access message when you click.

I left an update that got caught up in the comments need approval shredder but in the preview phase the link did work.

There really wasn't any reason why the link should not have worked and I haven't changed anything.

So today it works, clicks right through to the Thomas Jefferson Cultivated Life post.

Thanks.

Auuugggghhhhh!

The link worked in preview mode but now that it posted it doesn't work.

Wonder if this will work:

The Wine Commonsewer

Both links work in preview.

I changed the permissions, rebuilt, but the problem is still there.

I may have to upgrade to the latest version of MT. Tried to do that the other night, but it looked a lot like installing MT from scratch and I bailed.

Now, the link embedded in the body still works but the posted by TWC link doesn't work. As some much wiser than I have proposed on this thread, it looks like an issue on your end. Sorry.

The solution. (But I repeat myself...)

I looked for that code, never saw a ";" to replace with a "&" And even in the sample provided, I couldn't understand. Nothing changed, the two lines are the same!!!

It was gibberish, and I'm no stranger to code. But I'll go and look again.

Here's what you have:
           return sprintf(qq(<a target="_blank" title="%s" href="%s%s?__mode=red;id=%d">%s</a>),
                          $url, $cgi_path, $comment_script, $c->id, $name);

You want:
           return sprintf(qq(<a target="_blank" title="%s" href="%s%s?__mode=red&id=%d">%s</a>),
                          $url, $cgi_path, $comment_script, $c->id, $name);

(I linkified the changed parts to highlight them)