mainSavannah Administration - Support: sr #111106, Need a way to disable email...

 
 

sr #111106: Need a way to disable email replies to savannah trackers mails, on a per-project basis

Submitter:  Bruno Haible <haible>
Submitted:  Wed 14 Aug 2024 05:59:23 PM UTC
   
 
Category:  Savannah trackers - bugs, tasks, etc. Priority:  5 - Normal
Severity:  3 - Normal Status:  Done
Privacy:  Public Assigned to:  ineiev
Operating System:  None Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Sat 17 Aug 2024 02:28:01 PM UTC, comment #8: 

Great work, Ineiev!   Thank you for your (prompt) work on this feature (and to Bruno for pointing out the concern)!

Corwin Brust <carlc>
Site Administrator
Sat 17 Aug 2024 01:47:45 PM UTC, comment #7: 

Thank you.

Ineiev <ineiev>
Site Administrator
Sat 17 Aug 2024 01:23:31 PM UTC, comment #6: 

Thanks. The new notification comment


To reply to this notification, you have two options:
* In the Web UI at <https://savannah.nongnu.org/support/?111106>.
* By email, ONLY IF you sign your email with a GPG key registered
  in your Savannah account AND you include the following line
  in the reply:

  {savane: user = 1871; tracker = support; item = 111106}


should be sufficient to guide most users appropriately.

Bruno Haible <haible>
Site Administrator
Sat 17 Aug 2024 01:16:30 PM UTC, comment #5: 

comment #2:

> To reply to this notification, you have two options:
...
email AND you include the following line in the reply:
> {savane: user = 1871; tracker = support; item = 111106}


Done; let us see what further changes are needed.

Ineiev <ineiev>
Site Administrator
Thu 15 Aug 2024 07:05:56 PM UTC, comment #4: 


> > The feature offers users an option to post on trackers using
> GnuPG-authenticated email.
>
> Ah, that explains why the reply ended up on the mailing list, not on the
> tracker.


/Just explaining this to myself:/ That explains why the reply ended up
only on the mailing list but not on the tracker.  the Reply-To:
header contained both addresses, and I believe the poster sent
the message to all.  GnuPG signature by itself doesn't direct
it to savannah-trackers@ rather than to the mailing list.

> In order to prevent that, please add some text to the reply, to
> explain the feature and its limitations.

...

> To reply to this notification, you have two options:
> * Reply in the tracker at https://savannah.gnu.org/bugs/<number> after logging
> in, or
> * By email, IF AND ONLY IF you are using GnuPG-authenticated email AND you
> include the following line in the reply:
> {savane: user = 1871; tracker = support; item = 111106}


Thank you, I shall.

> > changing the Reply-To: header to avoid the mailing lists
>
> This would be even worse, because it would turn the discussion into a private
> email discussion. It is essential for the community that discussions happen in
> public.


I see.

>> adding a user preference to include that data, disabled by default.
>
> That is also a possibility; if so, please include the notice about
> GnuPG-authentication here as well.


I'll bear this in mind if I implement this.

Ineiev <ineiev>
Site Administrator
Thu 15 Aug 2024 07:01:59 PM UTC, comment #3: 


> > The feature offers users an option to post on trackers using
> GnuPG-authenticated email.
>
> Ah, that explains why the reply ended up on the mailing list, not on the
> tracker.


/Just explaining this to myself:/ That explains why the reply ended up
only on the mailing list but not on the tracker.  the Reply-To:
header contained both addresses, and I believe the poster sent
the message to all.  GnuPG signature by itself doesn't direct
it to savannah-trackers@ rather than to the mailing list.

> In order to prevent that, please add some text to the reply, to
> explain the feature and its limitations.

...

> To reply to this notification, you have two options:
> * Reply in the tracker at https://savannah.gnu.org/bugs/<number> after logging
> in, or
> * By email, IF AND ONLY IF you are using GnuPG-authenticated email AND you
> include the following line in the reply:

Ineiev <ineiev>
Site Administrator
Thu 15 Aug 2024 04:52:28 PM UTC, comment #2: 


> they are correct at least partially: they can comment on the tracker through email.


