Ben Finney writes:
> David Bolen writes:
>
>> Individual messages could include an Expires: header if they wished,
>
> Since we're already well off-topic: NNTP, HTTP, and email, and probably
> other protocols as well, all deal with messages. They are all consistent
> in defining a message [0] as
David Bolen writes:
> Individual messages could include an Expires: header if they wished,
Since we're already well off-topic: NNTP, HTTP, and email, and probably
other protocols as well, all deal with messages. They are all consistent
in defining a message [0] as having *exactly one* header.
E
Dennis Lee Bieber writes:
> Either way -- it was still a change from "expiration at some
> date"... Though since (Netcom/Mindspring)Earthlink seems to have
> subcontracted NNTP service to Giganews (or some such) it wouldn't
> surprise me to learn that service also keeps a mammoth archive...
In article ,
Dennis Lee Bieber wrote:
>
> As for the use of X-Noarchive headers... Back before Google, most
>NNTP servers had automatic expiration of messages (on my ISP at the
>time, the binary groups expired after 24 hours!, most messages expired
>after one or two weeks). I never used X-N
