[Top] [All Lists]

Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15

2008-07-23 04:37:02

In <4885DDEF(_dot_)1020404(_at_)network-heretics(_dot_)com> Keith Moore 
<moore(_at_)network-heretics(_dot_)com> writes:

here's my question - what should _really_ happen when a message "expires"?

I keep most incoming messages for archival purposes.  So I wouldn't want 
my message store to delete them on my behalf - certainly not without my 
explicit consent.  What is "pointless" to you might not be pointless to 
me - even an announcement about a talk that happened before I got the 
announcement is useful information to me - it tells me that the talk 
happened, and there might be a video of it on youtube.

I think the most any standard would say is that agents MAY consign that
message to the bit bucket after that date.

But, traditionally, we do not prescribe the inner workings of MUAs (though
we might drop hints as to the *intended* use of some feature). One would
hope that implementation of that "MAY" would be a configurable option in
any decent MUA (but has anyine ever seen a "decent" MUA :-( ).

Of more interest is whether any standard introducing this header should
also try to update the IMAP and POP3 standards by defining circumstances
where such messages could be dropped (but, again, some user configuration
would have to be built in - but then user configuration is already a
feature of IMAP).

Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133   Web:
Email: chl(_at_)clerew(_dot_)man(_dot_)ac(_dot_)uk      Snail: 5 Clerewood Ave, 
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5

<Prev in Thread] Current Thread [Next in Thread>