From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pop3 before smtp
Date: Thu, 10 Jul 2003 19:56:43 -0400 [thread overview]
Message-ID: <c8c2a4af1278f7e5a9f91a14da24af13@plan9.bell-labs.com> (raw)
In-Reply-To: <01a101c3473d$c48a9720$b9844051@insultant.net>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
Actually, compared to most of the standards out there, I find mime
refreshingly simple. It actually solves a problem, albeit
with more mechanism than I would like. I don't want to go back
to the old days of n different ways to encode cruft into a
mail message. I also find it quite easy to present the mime
encoding as a pretty simple hierarchical file system. I don't
really need anything to replace MIME since the only thing I'ld
be getting is a bit more simplicity and little else.
If I were to throw stones at anything it would be ASN.1.
[-- Attachment #2: Type: message/rfc822, Size: 2499 bytes --]
From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] pop3 before smtp
Date: Fri, 11 Jul 2003 01:48:30 +0200
Message-ID: <01a101c3473d$c48a9720$b9844051@insultant.net>
> I doubt that the 7-bit channel was due to the IMPs; FTP can use all 8
> bits.
yeah, i guess it was 7 bit control and with FTP 8 bit data.
but all this is ancient history. we gotta replace all that stuff.
although i don't see it happening soon :(
hell, they can bearly keep up even with the 'army of programmers'.
next prev parent reply other threads:[~2003-07-10 23:56 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-07 12:05 [9fans] verifying CD vs. iso image pac
2003-07-07 13:39 ` [9fans] pop3 before smtp Kenji Arisawa
2003-07-09 0:49 ` Lyndon Nerenberg
2003-07-09 1:16 ` boyd, rounin
2003-07-09 1:24 ` Dan Cross
2003-07-09 1:58 ` boyd, rounin
2003-07-09 1:36 ` Scott Schwartz
2003-07-09 1:54 ` boyd, rounin
2003-07-09 5:05 ` Kenji Arisawa
2003-07-09 7:21 ` Fco.J.Ballesteros, nemo
2003-07-09 7:39 ` Kenji Arisawa
2003-07-09 7:56 ` Geoff Collyer
2003-07-09 8:29 ` Kenji Arisawa
2003-07-09 9:07 ` Kenji Arisawa
2003-07-10 4:02 ` Russ Cox
2003-07-10 19:18 ` Lyndon Nerenberg
2003-07-10 19:24 ` David Presotto
2003-07-10 19:38 ` David Presotto
2003-07-10 19:49 ` boyd, rounin
2003-07-10 20:09 ` William Ahern
2003-07-10 21:21 ` Scott Schwartz
2003-07-10 21:50 ` Dan Cross
2003-07-10 21:56 ` boyd, rounin
2003-07-11 0:02 ` David Presotto
2003-07-11 0:09 ` boyd, rounin
2003-07-11 0:23 ` David Presotto
2003-07-11 15:03 ` William Ahern
2003-07-11 15:16 ` Martin Harriss
2003-07-11 15:59 ` William Ahern
2003-07-12 0:51 ` Bruce Ellis
2003-07-11 10:44 ` matt
2003-07-11 14:46 ` William Ahern
2003-07-12 23:58 ` C H Forsyth
2003-07-11 8:52 ` bs
2003-07-11 9:18 ` boyd, rounin
2003-07-10 19:51 ` Lyndon Nerenberg
2003-07-10 20:01 ` boyd, rounin
2003-07-10 20:20 ` Lyndon Nerenberg
2003-07-10 19:33 ` George Michaelson
2003-07-10 19:44 ` Lyndon Nerenberg
2003-07-10 22:02 ` Geoff Collyer
2003-07-10 22:14 ` boyd, rounin
2003-07-10 23:11 ` Geoff Collyer
2003-07-10 23:26 ` boyd, rounin
2003-07-10 23:38 ` Geoff Collyer
2003-07-10 23:48 ` boyd, rounin
2003-07-10 23:56 ` David Presotto [this message]
2003-07-11 0:03 ` boyd, rounin
2003-07-10 22:23 ` Lyndon Nerenberg
2003-07-07 16:58 ` [9fans] verifying CD vs. iso image David Presotto
2003-07-07 20:46 ` boyd, rounin
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=c8c2a4af1278f7e5a9f91a14da24af13@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--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).