We are an Operations Team and use Phabricator and especially Maniphest for managing incoming Requests from our Users. If a User has a Problem, he should file a new Maniphest Task for it. They can either use the Web UI or send an Mail into Phabricator. We configured an incoming Application Mail Adress for Maniphest for that.

Sometimes Users instead write Mails to specific Members of our Team. Since we are nice guys, we wouldn't tell them to stop being lazy and create a Maniphest Task, but instead do it ourselves. However, our workflow for that isn't really handy right now. Basically it boils down to copying the relevant Parts of the Mail and copy-pasting them into the Web Interface. Of course we first tried the most obvious Solution and just forwarded Mails to our Phabricator.

The Problem with that is, that Phabricator seems to cut off the mail history for everything it receives so we basically end up with a new Ticket thats fairly empty since the interesting Part (the forwarded User Mail) got truncated. I think the rationale behind cutting of mail history is, that it doesn't make sense for replys to mails sent by Phabricator (for e.g. existing Tasks) to duplicate the entire History of the Task in every Comment received by mail.

Hoewever, since in this specific case, we will always want to create new Tasks, we can safely assume that there's no pre-existing history regarding this Task anyway and therefore everything thats forwarded is probably important. So if I send an Mail to Maniphest and it creates a new Object instead of replying to an existing one, i'd like to have the entire Mail and not just the Part i wrote myself.

(Another suggestion for our Problem (though I think much harder to implement) would be instead of cutting of Mail History to parse it instead and try to match it to existing Objects (Tasks or Comments) and use everything else that couldn't be found for Mail Body instead.)