From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: acme mail
Date: Mon, 20 Feb 2006 16:29:01 +0000 [thread overview]
Message-ID: <c49bcff7ad0f7071cc5ebba350f4f89b@swtch.com> (raw)
In-Reply-To: <75a40fbd082e325150a743aa7bc36070@quanstro.net>
> s/mime and pgp email dislike it when the body is changed.
> this isn't something i've used extensively so i don't know how
> much of a problem this might be.
>
> would it be better of the raw file remained an exact
> representation of the original mail?
there is a difference between the in-memory representation
and the representation presented by the "raw" file.
i agree - the raw file should present the raw message bytes,
with no indenting of from lines. however, the internal
representation used by upas/fs does indent from lines,
and the pop3 and imap4 code in upas/fs needs to convert
the downloaded messages into that representation for
consistency with the rest of the system.
and upas/fs needs to process that representation to present
the "raw" file.
this is exactly what i said two or three messages ago.
russ
next prev parent reply other threads:[~2006-02-20 16:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 21:22 quanstro
2006-02-20 16:29 ` Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-20 23:30 quanstro
2006-02-20 18:15 quanstro
2006-02-20 14:18 ` Russ Cox
2006-02-20 19:43 ` uriel
2006-02-20 14:51 ` Russ Cox
2006-02-20 20:44 ` "Nils O. Selåsdal"
2006-02-20 20:49 ` Richard Miller
2006-02-20 16:00 ` Russ Cox
2006-02-20 21:03 ` Richard Miller
2006-02-20 17:29 quanstro
2006-02-20 18:09 ` C H Forsyth
2006-02-20 17:13 Brian L.Stuart
2006-02-20 17:15 ` Richard Miller
2006-02-20 12:21 ` Russ Cox
2006-02-20 17:03 Brian L.Stuart
2006-02-20 12:20 ` Russ Cox
2006-02-20 17:07 ` C H Forsyth
2006-02-20 15:56 [Fwd: [Fwd: Re: [9fans] acme + mh]] Ronald G Minnich
2006-02-20 11:51 ` [9fans] Re: acme mail Russ Cox
2006-02-20 23:19 ` Ronald G Minnich
2006-02-20 23:37 ` David Leimbach
2006-02-21 0:22 ` Dan Cross
2006-02-21 0:30 ` George Michaelson
2006-02-21 0:33 ` Steve Simon
2006-02-21 9:41 ` Charles Forsyth
2006-02-21 21:42 ` Dan Cross
2006-02-21 21:54 ` Skip Tavakkolian
2006-02-21 0:39 ` geoff
2006-02-20 19:42 ` 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=c49bcff7ad0f7071cc5ebba350f4f89b@swtch.com \
--to=rsc@swtch.com \
--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).