[comp.mail.misc] Internet -> ENVOY100 INSTRUCTIONS enclosed

smd@lsuc.on.ca (Sean Doran) (01/10/91)

In an article (Message-Id: <1991Jan9.224506.920@rick.doc.ca>),
andrew@calvin.doc.ca (Andrew Patrick) wrote:

| In article <1991Jan5.031755.15324@bkj386.uucp> anton@analsyn.UUCP
| >OK, so we know how to send to mcimail.
| >How about sending to people who have ENVOY 100 accounts ?

| #F internet
| #T envoy
| #R John Smith (ID=userid)
| #C /C=CA/ADMD=TELECOM.CANADA/ID=ICS.TEST/S=TEST_GROUP/@nasamail.nasa.gov
| #C   for second method only
| #I send to "uunet.uu.net!att!attmail!mhs!envoy!userid"
| #I   or to "/C=CA/ADMD=TELECOM.CANADA/DD.ID=userid/PN=John_Smith/@Sprint.COM"

Ah, this is out of date...  I will let the maintainer know.

I am the person who (with no help from Telecom Canada) tracked down 
and 'discovered' these gateways, much to the detriment of poor Rayan 
Zachariassen who had to put up with bouncing mail from time to time
during my researches.   :)

The contact address is valid (see my .signature), but sprint.com is
no longer forwarding mail beyond the Telemail ADMD, and the attmail
gateway-addressing method is unpredictable at best.  

lsuc!att!attmail!mhs!envoy!ICS.TEST works for me, but is almost guaranteed
not to work for anyone else.  Thus, the #I fields are wrong and should
be changed.

..!uunet!att!attmail!mhs!envoy!ICS.TEST has occasionally worked,
as has ..!{gargoyle,decuac,sun}!att!attmail!mhs!envoy!ICS.TEST.

The ATTMAIL MHS gateway is often too picky, though, and bounces things or
just eats them.

Using envoy to [ID="internet(b)site.baz.dom(b)user" @UUCP]ATTMAIL/US
works reliably ( the "(b)" is the RFC 987 encoding of '!' ), but generates
an unreplyable From: line, which uses some bizarre twisting of
attmail.com.

Mail to envoy using attmail.com, mhs.attmail.com, and
envoy.mhs.attmail.com fail, though ATTMAIL's techies don't know why yet.
Mail to attmail using att.com is embargoed due to a long-standing
agreement between AT&T and DARPA.

| However, numerous tests using this format (and some variations) have
| all resulted in messages like:
| 
| >The following address(es) could not be translated to X.400 ORName(s):
| >  address:   /C=CA/ADMD=TELECOM.CANADA/PN=PHILLIPS/ID=PHILLIPS.D/@sprint.com
| >  reason:  part before '@' not an encoded ORName (illegal attribute)

Correct.  Sprint no longer forwards to Telecom Canada, and also the
PN encoding breaks their gateway unless it is in the format of:
P1.GivenName<dot>P1.SurName, which is causing Alan.Roszkiewicz@Sprint.COM 
no end of trouble.

The second failure reflects the accountants' decision to stop paying for
gatewaying Internet mail to Telecom Canada and other ADMDs abroad.

| >    Reason: unable to transfer
| >    Diagnostic: unrecognized ORName

| I am able to send mail from Envoy to Internet (using the format
| suggested in the Guide), but replying using the From: header results in
| the same messages listed above.

Yes.  The gateway is presently embargoing mail that Sprint has to pay
for.  You pay for outgoing mail from Envoy 100, so there is no problem as
far as Sprint's gatewaying policy is concerned.  Complaints should be
sent in writing to SprintMail if you are a SprintMail customer.  They
aren't very receptive to pleas or arguments from Envoy users.

| So, how does one get mail from Internet to Envoy?

Use this format:

From the Internet, send to:

/C=CANADA/ADMD=TELECOM.CANADA/ID=ICS.TEST/S=TESTGROUP/@nasamail.nasa.gov

Substitute your Envoy ID and SurName as appropriate.

The gateway loosely follows the conventions of RFC-987 wrt addressing.

Reply instructions and the RFC822 header will be included in the inbound
message, along with a contact address for the friendly Nasamail admin.

From Envoy, send a message to: [MAIL @NASA]NASAMAIL/TELEMAIL/US,
with the first line of the Text part being an RFC-822 To: line, a la:

To: smd@lsuc.lsuc.on.ca, andrew@calvin.doc.ca,
	andrew%doccrc.bitnet@cunyvm.cuny.edu


Leave the second line blank.

This gateway is fully functional in both directions, and generates replyable
address on the Internet side.  The only problem I have been told about so far
is the refusal of certain Internet and UUCP MTAs to manage addresses with
slashes in them. 

Feel free to mail me any questions here or on Envoy at ICS.TEST.

| -- 
| Andrew Patrick, Ph.D.       Department of Communications, Ottawa, CANADA
|                andrew@calvin.doc.CA    andrew@doccrc.BITNET

-- 
Sean Doran <smd@lsuc.ON.CA>    Disgruntled anti-GST Young Liberal.
also seand@ziebmef.mef.org     Jeune Liberal qui se fache a cause de la TPS.
and  /C=CANADA/ADMD=TELECOM.CANADA/ID=ICS.TEST/S=TESTGROUP/@nasamail.nasa.gov