🚀 go-pugleaf

In article <1990Nov22.135312.29693@dircon.uucp> sys0001@dircon.uucp (Ben Knox) writes:
>In my root domain file, I've got an entry:
>
>com:	ukc.ac.uk
>
>In my uucp.chn channel file, I've got:
>
>ukc.ac.uk:	ukc!%s
>ukc.UUCP:	ukc!%s
>
>and in my uucp.dom domain file, I've got:
>
>ukc:	ukc.UUCP
>
>(My neighbouring site is ukc).
>
>If I use 'checkaddr -w abc@com', the address is found OK and the
>Then, if I try: checkaddr -w abc@zzz.com, I get:
>Bad address
>(BHST) Unknown host/domain name in "abc@zzz.com".

I'll bet you're not specifying "flags=route" for your "top" domain table.
This is a feature new in update 43 ...

The way this works -- when submit is searching around for the place to
send the mail & there isn't an exact for the domain name it has in any
of the tables it starts stripping names off the left end of the name.
For "zzz.com" it tries "zzz.com", fails, then tries "com".  Hmm.. don't
remember if this also requires "flags=partial", but it's documented in
the admin guide.

If the name it finds is not a match for the name it has then it
generates a route, like you're expecting.  In this case

	@ukc.ac.uk:user@zzz.com


>I currently do not have a badhosts channel defined. If I do this,
>and set it to 'ukc.ac.uk', then the 'checkaddr -w' message
>gives: asd@zzz.com: queueing for badhosts: via '': 'asd@zzz.com'.
>I'd have thought that the via string should be ukc.ac.uk?

Put "host=ukc.ac.uk" in the MCHN for your badhosts channel.  This
tells the badhosts channel (works for badusers channel too) which
host to send the mail to .. 


-- 
<- David Herron, an MMDF & WIN/MHS guy, <david@twg.com>
<- Formerly: David Herron -- NonResident E-Mail Hack <david@ms.uky.edu>
<-
<- Use the force Wes!