[comp.unix.aux] How do I configure mail?

qfhca81@memqa.uucp (Henry Melton) (10/22/90)

I can receive mail from other machines on my AUX2.0 system, but when I attempt
to mail out to some other system (SMTP) the mail remains in limbo for three
days and then comes back to me.  From looking at the headers, the mail never
leaves the machine.  I have tried to get the sendmail.cf file set up, but it
is a puzzling beast.  Is there a handly checklist of things I sould try for
simple SMTP mail?

-- 
Henry Melton  qfhca81@memrqa.sps.mot.com 
{slow}  qfhca81@memqa   ..!cs.utexas.edu!execu!sequoia!memqa!qfhca81
{home}  henry@hutto     ..!emx.utexas.edu!hutto!henry

herbw@midas.WR.TEK.COM (Herb Weiner) (10/25/90)

In article <9189@memqa.uucp> qfhca81@memqa.uucp (Henry Melton) writes:
> I have tried to get the sendmail.cf file set up, but it is a puzzling beast.

I nominate the above for the understatement of the year.

My machine at home is connected to the world using uucp.  (There is no
local area network!)  I can send and receive mail using UUCP style addressing.
I am unable to send email using internet style addressing.  Neither of the
following works:

1.  Mail sent to "myuucpneighbor!user@domain" gets rejected by sendmail on
    my system as an unknown user, even though mail sent to "myuucpneighbor!joe"
    gets through.  Sendmail is refusing to let my uucp neighbor decide how to
    route the mail.  (My uucp neighbor is perfectly capable of handling this
    mail, if only I could get it there.)

2.  Mail sent to "user@domain" is also rejected as an unknown user.  I would
    like sendmail to treat this exactly like case 1 above; that is, send it
    to myuucpneighbor, who will know how to forward it.

Can anybody tell me how to configure sendmail to handle either or both of the
above situations?

Apple: I would think that a significant portion of your A/UX market is people
who use (not necessarily administer) Unix systems at work, and want to set
up a Unix system at home.  Therefore, I recommend that add information on
the above configuration to your manuals, in a form that "the rest of us"
can understand.

Thanks for any assistance that anyone can provide.
Herb Weiner (herbw@midas.wr.tek.com)

wtm@uhura.neoucom.EDU (Bill Mayhew) (10/25/90)

Indeed, sendmail.cf can be a study in frustration, considering the
many OEM versions thereof and the copious (just kidding) amounts of
documentation available.  Seriously, if you know anybody that has
access to an HP-9000 system, read HP's book on network
configuration.  It has a particularly lucid treatise on sendmail.

It is tough being a uucp island and living with sendmail.  It can
be done.  I am running an AT&T 3b1 ('til I get my II si, are you
listening, Santa?) at home and doing just that.  I wanted sendmail
so that I could have reasonably RFC-compliant headers instead of
the meager output from the stock /bin/mail that comes with the
3b1 system.

Basically, what you need to do is to add a(some) line(s) to rule
set 0 to divert all lines that are in domain style to a mailer of
your own definition.  Say, the following added to the bottom of
rule set 0:


# General disposition of remote mail.
R$*<$*.$=T>$*		$1<$2>$4		strip fake domain
R$*<@$->:$+		$#uusmart$@$2$:$1$3	let remote process it
R$*<@$+>$*		$#uusmart$@$2$:$1$3	ditto
R$*<$*>$*		$#error$:Unknown address $1$2$3		barf!


Now, set up a uux command to forward everything that appears to be
non-local:


############################################################
#
#      REMOTE INTERNET SMART-HOST PROCESSING WITH UUCP RELAY
#
############################################################

Muusmart,	P=/usr/bin/uux, F=CDFhMmsu, S=15, R=25,
	A=uux -a$g - $r!rmail ($u@$h)

# Mailer-specific sender rewriting (From:)
S15
R$+			$@$>11$1	

# Mailer-specific recipient rewriting (To:/CC:)
S25
# None needed.


Note that $r is the variable that contains the name of the remote
host.  You should disable local attempts to do nslookups, etc.  I
don't have the A/UX sendmail.cf right here, but it should be easy
to turn that off.  Provided the other end of your connection is a
smart mailer, it should work.  Of coruse, you need to make
arragnements with the administrator on the other end to agree to
handle your mail.

This isn't the prettiest approach, but it does work for me.  I'm an
EE, not a CS person, so I have a bit of an excuse.  I'd love to
hear any better ideas.


==Bill==
-- 
Bill Mayhew      NEOUCOM Computer Services Department
Rootstown, OH  44272-9995  USA    phone: 216-325-2511
wtm@uhura.neoucom.edu   ....!uunet!aablue!neoucom!wtm
via internet: (140.220.001.001)

thad@cup.portal.com (Thad P Floryan) (10/26/90)

wtm@uhura.neoucom.EDU (Bill Mayhew) in
<1990Oct25.030125.12673@uhura.neoucom.EDU> writes some interesting info about
sendmail configuration on his 3B1, and concludes "This isn't the prettiest
approach, but it does work for me.  I'm an EE, not a CS person, so I have a
bit of an excuse.  I'd love to hear any better ideas."

Some other solutions that will work and which I've tested (with multiple 3B1s
and other systems on a network) include some of the following.  Note that
the 3B1s are running HDB, Ethernet, StarLAN, and the latest OS from AT&T
along with the BSD networking stuff I ported to the 3B1.

smail 2.5, both with and without sendmail "handoffs".  Very easy to configure,
and specifying a "smarthost" to handle non-local mail is trivial.  You should
be able to bring this package up within a few minutes after reading its docs.
It also provides replacements for the "stock" mail, etc.  You'd also want the
pathalias up and running.  This all works fine compiled with the stock cc and
with gcc on the 3B1, so I suspect it'd go fine under A/UX with gcc, too.  And
smail gives you the RFC-compliant headers, etc.

(BTW, we finally got GNU "make" 3.58 up on A/UX 2.0 since the standard "make"
couldn't handle the number of targets and dependencies required for my
product; if anyone else is contemplating porting GNU make, there are some
"gotchas" under A/UX 2.0 (hint: do a grep setvbuf :-) and it doesn't work too
well with the stock cc, so use gcc instead).

smail 3.*, and dispose of sendmail entirely.  I'm still "playing" with this
one and will reserve comments until I've read over all the sources and docs.

mmdf, though I haven't done anything with it (yet).  It claims to be the
solution to all the sendmail woes.


Thad Floryan [ thad@cup.portal.com (OR) ..!sun!portal!cup.portal.com!thad ]