> The solution I would like is a subscription process which recognizes
> whether a new subscriber can handle HTML or not and sends HTML-based
> messages out in HTML or plaintext, accordingly. However, I'm not sure that
> current subscription protocols have the ability to do that level of
> discrimination yet.
Seems simple enough. Send a confirmation message in multipart/crud, er,
multipart/alternative format with one confirmation URL in the text part and a
different one in the HTML part, with mailback instructions in the part above
the first MIME.
Regards,
John Levine, [EMAIL PROTECTED], Primary Perpetrator of "The Internet for Dummies",
Information Superhighwayman wanna-be, http://iecc.com/johnl, Sewer Commissioner
Finger for PGP key, f'print = 3A 5B D0 3F D9 A0 6A A4 2D AC 1E 9E A6 36 A3 47
