From: Stephen Satchell <list@fluent2.pyramid.net>
To: Matti Aarnio <matti.aarnio@zmailer.org>, Oliver Feiler <kiza@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: [OT] Re: Mailinglist problems?
Date: Mon, 28 Apr 2003 07:30:15 -0700 [thread overview]
Message-ID: <5.2.0.9.0.20030428070633.01d630a0@fluent2.pyramid.net> (raw)
In-Reply-To: <20030428112434.GH24892@mea-ext.zmailer.org>
At 02:24 PM 4/28/03 +0300, Matti Aarnio wrote:
> Then come various weird things, like overzealous reg-expr message
> content filters, broken MTA configurations (don't people ever
> test that their changes do work ?), etc...
Smaller operators and a number of company Intranets have SysAdmins who
don't have a clue how to test changes in their configuration. They don't
have "outside" accounts, not even ones a Yahoo or other web-mail places, so
they can't evaluate their changes. They also run exactly one mail server
suite, the production servers, and make changes willy-nilly to the live
system without fear of consequences. (Smart mail admins have a test server
and a way of exercising it -- Mail Admin 101.)
So many clueless Mail Admins I've seen have strange letters, like MCSE,
after their name. Also RHCE, I'm sorry to say. (It's amazing how many
people put stock in certification, only to learn that it's no bar to true
twits. Any sorry tech who knows how to take exams can get most of the
first- and second-level certifications with ease. Still sorry admins, but
sorry admins with paper.)
Developers haven't helped much. For example, one feature I loved in
IPCHAINS was the ability to run packets through the software in a testing
mode and see what happened to them. I haven't found a similar function in
IPTABLES yet. From this comment in the IPTABLES man page, it isn't there yet:
>BUGS
> Check is not implemented (yet).
(And some joker removed this from later versions of IPTABLES, but there is
still no "check" option!)
Now, how many MTAs have you encountered that let you "play" mail through
them to see what happens? I've used fetchmail to do the job (inject a
mailstream) on a test system, and that helps quite a bit, but then again I
know about fetchmail because I once had to deal with ConcentricNet (XO) and
wanting to run mail sent to my account there through my spam filters, and I
have quite a corpus of spam mail I have saved just for the purpose.
Getting back to our mutton, until the marketplace requires a certain amount
of USEFUL knowledge in its administrators (something like the NSFnet days)
the things you are talking about will continue to be there.
OK, I'll shut up now.
Satch
--
X -> unknown; Spurt -> drip of water under pressure
Expert -> X-Spurt -> Unknown drip under pressure.
prev parent reply other threads:[~2003-04-28 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 10:23 Oliver Feiler
2003-04-28 11:24 ` Matti Aarnio
2003-04-28 11:35 ` Oliver Feiler
2003-04-28 12:25 ` Maciej Soltysiak
2003-04-28 14:30 ` Stephen Satchell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5.2.0.9.0.20030428070633.01d630a0@fluent2.pyramid.net \
--to=list@fluent2.pyramid.net \
--cc=kiza@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®