Should fix all email reply issues, but no solid means of testing at home (how do you local reply test?)
Details
Details
- Reviewers
epriestley - Maniphest Tasks
- T3846: Build reply handler functionality for Ponder
- Commits
- Restricted Diffusion Commit
rPed77b639f0cf: Fix Ponder Answer email reply handler
Check for answer mail in /mail/ and see proper headers. Make sure question mail works too.
Diff Detail
Diff Detail
- Repository
- rP Phabricator
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
The easiest way to test inbound mail is generally:
$ nano body.txt # Write the body of your mail $ ./bin/mail receive-test --as epriestley --to D123 < body.txt
Since A123 isn't actually an object monogram (I think?), I'm not sure if A123 will work, though. If it doesn't, the answer PHID might.
I think the reason these Editors share some of the templating code is to try to get questions and answers to thread together. At least in Mail.app, they aren't always threading together even now, and this change will probably make them thread together less often in more clients. But maybe that's fine.