Re: [ebxmlms-develop] mailto problems

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
 <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
 <title></title>
</head>
<body>
ebMail is using this function. One requirement is that we should let
ebMail configure this address, as ebMail is using that "sender" address
for reply purpose. Therefore, ebMail would "receive" from that address
for getting replies. 
 
Therefore, I think we cannot mandate that properties in
msh.properties.xml as the sender address. Instead, I suggest we should
keep the current approach to use from party id by default. If the from
party id does not look valid as an email address, we will use the
default value in that property. Comment? 
 
Regards, -Patrick 
 
 
Mayne, Peter wrote: 
<blockquote type="cite"
 cite="mid...@s-...">
 <meta http-equiv="Content-Type" content="text/html; ">
 <meta name="Generator"
 content="MS Exchange Server version 5.5.2654.45">
 <title>mailto problems</title>
 I've just tried registering a mailto: receiver to
accept incoming messages and run across a couple of problems. 
 In Mail.send(), the from address of the mail
message is set using 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mimeMessage.setFrom(new
InternetAddress(fromPartyId)); 
 This assumes that the frompartyId is a valid
RFC2822 (or whatever InternetAddress accepts) address. However, this is
not necessarily so, which is why we now have UrlFinder, for instance.
 Suppose our business partner (PartyId (ABN)123)
exchanges messages with us(PartyId (ABN)456) over HTTP. We have a URL
mapping so that when we send an ebXML message to (ABN)123, Hermes can
map this to a physical address of&nbsp; <a
 href="http://our.business.partner/msh" target="_blank">http://our.business.partner/msh</a>.
(The physical from address is irrelevant, since HTTP has no such
concept.)
 Now, suppose a message arrives over HTTP from
(ABN)123, and we have a mailto receiver registered for Hermes to pass
it to. The SMTP From address obviously can't be "(ABN)123", nor
obviously can it be "<a href="http://our.business.partner/msh"
 target="_blank">http://our.business.partner/msh</a>". We could have
yet another mapping, but that gets confusing.
 Not having searched the specs yet (so I'm open to
contradiction), I would say that the only sensible thing to do here is
to use a fixed From address for all SMTP messages sent by Hermes, both
to other MSHs and receivers. After all, the SMTP From address is
irrelevant to the MSH, since it looks in the ebXML message to find out
who the sender is.
 The above line should therefore be something like 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mimeMessage.setFrom(new
InternetAddress(PROPERTY_SMTP_SENDER)); 
 where PROPERTY_SMTP_SENDER is obtained from
msh.properties.xml. 
 Comments? 
 The other problem is that the attachment is not
attached in the email. Yesterday I blamed ebmail for this, but it
appears to be something in Hermes. I'll investigate further.
 PJDM 
 -- 
 Peter Mayne 
 Technology Consultant 
 Spherion Technology Solutions 
 Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602 
 T: 61 2 62689727&nbsp; F: 61 2 62689777 
 
 <pre>The information contained in this email and any attachments to it:

(a) may be confidential and if you are not the intended recipient, any interference with, 
use, disclosure or copying of this material is unauthorised and prohibited; and

(b) may contain personal information of the recipient and/or the sender as defined 
under the Privacy Act 1988 (Cth). Consent is hereby given by the recipient(s) to 
collect, hold and use such information and any personal information contained in a 
response to this email, for any reasonable purpose in the ordinary course of 
Spherion's 
business, including forwarding this email internally or disclosing it to a third party. All 
personal information collected by Spherion will be handled in accordance with 
Spherion's Privacy Policy. If you have received this email in error, please notify the 
sender and delete it.

(c) you agree not to employ or arrange employment for any candidate(s) supplied in 
this email and any attachments without first entering into a contractual agreement with 
Spherion. You further agree not to divulge any information contained in this document 
to any person(s) or entities without the express permission of Spherion.

  </pre>
  </font> </blockquote>
</body>
</html>