Mime-Version: |
1.0 |
Content-Type: |
text/plain; charset=us-ascii |
Date: |
Tue, 13 Jan 2004 08:29:03 -0600 |
Content-Disposition: |
inline |
Reply-To: |
|
Subject: |
|
From: |
|
In-Reply-To: |
|
Sender: |
|
Parts/Attachments: |
|
|
On Tue, Jan 13, 2004 at 08:36:19AM -0500, A. Harry Williams wrote:
>
> Well, using your logic, maybe you shouldn't be doing this job then
> since you don't understand what's going on. Don't like the gratuitous
> snipe? Maybe you shouldn't do it either before trying to understand the
> situation.
Ben is the one that said LISTSERV is simple-minded so those
were his words repeated and not my own. LISTSERV has done
a fabulous job for me except for a few minor nits.
> The common UNIX MTAs have default settings for default usages.
> Guess what! Running LISTSERV isn't a default usage. It's a special
> case usage. Guess what! That means using special case settings
> on programs. Oh my, oh my. What's a person to do? Other than
> reading the documentation, FAQs and trying to understand what is
> going on and adjust to the new situation.
I only asked this list because none of those sources provided
any answers.
> LISTSERV has a task to do, and it trys to do it well, and let
> other processes handle their tasks. Being an MTA isn't one of
> LISTSERV's jobs.
... and that's exactly what I'm trying to let it do. I want
LISTSERV to let my MTA do its job. I figured the knob was in
LISTSERV to allow that. Now that I have a hint at what I need
to make my MTA do what LISTSERV wants I have a better idea of
what to look for.
Thanks.
-steve
|
|
|