from: and to: address for mails sent by Launchpad needs reanalysis and harmonisation across the system
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
IIUC, merge proposal emails are sent with a To: header set to the owner of the branch, and essentially Bcc'd to all subscribers of the branch and the project driver. If the driver is a mailing list, this Bcc will trip up the "implicit destination" filter in Mailman. By default, Mailman has a spam filter that requires the mailing list address to be explicitly mentioned in the To or Cc headers, although you can configure your list to accept one or more aliases (addresses or regexps). When the driver is Bcc'd, the mailing list address does not appear in any recipient header and the message gets held for moderation.
Even without mailing lists in the picture, merge proposal messages look like spam ;). In my direct copy I see a To header addressed to someone I have no idea who they are.
I think it would be better to use the merge proposal address in the To header. E.g. if the message had
To: <email address hidden>
From: <email address hidden>
then it would have several advantages. It would make more sense, it would be immediately obvious that this was a merge proposal notification, and i could set the mailing list alias to match the To header because it would be predictable.
| affects: | launchpad → launchpad-code |
| Tim Penhey (thumper) wrote | #1 |
| Changed in launchpad-code: | |
| status: | New → Incomplete |
| tags: | added: email |
| Changed in launchpad: | |
| status: | Incomplete → Triaged |
| importance: | Undecided → Wishlist |
| summary: |
- merge proposal emails Bcc'd to forged To address + from: and to: address for mails sent by Launchpad needs reanalysis and + harmonisation across the system |
| Changed in launchpad: | |
| importance: | Wishlist → Low |
It is a bit more difficult than that. When we initially did the email identification we modelled the code on bugs.
Now it seems that we do specify the merge proposal email in the to field for some but not all of the emails.
Whatever we decide, we should have a policy that applies across all the email sent by launchpad.