9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: csant <csant@csant.info>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Attached "noname" file
Date: Fri,  6 Oct 2006 09:12:52 +0200	[thread overview]
Message-ID: <op.tgznnqt8d84skq@fiore.malebolge> (raw)
In-Reply-To: <7871fcf50610051825o3478988bwd8a47bfb8f92673a@mail.gmail.com>

> 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


  reply	other threads:[~2006-10-06  7:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06  1:25 Joel Salomon
2006-10-06  7:12 ` csant [this message]
2006-10-06  7:34   ` Skip Tavakkolian
2006-10-06 10:04     ` erik quanstrom
2006-10-06 15:38     ` Russ Cox

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=op.tgznnqt8d84skq@fiore.malebolge \
    --to=csant@csant.info \
    --cc=9fans@cse.psu.edu \
    /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).