Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!cbosgd!ihnp4!zehntel!hplabs!hao!seismo!umcp-cs!zben
From: zben@umcp-cs.UUCP (Ben Cranston)
Newsgroups: net.mail
Subject: InterNet <-> BitNet mail forwarding/header munging
Message-ID: <82@umcp-cs.UUCP>
Date: Sun, 23-Sep-84 07:28:54 EDT
Article-I.D.: umcp-cs.82
Posted: Sun Sep 23 07:28:54 1984
Date-Received: Wed, 26-Sep-84 05:32:54 EDT
Distribution: net
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 24

Am trying to do the above, and am trying to figure out how to munge addresses
and how to handle the implicit conflict between the InterNet (SMTP) concept
of out-of-band from and destination addresses and the BitNet use of the 
actual text of the header for this information.

The worst case is InterNet -> BitNet forwarding.  I am presented with both the
out-of-band send information (from the MAIL FROM and RCPT TO commands) and the
existing message header, and must formulate a new header containing the correct
information so BitNet mailers can handle it.  In general, the out-of-band
information has had site names concatenated onto the FROM address and stripped
from the TO address(es), but the information in the header will not, in
general, have been so updated by the SMTP mechanisms.

I have read RFCs 821, 822, and 886.  Can anybody suggest further reading and/or
knowledgable names for me to contact?

adTHANKSvance

Ben Cranston
POSTMASTER@UMD2.ARPA
POSTMASTER@UMD2.BITNET
...umcp-cs!zben
-- 
Ben Cranston   ...seismo!umcp-cs!zben      zben@umd2.ARPA