[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [OT] base64 messages

To: or-talk@xxxxxxxxxxxxx
Subject: Re: [OT] base64 messages
From: Drake Wilson <drake@xxxxxxxxxxxx>
Date: Mon, 21 Jul 2008 23:56:52 -0500
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Tue, 22 Jul 2008 00:57:01 -0400
In-reply-to: <200807220449.m6M4nGdv017413@xxxxxxxxxxxxx>
Mail-followup-to: or-talk@xxxxxxxxxxxxx
References: <200807220449.m6M4nGdv017413@xxxxxxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)

Quoth Scott Bennett <bennett@xxxxxxxxxx>, on 2008-07-21 23:49:16 -0500:
> >PiBUb3IgaXNuJ3QgdGhlIHJpZ2h0IHBsYWNlIHRvIGJlIG1hbmdsaW5nIGFwcGxpY2F0aW9uIHBy
>
>      Is there some good reason for posting crap like the above to this list?

That would be << Content-Transfer-Encoding: base64 >> in action.  This
is kind of interesting, though off-topic; is GMail starting to send
these out consistently?  I've only mostly seen it used for S/MIME.

   ---> Drake Wilson

Follow-Ups:
- Re: [OT] base64 messages
  - From: Tomás Arribas

References:
- Re: browser footprint
  - From: Scott Bennett

Prev by Author: Re: browser footprint
Next by Author: Circuit question
Previous by thread: Re: browser footprint
Next by thread: Re: [OT] base64 messages
Index(es):
- Author
- Thread