X-Launchpad-Message-Rationale header isn't for the most direct subscription

[Jeremy Kerr]

Since I'm a member of quite a few launchpad teams, I get quite a bit of bug updates emailed to me. To make sure I don't miss out on anything important, I filter notifications about the bugs that I'm subscribed to into a separate mail folder (by looking at the X-Launchpad-Message-Rationale header.

Bugs that I'm directly subscribed to have:

 X-Launchpad-Message-Rationale: Subscriber

whereas bugs that I'm indirectly subscribed to (ie, through a team membership), have:

 X-Launchpad-Message-Rationale: Subscriber @dell-team

In case it helps, I use the following sieve code:

 if header :contains "X-Launchpad-Bug" "" {
  if header :is "X-Launchpad-Message-Rationale" "Subscriber" {
   fileinto "lp.subscribed";
  } else {
   fileinto "lp";
  }
 }

The problem is that the X-Launchpad-Message-Rationale value is not the most specific rationale. If both me *and* dell-team are subscribed to a bug, I get:

 X-Launchpad-Message-Rationale: Subscriber @dell-team

- indicating that I'm getting the mail from my membership to the dell team, rather than from my direct subscription to the bug itself. So, there is no way to filter these messages into my 'important' mailbox.

Is is possible to calculate the *most specific* rationale, and use that instead?

That's not feasible, is it possible to list all of the possible rationales? Something like "Subscriber, Subscriber @dell-team", or even multiple X-L-M-R headers would work.

[Graham Binns (gmb)]

I think this is a fine idea, and probably wouldn't be all that hard to do. For specificity's sake we should assume that direct subscription > structural subscription > subscription via a duplicate, I think.