This sometimes happens due to a technical problem, an improper configuration in your news server. Tell your ISP to see the instructions at
If they are unable or unwilling to follow these instructions (as some seem to be) or you don't want to wait, then you can instead mail your posts directly to the moderation program, which is what your ISP's news server is supposed to be doing automatically for you. (And if they don't, then it appears that they just put it out on their own server, which is why you see it but few others do!) The eddress to use appears to be constructed like this: take the newsgroup name, replace the dots with dashes, and tack @mensa.org onto the end. (There, that should make life a bit less easy for eddress harvesters.)
And now, some highlights of a conversation I had with somebody who bumped into this problem around the same time I did, and who received my posts, though apparently nobody else did. As usual, the names have been changed to protect the innocent... or, in the case of the guilty, to protect me. BTW, the monoalphabetic labels that I've substituted do not necessarily map to those I used on my PICS pages. I don't feel like going back and synchronizing them, so I'm starting anew.
Although my mensa.talk.misc posts appear on my local server (almost immediately, which also makes me suspicious), they don't appear to be getting out into the world. As a check I tried Deja but Deja doesn't have them, although it has the posts to which I was replying. Of course, my recent posts may have been of too little interest to prompt replies. But I'd feel better if I had some verification that my posts were actually going out. Please, somebody, reply.
- Thanks - Bill
Got it. Funny, I'm having the same problem.
Je merkredo, 03 May 2000 23:25:18 GMT, vi skribis:
Je Wed, 03 May 2000 23:25:18 GMT, en mensa.talk.misc vi skribis:
Interesting! But does the roboprogram keep the replies in a threaded format?
I actually got so frustrated with the posting problem that I unsubscribed.
There was recently a thread called "To the moderator", a discussion of posts that just disappear. Not quite like our situation, these were people who have posted before successfully, but whose posts sometimes don't get through. What I gathered from this thread is that when you post to mensa.talk.misc, the news server that you use is supposed to forward the post to the roboprogram address *instead of* blasting it out to mensa.talk.misc (thus requiring some special configuration at your ISP, I suppose). Then the roboprogram either sends it out to mensa.talk.misc from Mensa's server (if you're a known "good" poster) or forwards it to a moderator who bounces it back to you if it's not approved, or sends it out to mensa.talk.misc from Mensa's server if it is.
So it sounds like there's two solutions...
1) Your ISP has to configure its server to do this
2) You can mail it yourself to the roboprogram address.
So, to close this long answer to your question... I'm guessing that it will thread the same way, it's just going out through a different server.
What was happening to us, I think, is that our posts were just getting out to a little "local" part of USENET, probably being passed on until they bumped into a server that knew it wasn't supposed to be forwarding these unapproved messages in a moderated newsgroup. If you can look at the header details in the messages you've received, you'll see some fields that tell the server how to handle these messages, including a field that points to the roboprogram address!
But I guess we shall see, eh?
STUMP seems to be working well enough for me. Since I started e-mailing my replies directly to the moderator instead of relying upon my ISP's news server to do it (since it lacks that capability) or Deja (which can be erratic), I haven't had any posting failures at all and I get nearly instant response.
If it ain't broke, don't fix it.
It is broke. Just beause you are not having problems doesn't mean all is well.
I appreciate the distinction. However I would like to note that while some have problems, not all do.
The address can be found in the header of each mensa.talk.misc message. If your newsreader conceals all that stuff, open it up and study it...
A handy workaround to dealing with recalcitrant news servers that aren't set up properly.
Aha! Now I know the trick and can post to MTM. From the "To the moderator" thread I learned about STUMP, the problems with STUMP, the problems with servers that don't play nice, and, most importantly in my case... how to post to the newsgroup by mailing to [the moderation program].
My posts had been appearing on my local server, so I didn't even know that there was a problem. Except that nobody (save one person who appears to be sharing my little piece of the Net) ever replied. Of course, my posts may have been of too little interest to prompt replies. As a check I tried Deja, but Deja didn't have my posts, although it had the posts to which I was replying. And some had said that there was a problem with Deja anyway. So I wasn't really sure until recently about just what was going on.
On 19 May 2000 07:33:18 -0500, William W Patterson wrote:
Then your news server is not configured properly and you need to notify your ISP that the moderation directions are at:
The International mensa web site does have the link admin instructions on the newsgroup page:
as well as who to contact if there is a problem.
e-mailing directly to STUMP doesn't resolve the newserver problem. That needs to be resolved.
In some cases it's the only solution possible. The news provider my ISP uses isn't properly configured to e-mail to STUMP. When I e-mailed them about it the news provider (not my ISP mind you) sent me a rather snotty reply that they had no intention of e-mailing to the Mensa moderator, that they did their own moderating and didn't need any other moderator. It's obvious they're simply not going to make any changes even if they could figure out how. So until/unless I change ISPs or the ISP changes news providers mailing to STUMP is the answer.
Huh? What are you talking about? Who is the ISP? The ISP doesn't e-mail the moderator at all. The ISP directs the messages to a clearing house for moderation.
Did you point them to the webpage:
for configuration instructions??
If they are going to configure the groups properly, there is no sense carrying them at all, since for all purposes, they are using our newsgroup as a local group.
No ISP mails anything to STUMP on the chicago machine (although they could)!
"mensa.* is also listed in the master moderators.uu.net/uunet.uu.net database, so if you are using one of them as your moderator address that should work fine as well. "
They just configure this moderated group like any other -- sending the messages to the moderators master file. There they are forwarded to our moderation system.
Yes, several times. Their response suggested they weren't the least bit interested. At first I thought that the challenge of setting it up properly might be beyond their capability but from what they told me it appears they prefer that their moderated news groups not work.
I finally got tired of fighting with them and just adopted the practice of e-mailing responses directly to [the moderator]. I haven't tried posting to any other moderated usenet groups so I don't know if they're set up properly either.
My ISP is caught in the middle. They don't operate a news server but contract with a third-party to provide news service, setting up their DNS to direct my reader to their news provider's server.So that's the way it is unless I change ISPs or my ISP changes news providers.
So who runs this news service? What is the name of the newserver to which you connect? If they aren't going to configure properly, they don't need to carry our group. That will drive some people away from Mensa who don't understand it is a newserver problem.
Thanks, I'll look into that.
But I still think that a little note about this on the newsgroup page would be a good thing. Once one knows how this is supposed to work, the solution is obvious... but beforehand, not obvious at all. I wasn't familiar with this mechanism, and the probability is low that I would check the admin info concerning the serving of a newsgroup which I was already receiving. As for contacting somebody for help... why not save us *and* them some time and trouble, with that little note?
I've been in email contact with a person who did somehow receive one of my misrouted posts, a person who had simply given up on mensa.talk.misc soon after. I wonder how many others give up, or go away thinking that Mensans can't even run a news server... even though it's not Mensa's fault at all.
STUMP isn't broke. It is working the way it is intended to work. The decision to use STUMP was made long ago -- and that is that until someome comes up with a better free program.
So are you volunteering to fix it? Are you a skilled PERL programmer? Are you willing to volunteer your time? In the Full header is the address where STUMP is located -- so have at it please.
More than one person has had problems. If these are calmly reported, collected & analyzed, it is possible we can find out what the problems were. Some posters have ISP problems with misconfigured news groups - if one wishes to check this, go to www.deja.com and look to see if they've got your posts. If they don't, it's likely that your ISP is misconfigured. As someone remarked, it's a peculiar symptom though - you just feel ignored, since you can see your posts as can all others using the same ISP (or similarly misconfigured ISPs).
As I said in another posts, lost posts are a common problem with news - it's a complex network, and sometimes posts disappear - moderated or unmoderated. It's just that in unmoderated groups, you won't know your posts have disappeared, since you're able to see them.