OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-cppa message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


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



Dale,

It seems to me that the SMTP "from" address is local deployment information
that is of no use to the other party, so there is no need to put it in the
CPP or CPA. In other words, your alternative "from an installation value"
is the right answer.

I might also note that the SMTP "from" address is not necessarily the same
email address that the party uses for receiving messages (the one that is
in its delivery channel), so the original question is equally valid for
SMTP in both directions.

Regards,
Marty

*************************************************************************************

Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287;  IBM tie line 863-7287
Notes address:  Martin W Sachs/Watson/IBM
Internet address:  mwsachs @ us.ibm.com
*************************************************************************************



Dale Moberg <dmoberg@cyclonecommerce.com> on 01/02/2002 05:14:20 PM

To:    Robert D Kearney/Watson/IBM@IBMUS, ebxml-cppa
       <ebxml-cppa@lists.oasis-open.org>
cc:
Subject:    RE: [ebxml-cppa] SMTP Needs "to" and "from" e-mail addresses



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>

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





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC