Quoting John W. Lemons III ([EMAIL PROTECTED]):
> I've seen this over and over and over. Someone joins the list, probably
> because they are having problems (the same reason I joined), posts a
> question
Back in the day, it was prudent and _neccessary_ to do thorough
checking of the forum's archives and lurk before posting, unless you
wore fireproof undies. It's still true to this day, although it seems
that someone is complaining about this most basic Internet truth every
week (day?) on this list.
When you have a problem, subscribing to a mailing list and immediately
posting your question is unwise, as your problem has likely been asked
and answered dozens, if not hundreds, of times.
The vast, VAST majority of questions posted to this list in recent
memory have been asked and answered a bazillion times. Some don't
mind seeing them a bazillion times, most do.
This is Internet 101, but I'm afraid the deluge is starting drown us.
Inane questions are costing us all money. You could argue that it's a
fraction of a penny, but still, for those interested in actually
helping out those who pose good questions, it wastes time and money to
have to wade through those asking about shell syntax. Less noise
would mean UIC's 'net connection would be a little less-stressed, as
well. Alas, I expect trends to continue.
Why is it that all of these people are installing their Redhat CD's
and installing qmail without having the foggiest idea how it all fits
together? Why are they not doing their homework? It's all fine and
dandy for your home playground, but many of these questions are coming
from professionals working with production systems!
So many questions posted here really haven't anything to do with email
or qmail, but rather basic Unix administration fundamentals, which is
decidedly lacking among more and more of the world's Unix
"administrators" these days, it would seem (and not just the low-paid
ones, I'm afraid). Without understanding how your shell works, how to
decipher the syntax of your init scripts? There are many other
examples.
You don't just move from NT to any type of Unix without extensive
research and experience, save for your own home boxes or what not, or
unless you are particularly bright (again, obviously lacking among
many newbie posters here). If you can't do it yourself, then it's
wise to hire someone.
Now, when I installed qmail the first time for a production system, I
was subscribed to the qmail list for awhile already--I knew I HAD to
get rid of sendmaul, and I did my homework! I did it using only Dan's
docs in the qmail tarball! Yes. There was no LWQ. I also learned a
great deal just by reading this list for a month or two. It was PIECE
OF CAKE, especially when one has experience with such monstrosities as
INN--the poor souls having trouble with qmail and posting here would
shoot themselves. Some don't have the luxury of that much time or
experience, granted, but still, there's a limit. Having a firm grasp
of Unix and a little common sense goes a long ways. If you don't have
a firm grasp on Unix, then there are resources out there to help you,
on Usenet, the Web, in printed books, whatever.
The keys to success:
- Read the docs, then read more docs.
- Know the software, your OS, your shell, and basic Unix stuff like
file permissions ("my log says the .qmail file has an x bit set and
program delivery, and qmail won't deliver my mail! how do I fix it??"
how many times have I seen that?!) before you decide to put that new
qmail box in production! Argg. Or hire someone who does.
- Attention to detail.
Heck, there are probably others, but I can't stress the latter enough,
since it's apparent that attention to detail is non-existant for most of
those used to point-and-drool and that ask question on this list.
> On a side note, I've tried to unsubscribe from the list because of exactly
> this kind of crap from self-important jerks who seem to get a charge out of
> kicking people when they are down, but the damn server tells me I'm not
> subscribed so it can't unsubscribe me. Go figure.
Well, again, attention to detail is the key. Your envelope sender
address does not match the address that you were subscribed as, for
whatever reason. Look at this mail's return-path for a clue.
I've said enough. Pretty close to adding a rule for *Outlook* and
*Inernet Mail Service* (heh, "Service!") into my .procmailrc, though,
for mails to this list, with the SNR getting so bad among you all.
Sigh.
Aaron
