Re: Internet Draft for flexible proxying of the mail protocols

Dan Wing <dwing@cisco.com> Thu, 28 September 2000 21:26 UTC

Received: from cs.utk.edu (CS.UTK.EDU [128.169.94.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA02669 for <drums-archive@odin.ietf.org>; Thu, 28 Sep 2000 17:26:04 -0400 (EDT)
Received: from localhost (daemon@localhost) by cs.utk.edu with SMTP (cf v2.9s-UTK) id RAA05903; Thu, 28 Sep 2000 17:25:41 -0400 (EDT)
Received: by cs.utk.edu (bulk_mailer v1.13); Thu, 28 Sep 2000 17:25:41 -0400
Received: by cs.utk.edu (cf v2.9s-UTK) id RAA05886; Thu, 28 Sep 2000 17:25:40 -0400 (EDT)
Received: from omega.cisco.com (marvin@localhost) by cs.utk.edu with ESMTP (cf v2.9s-UTK) id RAA05871; Thu, 28 Sep 2000 17:25:38 -0400 (EDT)
Received: from omega.cisco.com (171.69.63.141 -> omega.cisco.com) by cs.utk.edu (smtpshim v1.0); Thu, 28 Sep 2000 17:25:38 -0400
Received: from localhost (localhost [127.0.0.1]) by omega.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id OAA15910; Thu, 28 Sep 2000 14:25:24 -0700 (PDT)
Date: Thu, 28 Sep 2000 14:25:24 -0700 (PDT)
From: Dan Wing <dwing@cisco.com>
To: Lee Thompson <lt@seattlelab.com>
cc: Kumar Gaurav Khanna <gauravkhanna@mailandnews.com>, drums@cs.utk.edu, ietf-smtp@imc.org
Subject: Re: Internet Draft for flexible proxying of the mail protocols
In-Reply-To: <bgc7ts4q0qghd3ns2bskk2g4c3g84sd4v8@4ax.com>
Message-ID: <0009281417010.4039-100000@omega.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
List-Unsubscribe: <mailto:drums-request@cs.utk.edu?Subject=unsubscribe>

On Thu, 28 Sep 2000 14:04 -0700, Lee Thompson wrote:

> > For POP, the protocol is arguably dying in favor of IMAP4.
> 
> Here's your argument :)
> 
> I wouldn't say POP3 is dying.   At least not from where I sit.    Most ISPs
> appear to not want to be message stores for people either.  (Large
> corporations and Universities, I'm sure, love IMAP.)
> 
> 
> My Two Cents anyway

Considering that:

 o IMAP has a proposed standard to do this already (RFC2193)
 o SMTP should probably utilize AUTH to help redirect someone to a
   correct server

it seems the proposal is only really applicable to POP3, then, yes?

If so, how about rewriting it so it only extends POP3.


It would seem most useful, however, to use ACAP and connect to a default
server, say, acap.default.com, and ask it for the SMTP, POP3, IMAP4, LDAP,
IPP, etc. servers that are appropriate for the user.  Confining the
solution to only email solves only about 3/4 of the configuration that
typically has to be done of applications to find servers.

-d