In <200405252146(_dot_)i4PLkcl9052643(_at_)m5p(_dot_)com>
george(_at_)m5p(_dot_)com writes:
SPF_0x1b <SPF(_at_)0x1b(_dot_)com> wrote:
[...] XML isn't all that bad ;) [...]
For me, it's a deal breaker. Hardware vendors will love the idea of
XML getting pulled into the everyday processing of the internet, but
the people who have to buy the hardware will be less thrilled. Using
XML to express email processing policies is like using a sledge
hammer to exterminate cockroaches.
Ditto here. I'm not willing to add a full XML parser to my mail server
(which is NOT Windoze, Mac, or Unix based) JUST for this one feature;
a feature I DO very much want to implement.
It seems the XML abomination is being brought to us by the same folks that
turned a simple "hi mom" email from ~500 bytes into about 5,000 bytes, and
are responsible for most of the joe-job/virus deliveries sent as intentional
bounces, since their email servers were notorious for accepting ANY garbage
recipient AND senders, then later emailing the (forged) sender a non-standard
undeliverable notice, usually complete with virus payload. :-(
Just say "no" to XML! ;-)
-Chris Bartram
3k Associates, Inc.