* [9fans] Attached "noname" file
@ 2006-10-06 1:25 Joel Salomon
2006-10-06 7:12 ` csant
0 siblings, 1 reply; 5+ messages in thread
From: Joel Salomon @ 2006-10-06 1:25 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
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?
--Joel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9fans] Attached "noname" file
2006-10-06 1:25 [9fans] Attached "noname" file Joel Salomon
@ 2006-10-06 7:12 ` csant
2006-10-06 7:34 ` Skip Tavakkolian
0 siblings, 1 reply; 5+ messages in thread
From: csant @ 2006-10-06 7:12 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
> 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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9fans] Attached "noname" file
2006-10-06 7:12 ` csant
@ 2006-10-06 7:34 ` Skip Tavakkolian
2006-10-06 10:04 ` erik quanstrom
2006-10-06 15:38 ` Russ Cox
0 siblings, 2 replies; 5+ messages in thread
From: Skip Tavakkolian @ 2006-10-06 7:34 UTC (permalink / raw)
To: csant, 9fans
it's in marshal.
cpu% grep -n Content-Disposition /sys/src/cmd/upas/*/*.c | grep ainline
/sys/src/cmd/upas/marshal/marshal.c:389: Bprint(&out, "Content-Disposition: ainline\n");
/sys/src/cmd/upas/marshal/marshal.c:690: Bprint(out, "Content-Disposition: ainline\n");
> 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?
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2006-10-06 15:38 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-10-06 1:25 [9fans] Attached "noname" file Joel Salomon
2006-10-06 7:12 ` csant
2006-10-06 7:34 ` Skip Tavakkolian
2006-10-06 10:04 ` erik quanstrom
2006-10-06 15:38 ` Russ Cox
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).