RE: [ebxml-cppa] SMTP Needs "to" and "from" e-mail addresses

[Dale Moberg <dmoberg@cyclonecommerce.com>]

Hmmh. If there is a missing "from" address in the
CPA (such as in your case of SMTP one way, and
HTTP back), then the CPA could not be used to
populate that required informational item. 

The "from" element is, of course, a 'sending' 
feature rather than a 'receiving' feature in 
a delivery channel, and the original 
goal had been to focus on defining channels
by receiving characteristics only. This has
not worked out too well, and this could be
another gap.


Currently, the sending software would have to figure out
a way to get this value (from a user wizard, from
an installation value, from a certificate's field, from
an alternative PartyId that happened to have
rfc821 addresses, and so on. Do you think we
should fix this? Where would be a good place
to stick the info? Under the SendingProtocol
element? Someplace better occur to you?

Dale


-----Original Message-----
From: Robert D Kearney [mailto:firefly@us.ibm.com]
Sent: Wednesday, January 02, 2002 3:00 PM
To: ebxml-cppa
Subject: [ebxml-cppa] SMTP Needs "to" and "from" e-mail addresses


The CPP/A document describes an Endpoint element for SMTP containing an
e-mail address (page 38?).  According to the Messaging Specifications,
any
bXML over SMTP requires both "to" and "from" lines in the SMTP header.
It
is not clear from the description that if the sending protocol is SMTP,
that there has to be a "from" e-mail address somewhere in the CPA.  In
fact, if one direction is SMTP and the other is HTTP, I don't see that
there is a place for two e-mail addresses.  Can someone clarify what
happens in this case?

Bob Kearney


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>