Send bug mail to bug address
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Mail from merge proposals, for example, has a To: header that includes the merge proposal address (e.g. <email address hidden>) in addition to the recipient. The Reply-To: address is set to just the merge proposal address.
Bug mail has only the recipient in the To: header, and Reply-To: is set to the bug address (e.g. <email address hidden>). It would be much easier to filter in Gmail if the bug address was included in the To: header.
Now, as to correctness, I feel that the Bugs way is more correct, but it would be wrong to discount anything the Code team does. They have such big brains that they can't ever meet in person because of gravitational effects. In other words, there is probably a very good reason why merge proposal addresses are added to the To: header of outgoing proposal email.
In any case, it's probably worth coming up with an agreed form for outgoing mail, then either documenting it, or enshrining it in code, or both.
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Deryck Hodge (deryck) wrote | #1 |
| summary: |
- Include the bug address in bug mail + Send bug mail to bug address |
| tags: | added: story-better-bug-notification |
I think we should converge on the code team's version of sending mail. This can be done as part of our better bug notifications work.