I can update in the next few days, but I find it hard to believe that—if this were a bug—it hadn’t been discovered and fixed by 1.6.2.
Which leads me to believe that there must be something I’m doing wrong in twiddling the various knobs and switches involved in configuring a weblog to send trackback pings.
You know?
To answer your question: no, this feature has never worked for me. Granted, I haven’t been trying for all that long—maybe a month or so—but it’s failed every time. And I haven’t fiddled with any of the core or system code that sends and records trackback pings.
I also looked in the db and there are no saved sent trackbacks. From the code it looks like it’ll only save them if they’re successful, but I figured I’d add that info just in case it’s helpful.
Another note: I tried testing with a local install with the exact same codebase. Since I’m using MAMP locally, which uses port 8888, I had to temporarily comment a couple lines of code that check for port 80 so I could do my test. I created a post, then created a new post that pinged the first post’s trackback URL. Interestingly, when I submitted post #2 (that sends the trackback ping), the page hung and the webserver spiraled out of control. I had to kill httpd. And the trackback ping never was sent/received.
I don’t know if that experiment tells you anything, but it sure was a failure.
For what it’s worth, the site in question is hosted at EngineHosting, which is familial to you guys and may help troubleshooting. I didn’t install EE myself—they installed the core and other items for me.