Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@justresearch.com>
Subject: Unintended base64 encoding
Date: 11 Jun 1999 14:46:42 -0400	[thread overview]
Message-ID: <vxk1zfi7ey5.fsf_-_@beaver.jprc.com> (raw)
In-Reply-To: Karl Kleinpaste's message of "11 Jun 1999 14:40:26 -0400"

Karl Kleinpaste <karl@justresearch.com> writes:
> --=-=-=
> Content-Type: message/rfc-822
> Content-Disposition: inline; filename=24514
> Content-Transfer-Encoding: base64
> Content-Description: X-Face display patch
> 
> WC1Gcm9tLUxpbmU6IG93bmVyLWRpbmdAaHBjLnVoLmVkdSAgV2VkIE1heSAxMiAxMjoyNTo0
> NCAxOTk5ClJldHVybi1QYXRoOiA8b3duZXItZGluZ0BocGMudWguZWR1PgpSZWNlaXZlZDog

Why did p0.84 decide to do that to me?  I composed the message with
`C-c C-a', specified message/rfc-822, and manually tweaked the
disposition to "inline".  The forwarded message itself was text/plain
and us-ascii.

Duh?  I'm confused.


  reply	other threads:[~1999-06-11 18:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-11 18:36 X-face display patch Hrvoje Niksic
1999-06-11 18:40 ` Karl Kleinpaste
1999-06-11 18:46   ` Karl Kleinpaste [this message]
1999-06-13  1:17     ` Unintended base64 encoding Lars Magne Ingebrigtsen
1999-06-13  2:38       ` Karl Kleinpaste
1999-06-15 11:41       ` Toby Speight
1999-07-03  9:17         ` Lars Magne Ingebrigtsen
1999-07-09 11:55           ` Toby Speight
1999-07-09 18:09             ` Lars Magne Ingebrigtsen
1999-07-09 18:44               ` François Pinard
1999-07-09 19:18                 ` Lars Magne Ingebrigtsen
1999-07-09 19:43               ` Aaron M. Ucko
1999-07-09 20:01                 ` François Pinard
     [not found]               ` <udl4sjdbodp.fsf@tux.mit.edu>
1999-07-09 20:00                 ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vxk1zfi7ey5.fsf_-_@beaver.jprc.com \
    --to=karl@justresearch.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).