pop3 changes

brtmac@ksu.ksu.edu Sat, 04 June 1994 00:21 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14001; 3 Jun 94 20:21 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa13997; 3 Jun 94 20:21 EDT
Received: from PO4.ANDREW.CMU.EDU by CNRI.Reston.VA.US id aa22762; 3 Jun 94 20:21 EDT
Received: (from postman@localhost) by po4.andrew.cmu.edu (8.6.7/8.6.6) id UAA02417; Fri, 3 Jun 1994 20:20:01 -0400
Received: via switchmail for ietf-pop3+@andrew.cmu.edu; Fri, 3 Jun 1994 20:19:59 -0400 (EDT)
Received: from po5.andrew.cmu.edu via qmail ID </afs/andrew.cmu.edu/service/mailqs/q002/QF.UhvwVzC00UddMIlU5P>; Fri, 3 Jun 1994 20:19:12 -0400 (EDT)
Received: from grunt.ksu.ksu.edu (grunt.ksu.ksu.edu [129.130.12.17]) by po5.andrew.cmu.edu (8.6.7/8.6.6) with ESMTP id UAA05298 for <ietf-pop3@andrew.cmu.edu>; Fri, 3 Jun 1994 20:18:54 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: brtmac@ksu.ksu.edu
Received: from mort.ksu.ksu.edu by grunt.ksu.ksu.edu (8.6.8/1.34) id TAA06403; Fri, 3 Jun 1994 19:18:52 -0500
Received: by mort.ksu.ksu.edu (8.6.8/1.34) id AAA02997; Sat, 4 Jun 1994 00:18:38 GMT
Date: Sat, 4 Jun 1994 00:18:38 GMT
Message-Id: <199406040018.AAA02997@mort.ksu.ksu.edu>
To: ietf-pop3@andrew.cmu.edu
Subject: pop3 changes

I'm not a POP user, but I do support a POP3 server and have found what
I see as a very large gap in it's functionality.  Right now, POP3 does
not allow for a POP client to hand it mail to have sent out.  That
means that every single PC, Mac, etc. that runs a POP mail client has
to be configured to know how to send mail, or where to send it so that
it gets routed properly.  It also has to get the headers correct, etc.
It would seem to me that a way for a POP client to hand mail to the POP
server and have it do the trick of getting it delivered would be a much
preferable method.  The server can be configured for what should be in
the headers, and where to actually send the mail to have it delivered.
The only thing the POP client would need to know is where the POP server
is.  Right now POP clients on our campus have to know where the POP server
is, where the mail router machine is, and how to configure the headers.

In case you are wondering, we do not run the POP server on our main
mail router.  The machine that runs the POP server is configured to
accept incoming mail and hand it off to the mail router, but that means
we have to run both the POP server and an SMTP server on that machine,
and it means that POP clients have to know how to speak SMTP to send
mail.

I suppose this is something that would be better suited for POP4, but it
seems like something that should be there.  You normally pick up and send
mail at the postoffice.  Why should that not be the case for POP?

Brett McCoy, UNIX Systems Administrator
Computing and Network Services
Kansas State University,  Manhattan KS  66506
vox: (913) 532-4908 / fax: (913) 532-5914 / e-mail: brtmac@ksu.ksu.edu