Page MenuHomePhabricator

Update "Configuring Inbound Email" to describe application email configuration in greater detail
Closed, ResolvedPublic


The "Configuring Inbound Email" document covers the technical/config steps, but doesn't actually walk through the application email setup stuff.

There's also a mention in "Spaces User Guide" that should probably be crosslinked.


We have a few different teams within our company that uses Phabricator for their own backlogs, and multiple teams would like to use the mail feature in Phabricator to receive new tasks to their specific backlog. One option we have is educate all of our users that they should write !project [teamname] and not type it wrong in all of their mails.
The other option we've identified would be to give them a mail address for each team, like and and that would then end up in Phabricator as an issue with the correct project attached. Now, we could attach the project to mail during inbound mail processing by appending !project to the body, but it is kind of fragile and it does not support encrypted emails either (I guess?). So, it would be really cool if you could control all of the !commands within mails with X-Phabricator--style headers as well as the in-body !commands. I would assume the !commands would take precedence if they contain overlapping or conflicting assignments.

Event Timeline

mikn raised the priority of this task from to Needs Triage.
mikn updated the task description. (Show Details)
mikn added projects: Mail, Maniphest.
mikn added a subscriber: mikn.
  • Define a recipient address for each team in ApplicationsManiphestHelp/OptionsEdit Application Emails. For example, and For example, here are five different receiving addresses:

Screen Shot 2015-06-22 at 4.54.42 AM.png (772×1 px, 158 KB)

  • Use "Receiving Email Address" rules in Herald to add projects and subscribers based on which address mail is sent to. For example:

Screen Shot 2015-06-22 at 4.54.10 AM.png (1×1 px, 170 KB)

Does that solve your problem?

This is actually pretty much exactly what we were looking for. Could be cool to add to the incoming email documentation, perhaps? Thank you, none the less. :)

epriestley renamed this task from Ability to assign projects on inbound mail issues through headers to Update "Configuring Inbound Email" to describe application email configuration in greater detail.Jun 22 2015, 2:49 PM
epriestley updated the task description. (Show Details)
epriestley edited projects, added Documentation; removed Maniphest.