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 244791 - Support for Mail-Followup-To header
Support for Mail-Followup-To header
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal enhancement
: Future
Assigned To: evolution-mail-maintainers
Evolution QA team
: 754733 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-06-14 09:43 UTC by Adam Warner
Modified: 2021-05-19 13:23 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Adam Warner 2003-06-14 09:43:28 UTC
Please consider supporting the Mail-Followup-To header as discussed here:
<http://cr.yp.to/proto/replyto.html>

This header is used by people who don't wish to receive duplicate mail, and
Evolution's lack of support for this header would help stop follow-up mistakes.

As a friendly reminder Branden Robinson of the Debian project expresses it
this way via a form letter:

"Many people, myself included, use the Mail-Followup-To message
header, which is honored by mail user agents such as Mutt to control the
distribution of replies to mailing lists; using such a header, a person can
easily indicate that he does (or does not) want to be send copies of
replies to his message.  You may want to use an MUA that honors this
header, as it is in fairly wide usage on the Debian mailing lists, and may
help you avoid mistakes resulting in inadvertent violations of Debian's
Mailing List Code of Conduct."

Thanks,
Adam
Comment 1 Adam Warner 2003-06-14 09:47:48 UTC
Clearly the second paragraph should have read: This header is used by
people who don't wish to receive duplicate mail, and Evolution's
support for this header would help stop follow-up mistakes.
Comment 2 Jeffrey Stedfast 2003-06-14 21:02:50 UTC
this ietf drums draft standard expired in 1998.
Comment 3 bernie 2010-07-04 16:39:01 UTC
There's no way we could get this header supported in Evolution, at least on the receiving side?

Many modern MUAs *do* support it: http://www.leptonite.org/mft/software.html

(GMail is not listed in this table, but it supports Mail-Followup-to as well)
Comment 4 Yves-Alexis Perez 2011-02-24 07:43:26 UTC
Why exactly was this bug marked as “not a bug”? It might be an enhancement request but it's definitely not resolved.
Comment 5 Andres Gomez 2015-09-08 16:49:33 UTC
Check bug 754733.
Comment 6 Michael Catanzaro 2015-09-08 18:13:27 UTC
(In reply to Yves-Alexis Perez from comment #4)
> Why exactly was this bug marked as “not a bug”? It might be an enhancement
> request but it's definitely not resolved.

It was closed because "this ietf drums draft standard expired in 1998."

But, I will reopen to request that the current maintainers review whether it is desirable to support nowadays.
Comment 7 Michael Catanzaro 2015-09-08 18:13:39 UTC
*** Bug 754733 has been marked as a duplicate of this bug. ***
Comment 8 Josh Triplett 2016-06-06 01:39:04 UTC
I'm interested in support for this as well; this isn't just a usability issue for Evolution, but for other people interacting with Evolution users via mailing lists.

Note that there are two issues here: respecting Mail-Followup-To when replying to mail, and making it possible to set Mail-Followup-To.  The former is more important; the latter would be nice but should not block implementation of the former.
Comment 9 André Klapper 2021-05-19 11:45:50 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. 
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org (resources are unfortunately quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
and create a new enhancement request ticket at
  https://gitlab.gnome.org/GNOME/evolution/-/issues/

Thank you for your understanding and your help.
Comment 10 Andres Gomez 2021-05-19 12:04:14 UTC
(In reply to André Klapper from comment #9)

> If you can still reproduce the situation described in this ticket in a recent
> and supported software version, then please follow
>   https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines

The proper link seems to be:
https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
Comment 11 Andres Gomez 2021-05-19 12:09:52 UTC
This is still interesting for me. Created a new issue at: 
  - https://gitlab.gnome.org/GNOME/evolution/-/issues/1493
Comment 12 Michael Catanzaro 2021-05-19 13:23:05 UTC
(In reply to Andres Gomez from comment #10)
> The proper link seems to be:
> https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines

Thanks for pointing this out. Some wiki maintenance happened today and we forgot to add necessary redirects. Fixed.