Re: POP3 highest number accessed

[Steve Dorner <[e-mail]>]

>> I am having trouble understand what I am supposed to do.  If the feature of
>> preserving the ``highest number accessed'' across sessions was nuked because
>> ``no one implemented'' it, that reason is incorrect.  My server, which has
>> been widely distributed, has implemented it since it was written in November
>> 1990.

It is doubly and triply incorrect.  TGV Multinet, MailShare (a MacOS pop3
server) also implement LAST in a state-preserving manner.

As I said previously, LAST is of no interest to me unless it preserves
state.  I have a hard time seeing how a non-preserving LAST is of any value
at all, except as a really slow place to store a global variable.  I
definitely vote for requiring persistence of the LAST value.  If
persistence is deemed too difficult to require, make the command optional.

--
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