Re: LMOS

At 10:37 AM -0800 3/13/98, Laurence Lundblade wrote:

>I'm having trouble designing sensible UI for the three values for new,
>top'd and retr'd.  While it's likely that new and top'd will have the same
>value, you still have to design sensible UI for when they're not.  So about
>about LMOS-fully-fetched, and LMOS-not-fully-fetched?  Then require new and
>top'd messages to be considered as not-fully-fetched.

But a TOPped message might really be fully-fetched.  At RFC 1939 warns,
if a server is implementing some form of message expiration, users
might start using TOP in lieu of of RETR as a way around the policy.
As a result, some sites might have a policy that treats TOP and RETR as
"seen".

The current draft recommends that there be only two categories of
messages, and allows TOP to be placed in either.  We could make this a
SHOULD.