🚀 go-pugleaf

In article <1crbn7INNhq3@taloa.unice.fr> florent@roupie.unice.fr
	(Florent Musso) writes:
>I am managing a Next Network ( release 3 ) with a server which is our mail  
>server, and  20 Stations . I have followed all the instructions to  
>configure the mail and everything seems to work except when i want to send  
>messages to BITNET adresses ( .bitnet). I have checked that there is no  
>trouble with the name server, the problem comes from our configuration.

BITNET isn't a top-level domain, so you can't resolve .bitnet
addresses with DNS.  I suggest turning over outgoing traffic to a
site that's on both BITNET/EARN and Internet, and letting it deal
with getting things delivered.

Define a BITNET forwarder early in sendmail.cf:

# BITNET relay
DBfrmop11.cnusc.fr
  ^^^^^^^^^^^^^^^^
  this is only an example--choose an appropriate
  Internet<->BITNET gateway for your site
  

and break out .bitnet addresses in ruleset 0:

R$*<@$-.bitnet>$*	$#ddn$@$B$:$1<@$2.BITNET>$3	user@node.bitnet

					-=EPS=-