After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 220810 - RFE: an "expiration date" for e-mail
RFE: an "expiration date" for e-mail
Status: RESOLVED DUPLICATE of bug 488798
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
unspecified
Other All
: Normal enhancement
: Future
Assigned To: evolution-mail-maintainers
Evolution QA team
: 237590 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-02-21 00:49 UTC by Neil Weisenfeld
Modified: 2012-09-20 13:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Neil Weisenfeld 2002-02-21 00:49:48 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:
This is a feature request.  It would be nice to be able to specify an
"expiration date" for a received e-mail.  There then would be a quick way
of marking all "expired" e-mails as having been deleted.

This is a feature of Outlook that is missed.

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen? 


Additional Information:
Comment 1 Sankar P 2005-08-29 10:28:18 UTC
As per RFC 1036, users are discouraged from providing expiration dates for
messages unless there is a natural expiration date associated with the topic. 
System software should almost never provide a default "Expires" line.  Leave it
out and allow local policies to be used unless there is a good reason not to.

Expiration date setting is higly cohesive with the server and it is already
implemented for GroupWise servers. It can be accessed in "Send Options" for
GroupWise accounts.

Moving to connector, since I dont know if it is implemented for Exchange servers.
Comment 2 Neil Weisenfeld 2005-08-29 13:58:26 UTC
From RFC 1036:

    Since local hosts have local
    policies for expiration of news (depending on available disk space,
    for instance), users are discouraged from providing expiration dates
    for messages unless there is a natural expiration date associated
    with the topic. 

This is for USENET news AND relates to the SENDER, not the reader.  I fail to
see how this has anything to do with a particular mail end-user deciding that
they want a particular message that they've received to have a particular
lifetime.  I frequently receive messages about a talk or event scheduled for a
certain date and want to keep that message until it is no longer relevant.  I
would like to be able to mark those messages, when I receive them, as having an
expiration date and have them automatically deleted.  This would avoid my having
to go back and cull through hundreds of "dead" messages later on.

What has this to do with RFC1036?  I have no idea.  But the whole thing speaks
more to the reason why I switched many years ago AWAY from Evolution and am
loathe to return.

See, I tried to be a good end user and report bugs via bugzilla and,
occasionally, suggest improvements that *I* would like to see, fully
understanding that if no one else was interested, then they would never be
implemented.  For the most part, I've never received a reasonable response, even
when the problem was a flat out bug, rather than a suggestion.

I really wish Novell/Ximian luck with their projects.  Now I have to go as I
have a lot of e-mail to read with Thunderbird.
Comment 3 Sankar P 2005-08-30 07:04:22 UTC
*** Bug 237590 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2012-09-20 13:11:54 UTC
Dup of bug 377352 / bug 488798.

*** This bug has been marked as a duplicate of bug 488798 ***