Implement mail aliases for Cloud-VPS projects (<novaproject>@wmflabs.org)
Open, LowPublic

Description

Project membership information can be pulled from the OpenStack keystone API.

The Toolforge project itself has something like this that routes emails for <tool>@tools.wmflabs.org to the shared tool account where it can be processed using .forward files. That processing is LDAP based, using a lookup script and exim4 configuration.

Possible implementations:

  • *@<project>.wmflabs.org forwards to project admins
  • <project>@<something>.wmflabs.org forwards to project admins
  • <project>-(admins|members)@<something>.wmflabs.org forwards to project admins/members
  • ...

Having some kind of optional per-project address -> destination mapping similar to the Toolforge feature would also be nice, but that is not necessary for an initial implementation.

Ideally this base feature can also be leveraged to fix T61142: root@<labs-instance> should email project admins either directly or indirectly.

Details

Reference
bz45828
bzimport raised the priority of this task from to Low.
bzimport set Reference to bz45828.
Aklapper removed RyanLane as the assignee of this task.Apr 26 2015, 12:11 PM
bd808 added subscribers: herron, bd808, Legoktm.

I was actually just asking @bd808 about the status of mail access for Cloud VPS projects yesterday. At least for my use case, it would be great if mail to <something>@<projectname>.wmflabs.org (where something is fixed string(s) or any string) just worked for forwarding to the project members, without any setup required in the individual project.

it would be great if mail to <something>@<projectname>.wmflabs.org (where something is fixed string(s) or any string) just worked for forwarding to the project members, without any setup required in the individual project.

I'd love to see some solution for this too. One potentially tricky step here is that project membership information has been moved out of the LDAP directory and is now completely managed in OpenStack's keystone API. Next tricky step is that <projectname>.wmflabs.org does not exist in DNS by default. This could be handled by the *.wmflabs.org MX record suggested by @herron in T41785#3566374 though. It is possible for projectX to register an HTTP proxy named projectY.wmflabs.org which could complicate/confuse things based on hostname level forwarding. It might be simpler to use addresses like <projectname>@<vps mail relay identifier>.wmflabs.org for the "contact a project's members" use-case. <vps mail relay identifier> could be something like projects or vps.

bd808 renamed this task from Labs: Implement mail aliases for projects (<novaproject>@wmflabs.org) to Implement mail aliases for Cloud-VPS projects (<novaproject>@wmflabs.org).Aug 30 2017, 8:15 PM
bd808 removed a project: Cloud-Services.
bd808 updated the task description. (Show Details)
Dzahn removed a subscriber: Dzahn.Sep 6 2017, 5:33 PM