Re: POP3 protocol question
Steve Dorner <sdorner@qualcomm.com> Thu, 13 October 1994 03:21 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14463; 12 Oct 94 23:21 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa14459; 12 Oct 94 23:21 EDT
Received: from ANDREW.CMU.EDU by CNRI.Reston.VA.US id aa01516; 12 Oct 94 23:21 EDT
Received: (from postman@localhost) by andrew.cmu.edu (8.6.9/8.6.9) id XAA29889; Wed, 12 Oct 1994 23:16:21 -0400
Received: via switchmail for ietf-pop3+@andrew.cmu.edu; Wed, 12 Oct 1994 23:16:20 -0400 (EDT)
Received: from po3.andrew.cmu.edu via qmail ID </afs/andrew.cmu.edu/service/mailqs/q001/QF.Eib:NL600UdbQJjU5n>; Wed, 12 Oct 1994 23:15:36 -0400 (EDT)
Received: from ux1.cso.uiuc.edu (ux1.cso.uiuc.edu [128.174.5.59]) by po3.andrew.cmu.edu (8.6.9/8.6.9) with SMTP id XAA05550 for <ietf-pop3+@andrew.cmu.edu>; Wed, 12 Oct 1994 23:15:26 -0400
Received: from dorner1.isdn.uiuc.edu by ux1.cso.uiuc.edu with SMTP id AA09001 (5.67b8/IDA-1.5 for <ietf-pop3+@andrew.cmu.edu>); Wed, 12 Oct 1994 22:15:08 -0500
Received: from [192.17.16.12] (dorner3.isdn.uiuc.edu) by dorner1.isdn.uiuc.edu with SMTP id AA00743 (5.67b/IDA-1.5); Wed, 12 Oct 1994 22:16:00 -0500
X-Sender: sdorner@192.17.16.10
Message-Id: <aac254ac1c030001c449@[192.17.16.12]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 12 Oct 1994 22:15:31 -0500
To: ietf-pop3+@andrew.cmu.edu
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Steve Dorner <sdorner@qualcomm.com>
Subject: Re: POP3 protocol question
At 9:01 PM 10/12/94, Mark Crispin wrote: >Uh, excuse me. The message header does not contain the correct list of >recipients of the message except in the most trivial cases. It absolutely >does not in blind copies or groups. XTND XMIT gets around the bcc thing by reading and then deleting the bcc: header. >c-client's SMTP code is less than 150 lines. Depends on how you look at it. If it weren't for SMTP, a simple POP client could dispense with RFC 822 address parsing, which is probably a bit more than 150 lines (I know my parser certainly is) even excluding comments and copyright notices. >Anyone who finds SMTP daunting is likely to find it even more daunting to >implement RFC-822 and MIME correctly. RFC 822 is really no big deal, *except* for the address parsing rules, which are pretty bad. Eliminate SMTP, and you eliminate much or all of the need for parsing addresses. MIME is yucky no matter how you slice it. Of course, *all* of this pales in the face of doing a GUI, which so many of us want to do nowadays. Perhaps unlike Mark and Chris, I sympathize with the folks who want posting in POP. But, like Mark and Chris, I don't agree. -- Steve Dorner, Qualcomm Incorporated Whosoever has lived long enough to find out what life is, knows how deep a debt of gratitude we owe to Adam. He brought death into this world. Mark Twain
- POP3 protocol question Jerome Chan
- Re: POP3 protocol question Chris Newman
- Re: POP3 protocol question Steve Dorner
- Re: POP3 protocol question brtmac
- Re: POP3 protocol question Michael D'Errico
- Re: POP3 protocol question Jerome Chan
- Re: POP3 protocol question Steve Dorner
- Re: POP3 protocol question Chris Newman
- Re: POP3 protocol question brtmac
- Re: POP3 protocol question Steve Dorner
- Re: POP3 protocol question Mark Crispin
- Re: POP3 protocol question Steve Dorner
- Re: POP3 protocol question John Gardiner Myers
- Re: POP3 protocol question Ned Freed