scouts-l Mail Archive for August of 2000: Re: Problems getting heard on Scouts-L
Cheryl Singhal (csinghal@CAPACCESS.ORG
Tue Aug 22 1972 - 07:56:28 CDT
Sorry for the extensive quote --
On Mon, 21 Aug 2000, rlazell wrote:
> to the list of when one first posts?) This person is very frustrated and I
> hope one of our daily good turns might be to give him some help.
> get my feet wet and send a short >message, I received the expected,
> automated reply..."your message has been forwarded to a >moderator...".
What's the rest of it?
> After waiting patiently for a week or so, I sent yet another message,
> realizing that >I had violated the protocol by not introducing myself to the
It's usually best to start that one out "DEAR MODS --"
> group formally. After waiting >another week or so, I tried yet a third time,
> and a forth, etc. I then resorted to sending e-mails >directly to the
> moderator identified. No response. I have now sent several messages to the
Until about 6 months ago, I had never sent a message to a MOD that
wasn't answered within a day. About 6 months ago, the regular MOD on one
of my lists went on sabbatical and the software refused to cooperate with
substitutions. Other than that one list, all MODS answer e-mail within a
day (counted at their end -- i.e., if you send it at 11pm Pacific, and
they log on at 9 am GMT, it could take 36 hours Pacific)
> list >owner without any reply of any kind. I am appalled and more than a
> little disappointed >in this >fruitless effort to communicate. It has been
> several weeks now. I must assume that I am >doing >something wrong.
First thing to do -- send a message to the listserv asking it to send you
your current settings. It took me a bit a figure out that since default
is NOREPRO, I didn't see my own postings, so the only way I knew they'd
gone out was if someone responded. Then change the default to REPRO so
you WILL see your own.
Then -- read the incoming message about the moderator again. The only
time you hear back from the mod is if (s)he's bouncing your message for
some reason. Otherwise, it goes out.
The most common causes for being put on moderation: excessive quoting
(defined as more than 2 lines) too often; sending HTML; sending binary.
Other things that *can* go wrong with any given message sent:
1) your end hiccups and thinks it sent it but didn't.
2) the hub between your end and the next port-of-call hiccupped etc
3) the list-serv is up but sloughing messages into the bit-bucket
4) the mod's end hiccupped and thinks it sent it but didn't
5) a personal or business emergency at the mod's end prevented his/her
dealing with the message in a timely fashion and it aged off their
6) TCU's computer is down but no TCU personnel knows it. And generally,
messages to list-servs don't bounce for some reason so we don't know either.