I would have nothing against that, if it was guaranteed that the reply ends up in the tracker, at that ticket.

> The feature offers users an option to post on trackers using GnuPG-authenticated email.


Ah, that explains why the reply ended up on the mailing list, not on the tracker. In order to prevent that, please add some text to the reply, to explain the feature and its limitations. Either


DO NOT REPLY BY MAIL unless you are using GnuPG-authenticated email.


or, with some more verbosity:


To reply to this notification, you have two options:
* Reply in the tracker at https://savannah.gnu.org/bugs/<number> after logging in, or
* By email, IF AND ONLY IF you are using GnuPG-authenticated email AND you include the following line in the reply:
{savane: user = 1871; tracker = support; item = 111106}


Rationale: 99% of the people I know use email without GnuPG-authentication. It is therefore essential to remind people that this is a requirement for not creating a communication mess.

> changing the Reply-To: header to avoid the mailing lists


This would be even worse, because it would turn the discussion into a private email discussion. It is essential for the community that discussions happen in public.

> adding a user preference to include that data, disabled by default.


That is also a possibility; if so, please include the notice about GnuPG-authentication here as well.

Bruno Haible <haible>
Site Administrator
Thu 15 Aug 2024 04:13:55 PM UTC, comment #1: 

On Wed, Aug 14, 2024 at 01:59:25PM -0400, Bruno Haible wrote:

> Now, for two weeks (more precisely, since
> https://git.savannah.gnu.org/gitweb/?p=administration/savane.git;a=commitdiff;h=940893361e4e6d9ce2b5c010613595b83c80529f
> ), the sent mail contains
> 1) a line "Include the next line when replying by email."
> 2) a CC such as 362990-bugs-savannah <savannah-trackers@gnu.org>
> which makes the recipient think that they can / should reply by mail.


If they think so, they are correct at least partially: they
can comment on the tracker through email.

> Please provide a way to turn this off on a per-project/package basis.


The feature offers users an option to post on trackers using
GnuPG-authenticated email. it's up to the user who submits comments
what way to use, handling that on per-package basis is pointless.

What I can think of instead is,

  • improving the comment "Include the next line when replying by email.";
  • changing the Reply-To: header to avoid the mailing lists;
  • adding a user preference to include that data, disabled by default.


Ineiev <ineiev>
Site Administrator
Wed 14 Aug 2024 05:59:23 PM UTC, original submission:  

For many years, savannah trackers mails from my tracker items started out with "From: Bruno Haible <INVALID.NOREPLY@gnu.org>". This told the recipient immediately that they should not reply by mail, but instead reply through the bug tracker.

Now, for two weeks (more precisely, since https://git.savannah.gnu.org/gitweb/?p=administration/savane.git;a=commitdiff;h=940893361e4e6d9ce2b5c010613595b83c80529f ), the sent mail contains
1) a line "Include the next line when replying by email."
2) a CC such as 362990-bugs-savannah <savannah-trackers@gnu.org>
which makes the recipient think that they can / should reply by mail.

Please provide a way to turn this off on a per-project/package basis.

Rationale: I can handle discussions on a mailing list. I can handle discussions in a bug tracker. But discussions that start in a bug tracker and then continue on a mailing list are a big mess.

For example, a ticket started here: https://savannah.gnu.org/bugs/?66089
and the reporter then replied by mail here: https://lists.gnu.org/archive/html/libffcall/2024-08/msg00003.html
This is madness. How am I, as a package maintainer, supposed to keep the ticket in sync?

Bruno Haible <haible>
Site Administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Digest:
   support dependencies.

 

Carbon-Copy List
  • -email is unavailable- added by carlc (Posted a comment)
  • -email is unavailable- added by ineiev (Posted a comment)
  • -email is unavailable- added by haible (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2024-08-17 ineiev StatusReady For Test Done
        Open/ClosedOpen Closed
    2024-08-17 ineiev StatusIn Progress Ready For Test
    2024-08-15 ineiev StatusNone In Progress
        Assigned toNone ineiev
    2024-08-15 ineiev Dependencies- support #106712 is dependent

    Back to the top

    Powered by Savane 3.15-26b0.
    Corresponding source code