mainSavannah Administration - Support: sr #110698, some email headers would be useful

 
 

sr #110698: some email headers would be useful

Submitter:  Eo Koochu <eokoochu>
Submitted:  Fri 19 Aug 2022 01:59:15 PM UTC
   
 
Category:  Savannah mail server Priority:  5 - Normal
Severity:  1 - Wish Status:  Works For Me
Privacy:  Public Assigned to:  ineiev
Operating System:  None Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Tue 30 Aug 2022 06:16:36 PM UTC, comment #2: 

I’m not getting those headers, but it’s possible that a mail forwarding service is stripping them out.

Sorry for the trouble!

Eo Koochu <eokoochu>
Tue 30 Aug 2022 05:10:02 PM UTC, comment #1: 

In a recent message, I can see these headers:


X-Savane-Server: savannah.nongnu.org:443 [209.51.188.113]
...
X-Savane-Project: administration
X-Savane-Tracker: support
X-Savane-Item-ID: 110621
X-Apparently-From: Savane authenticated user ineiev


Aren't they sufficient?

Ineiev <ineiev>
Site Administrator
Fri 19 Aug 2022 01:59:15 PM UTC, original submission:  

Email notices that are sent by Savannah have no meaningful headers & a very minimal amount of information in the headers. We see “@gnu.org” in the FROM field, but that is nearly useless because while Savannah is at gnu.org, not all of gnu.org relates to the Savannah bug tracker. We see a bug# in the subject line, but bug numbers are useless without knowing which forge/bug tracker/db they come from. The package name is not mentioned anywhere unless someone mentions it in the brief summary which then makes it onto the subject line.

If you are a Procmail user, it’s a bad practice to filter mail by the common headers (To, From, Subject) because they can change, they can represent the same info in a variety of different ways, they can be clobbered and manipulated by various email forwarding services. They neglect to convey the mechanical context by which the msg exists (e.g. was it distributed by an individual, a mailing list, or a misguided user on a mailing who directly sent you an extra copy?)

So to be brief, a well-seasoned procmail user uses a recipe like this to filter Debian bug report notices:

:0 :

  • ^X-Debian-PR-Package: \/.*

in/debian_bugs_${MATCH}_${YEAR:-0000}

The header conveys the bug tracker as well as the package the bug is about, and it does so in a way that is generally resilient to processing by mail forwarding services which munge the common/standard headers.

I therefore propose adding a header like:

x-savannah-(non)gnu: $pkgname/$bugnumber

If Bob were to start self-hosting his own Savannah called bobsplace, the header would be:

x-savannah-bobsplace: $pkgname/$bugnumber

Eo Koochu <eokoochu>

 

(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

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by ineiev (Posted a comment)
  • -email is unavailable- added by eokoochu (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 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-09-01 ineiev StatusNeed Info Works For Me
        Open/ClosedOpen Closed
    2022-08-30 ineiev StatusNone Need Info
        Assigned toNone ineiev

    Back to the top

    Powered by Savane 3.13-caa5.
    Corresponding source code