Package: emacs
Version: 46.1
Severity: wishlist
Dear Maintainer,
Gnus has only two semi-automated mechanisms to mark messages as
expirable (auto-expire and total-expire). Both approaches require
users to select or read every single message in the group in order to
have all messages set to expire. This imposes too much manual labor
for a group that collects spam, where a user simply wants to glance in
the group summary buffer periodically to scan for false positives,
without having to touch the individual messages.
I propose two solutions:
1) a header that gnus recognizes, which would suggest the expiration
date of a message. Something like "X-requested-exp-date:". This
would serve two purposes:
* procmail could (and should) hold the decision logic for when a
message should expire. Ideally procmail would add a header
like "X-requested-exp-date: 2015-10-16" or
"X-requested-exp-date: +96 hours". Or even just having a
boolean switch without a date.
* an author of a message could request that their message expire,
and a recipient could tell gnus to honor that.
2) rename the current "auto-expire" to "semi-auto-expire", and invent
a real "auto-expire" mechanism that starts an aging clock on all
messages as they arrive (selected or not), based on the group
settings.
-- System Information:
Debian Release: 8.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages emacs depends on:
ii emacs24 24.4+1-5
emacs recommends no packages.
emacs suggests no packages.
-- no debconf information
