Re: POP3 behavior on broken tcp connection

[Steve Dorner <[e-mail]>]

At 4:20 PM 6/3/94, John Gardiner Myers wrote:
>Wonderful observation.  Should we decide to declare that servers not
>enter UPDATE state on a broken connection, and should Eudora use this
>approach, Qualcomm could solve more problems by distributing a server
>that does UIDL than by distributing a server which by default enters
>UPDATE on a broken connection.
>
>Steve?

I am all for UIDL.  My current development version uses a very similar
mechanism (xtnd xlst and the message-id: header) to manage maildrops.  UIDL
would be better than this, and I would welcome it with open arms.  I would
ship a version of Eudora with it in the fall.

As for not entering the UPDATE state on QUIT, after the UIDL Eudora
penetrates widely, we'd probably be willing to change our server to do that
by default.  I would certainly support that position inside Qualcomm,
though I don't have final say.

I have spoken to two POP3 implementors not reading this list (for Novell
and VM/CMS).  They have both indicated that they are quite willing to
support UIDL.

I see UIDL as a big win for everybody, and an awfully good way out of this
whole mess with QUIT and LAST.

Adding UIDL to the spec as an optional command would not disturb any
existing implementations.

I think UIDL might bring peace to Bosnia, democracy to Haiti, and fiscal
responsibility to the US Congress.

--
Steve Dorner, Qualcomm Incorporated
 "There's nothing wrong with you that can't be cured
  with a little Prozac and a polo mallet." - Woody Allen