Re: Wanted:MAIL.MAI structure definition

Dave Froble wrote:
Hoff Hoffman wrote:
I have to assume that there is a lack of familiarity with XML here.

Again, possibly so, but I can envision some designs that could 'learn' about previously unknown types of data and make some reasonable guesses for adding such without need for re-programming. Definitely not a 100% solution, but could handle minor variations.

XML offers a block quote mechanism, allowing a translation tool to convert the incoming RFC-compliant SMTP headers into recognized and structured XML, and into what amounts to quoted headers for the odd stuff. When regurgitating the message, the block quotes can be replayed into the data stream. Or the incoming traffic detects the pieces of the header of interest, and block quotes the whole SMTP header for posterity. Much like how existing mailers handle this stuff.

If SMTP can do "it", then an XML translation can be implemented for "it", too.


Remember, those things that 'cannot be done' remain so only until the first time they are 'done'.

Ayup. That's part of the fun of working in a development group, too.

.