Xref: utzoo comp.mail.mh:1178 comp.mail.sendmail:2294
Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!nuug!ifi!obh
From: obh@ifi.uio.no (Ole Bj|rn Hessen)
Newsgroups: comp.mail.mh,comp.mail.sendmail
Subject: Re: decnet mail addressing and MH
Keywords: decnet addresses MH
Message-ID: <1990Oct22.235952.4324@ifi.uio.no>
Date: 22 Oct 90 23:59:52 GMT
References: <329@puma.ge.com> <1990Oct18.220124.7784@cs.utk.edu> <1990Oct21.103233.7518@idt.unit.no> <1990Oct22.011036.3679@cs.utk.edu>
Sender: obh@ifi.uio.no (Ole Bj|rn Hessen)
Reply-To: obh@ifi.uio.no (Ole Bj|rn Hessen)
Organization: Dept. of Informatics, University in Oslo, Norway
Lines: 29


In article <1990Oct22.011036.3679@cs.utk.edu>, moore@betelgeuse.cs.utk.edu (Keith Moore) writes:

> For instance, for our local configuration, I wanted to translate
> inbound mail-11 From: lines of the form NODE::BITNET%"USER@XYZZY"
> into USER@XYZZY.BITNET, but there was no way to get sendmail to
> "break open" the quoted string without modifying C code.

True. Include a patch from Paul Vixie's sendmail in your favourite 
sendmail and there you fly.

There is no way you can create a ruleset 3 that handle both DECnet 
addresses and RFC822 addresses (and still get a good night of sleep :-). 

Maintainance:

The clue is to rewrite special-type addresses to RFC822 format and 
then pass it on to the more complex sendmail.cf file. That reduces
maintainance to *very* simple sendmail.cf-files and a more complex 
sendmail.cf file that know how to do RFC 822 and routing.

You get simplicity where you need it; and complexity in one central 
place, reduced to the level of understanding.

I haven't pondered on my sendmail.cf files in months.

> Keith Moore

Ole Bjorn