🚀 go-pugleaf

In article <1993Jan7.222922.4587@prodigy.bc.ca> jchin@prodigy.bc.ca writes:
>In article <1993Jan7.222028.4493@prodigy.bc.ca> jchin@prodigy.bc.ca  
>(Joseph Chin) writes:
>> I've just noticed that since I upgraded to 3.0, I can no 
>> longer send email to accounts within my domain 
>> (prodigy.bc.ca). Is there a bug in the 3.0 sendmail.cf 
>> file? The NeXT is a mail client on the network, and the 
>> mail host is a Sun Sparc server. Everything worked fine 
>> before the 3.0 upgrade. 
>
>I forgot to add that the following was found in the  
>/usr/spool/mqueue/syslog file:
>Jan  7 13:39:25 johnette sendmail[942]: AA00939: to=jchin, delay=00:00:04,  
>stat=Service unavailable, mailer=etherl
>
>Joe
>--
>Joseph Chin				Prodigy Technologies Corp.
>jchin@prodigy.bc.ca (NeXTmail welcome)	Vancouver, British Columbia
>phone 16046874636 / fax 16046871671	Canada
> **** "Heaven won't take me and Hell's afraid I'll take over!" ****

Okay, well we had so much trouble with sendmail and our network that we
ended up almost completely rewriting the rule sets in many cases.

Sendmail is an extremely complicated system and trying to figure out
what is going wrong can be very difficult.  There is however, a
debugging mode: sendmail -bt, this will show you how addresses are being
parsed on your NS and which rule set is being used.

Also, make sure you are using the correct sendmail.cf file, the NeXT
comes shipped with a number of them.

At our site we ended up making our next a mailhost/server before we
finally got things right...  Then we had to modify Rule sets 0,D, and 1
to get addresses to parse right, all in all a nasty job.  The problems
we had:
	(1) a VAX Domain Server running PMDF configured not to understand
		UNIX mail addressing conventions... sigh!
	(2) a dotted machine name, ralph.cs where there is no cs domain,

and through all of this, w still got it to work.		

So good luck, read your manuals carefully, and discover the sendmail
comp newsgroup.

-Erik