Forgive me, I assumed it was a joke and reacted in kind. I looked to see
if I could find if you were reacting to something, and found nothing, and
then assumed that since you didn't include a seemingly obviously required
encoding method that it must be a quick joke on your part.
As for actually solving the encoding issue, the url format with a data: for
local encoded emojis and the potential for remote reactionary gifs is
interesting,
if we want to go whole hog.
Brandon
On Mon, Sep 14, 2020 at 6:23 PM Dave Crocker <dhc(_at_)dcrocker(_dot_)net>
wrote:
On 9/14/2020 5:41 PM, Brandon Long wrote:
Is this the new April Fools?
Is it restricted to SMTPUTF8 or do you have a preferred encoding
mechanism? How about UTF7?
😟 Forgive me, Brandom. Perhaps it's my age or impairment from smoke
inhalation, but I can't seem to find the constructive content in your
posting to the mailing list. Care to try again?
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
ietf-822 mailing list
ietf-822(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-822