Lists Home |
Date Index |
- From: "Dick Brooks (E)" <firstname.lastname@example.org>
- To: "K.Kawaguchi" <email@example.com>, <firstname.lastname@example.org>, "James Robertson" <email@example.com>
- Date: Tue, 8 Feb 2000 07:13:50 -0600
There are numerous issues related to e-mail based transport of business
documents (X12, XML or other):
“SMTP mail messages can travel unpredictably from Internet hosts.”*
“SMTP providers can only guarantee levels of service from end to end when
the Internet Service Provider owns the entire transmission path.”*
“The sender then has no guarantee that expired messages will not be viewed.”
Lack of Access Controls allows hackers and spammers access to E-C Servers
Many viruses travel by E-mail
Known file size limitations
Known problems with gateways on signed/encrypted messages
No real-time acknowledgement
If you're looking for "business grade" transports look at EDIINT AS2, it's a
HTTP based protocol.
From: firstname.lastname@example.org [mailto:email@example.com]On Behalf Of
Sent: Monday, February 07, 2000 9:18 PM
To: firstname.lastname@example.org; James Robertson
Subject: Re: Asynchronous message queue by SMTP&POP3
> Either way, the e-mail side of things should
> be pretty standard, so I'm not sure what a
> custom component would really do for you ...
Yes, I agree with you that they are standardized. And as you've
mentioned, sending it is especially easy. There is no need of "custom"
Things are basically the same with receiver side. If there exists a good
POP3 component (with source), maybe I don't need a "custom" one, because
I can imagine only few XML-specific functionalities
But the problem is, I still cannot find such a POP3 component. And if
I implement it from the scratch, it could have a better interface by
sticking to the concept of "queue by e-mail".
Is there something wrong with this reasoning?