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

On Tue, 2008-07-22 at 13:25 -0400, Hector Santos wrote:
> Michael,
> 
> Many backend systems have their own email policies.   What you are 
> describing seem to be more preferences or hints, which is good. 

Indeed it's just a preference / hint. Welcome onboard the
already full "it should only be advisory" boat (the other
boat is entirely empty, btw   :-)    ).

 
> End-users can use them (2822 expiration header) with their MUAs.  
> Backends can use them too.

Right... thanks for the details you give in the rest of your
email, I totally agree that these things could be handled
(and should be possible to handle) in backend systems, and
we'll try to make sure that the spec doesn't implicitly
state something against doing this.

[snip]

> In the end, redesigns may include the need for internal mail flags to 
> provide full tracing of how mail was "picked up" or requested 
> (regardless if it was read or not).   An unreceived expired message 
> still needs to be recorded.

Right

cheers,
Michael