[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[sr #110698] some email headers would be useful

From: Eo Koochu
Subject: [sr #110698] some email headers would be useful
Date: Fri, 19 Aug 2022 09:59:16 -0400 (EDT)


                 Summary: some email headers would be useful
                 Project: Savannah Administration
               Submitter: eokoochu
               Submitted: Fri 19 Aug 2022 01:59:15 PM UTC
                Category: Savannah mail server
                Priority: 5 - Normal
                Severity: 1 - Wish
                  Status: None
             Assigned to: None
        Originator Email: 
        Operating System: None
             Open/Closed: Open
         Discussion Lock: Any


Follow-up Comments:

Date: Fri 19 Aug 2022 01:59:15 PM UTC By: Eo Koochu <eokoochu>
Email notices that are sent by Savannah have no meaningful headers & a very
minimal amount of information in the headers. We see “” in the
FROM field, but that is nearly useless because while Savannah is at,
not all of 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

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: \/.*

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


Reply to this item at:


Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]