🚀 go-pugleaf

In <2d2d94ae.5350415449414c@synapse.org> evanc@synapse.org (Evan Champion) writes:

>I'm looking for a working sendmail.cf for SCO.  Specifically, the one that I
>have insists on bungling up addesses to/from uucp systems from internet
>addresses to uucp addresses, usually coming up with something bizarre
>like this:

>        spatial!spatial.synapse.org!evanc@uusynap.synapse.org

>Suffice it to say, not a lot of people are pleased with this kind of thing.  Any
>help would be greatly appreciated.

That's ok, you should see mine...

 On an ODT 2.0 machine, I ran the sendmail setup stuff, and I can send a
receive mail easily enough, but my return address looks like this:

From: icss3!root@icss3.agron.iastate.edu.agron.iastate.edu (Superuser)

 Then on an ODT 3.0 machine, I ran the sendmail setup stuff, and answered
the questions exactly the same, but my return address looks like this:

From: soils!root@soils.agron.iastate.edu (Superuser)

 And I'm not doing UUCP, so why does it look like a psuedo uucp address?

 Well I guess I should feel lucky that I've gotten it to work at all.

 I've got a few more tricks to try.  Maybe if I keep this up, I'll
understand sendmail better than I do now.

Steve
P.S. One thing I have found is that SCO's sed is broken.  But maybe people
already knew that.
-- 
Steve Sheldon           [These are my own opinions]
Iowa State University   ICSS Resource Facility by day
sheldon@iastate.edu     ProMap, Inc. by night

In article <sheldon.757969565@pv141b.vincent.iastate.edu>,
Steve Sheldon <sheldon@iastate.edu> wrote:
>That's ok, you should see mine...
>
> On an ODT 2.0 machine, I ran the sendmail setup stuff, and I can send a
>receive mail easily enough, but my return address looks like this:
>
>From: icss3!root@icss3.agron.iastate.edu.agron.iastate.edu (Superuser)

What version of sendmail are you guys running?  I never have had
problems with my sendmail daemon, but then I've always been running
v8 rather than the stock sendmail that comes with SCO (which was
mildly hosed as I recall).

>Steve
>P.S. One thing I have found is that SCO's sed is broken.  But maybe people
>already knew that.

Knowing that will come in handy should you ever want to install INN...
-- 
Murray S. Kucherawy ==========================================================
Software Support, Network Operations Centre    E-mail: mskucher@nic.hookup.net
HookUp Communication Corp. - Waterloo, Ontario, CANADA        NIC Handle "MSK"

In article <2glabs$8tf@nic.hookup.net>,
Murray S. Kucherawy <mskucher@nic.hookup.net> wrote:
} In article <sheldon.757969565@pv141b.vincent.iastate.edu>,
} Steve Sheldon <sheldon@iastate.edu> wrote:
} >That's ok, you should see mine...
} >
} > On an ODT 2.0 machine, I ran the sendmail setup stuff, and I can send a
} >receive mail easily enough, but my return address looks like this:
} >
} >From: icss3!root@icss3.agron.iastate.edu.agron.iastate.edu (Superuser)
} 
} What version of sendmail are you guys running?  I never have had
} problems with my sendmail daemon, but then I've always been running
} v8 rather than the stock sendmail that comes with SCO (which was
} mildly hosed as I recall).
} 
Mildly hosed?  That statement is mildly inaccurate... SCO sendmail is BIG TIME
hosed :-)

Actually, I dumped SCO's mmdf AND sendmail and went with IDA sendmail.  I can
honestly say I haven't been dissappointed.

DAS
-- 
David Snyder @ Snide Computer Services - Folcroft, PA         Current Release
                                                              is db4glgen-3.17
UUCP:  ..!uunet!das13!dave   INTERNET:  dave@das13.snide.com

In article <sheldon.757969565@pv141b.vincent.iastate.edu> sheldon@iastate.edu (Steve Sheldon) writes:
> Then on an ODT 3.0 machine, I ran the sendmail setup stuff, and answered
>the questions exactly the same, but my return address looks like this:
>
>From: soils!root@soils.agron.iastate.edu (Superuser)
>
> And I'm not doing UUCP, so why does it look like a psuedo uucp address?

Like most evils in the world, this can be blamed on MMDF ;->.  It turns out that
mail(x) still parses /usr/mmdf/mmdftailor even if MMDF is disabled.  To fix
this, edit /usr/mmdf/mmdftailor, and add

	MLDOMAIN agron.iastate.edu 

or whatever domain you want.

This will stop mail from doing this.  I tried just removing mmdftailor, and it
just made things much worse.

A future version of "mkdev cf" will edit mmdftailor automatically.

WRT the general issue of sendmail configuration on SCO, it's kind of tough.
SCO originally attempted to provide for a few common cases (and I've added one
or two more since ODT 3.0, since I now own the cf script), but it's not clear
that there is a "common" case in sendmail configuration.  Any bugs that may
exist in the configuration template just make it worse ;->

Shipping the BSD m4 files is not really an option, since m4 does not ship with
the SCO UNIX run-time, but rather with the development system.  It's also not
clear (at least to me) that a large portion of the customer base would know
what to do with the m4 files either.

I've been working with sendmail on and off since V4.12 and I've never seen a
vendor configuration that was compatible with what we wanted when it came out
of the box.  I've changed "mkdev cf" so that it's better for "dumb node" cases,
but getting a mail-hub configuration right is not trivial, so we don't really
even try.

If you have thoughts on this issue, feel free to send me mail.
-- 
Steve Alexander, Lachman Technology, Inc. | stevea@lachman.com
(708) 505-9555 x256 FAX: (708) 505-9574	  | ...!{sun,ico}!laidbak!stevea