From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Fri,  6 Oct 2006 09:12:52 +0200
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Attached "noname" file
From: csant <csant@csant.info>
Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8
MIME-Version: 1.0
References: <7871fcf50610051825o3478988bwd8a47bfb8f92673a@mail.gmail.com>
Content-Transfer-Encoding: 7bit
Message-ID: <op.tgznnqt8d84skq@fiore.malebolge>
In-Reply-To: <7871fcf50610051825o3478988bwd8a47bfb8f92673a@mail.gmail.com>
User-Agent: Opera Mail/9.03 (Linux)
Topicbox-Message-UUID: c6a2293e-ead1-11e9-9d60-3106f5b1d025

> I've seen this when sending mail from Acme mail to my Gmail account:
> if I attach a text file, the message text doesn't appear in the
> message body but in an attachment called "noname"; the other
> attachment appears under its own name.
>
> Skip's "C99 and you" also had that property under Gmail, though I
> could read it properly in Acme.  Is this Gmail or Acme Mail not
> implementing an RFC properly?

It's the
	Content-Disposition: ainline
that breaks it, since this is an unknown Content-Disposition. I have  
noticed it already several times, and kept meaning to ask about it. The  
correct value should be
	Content-Disposition: inline
How come several people do have this error? Is it a bug in acme?

/c