This task was filed through the "New Feature Request" form.
Sat, Jan 19
D19968 got us closer here, but the link targets aren't actually rendering properly.
Wed, Jan 16
Mon, Jan 14
Wed, Jan 2
I'm not confident there's really a path forward here even for the subset of mailers where we have full control of the SMTP envelope and can generate Message-IDs, which is only a small subset of mailers today. Even if it does work, it makes the "Reply All" problem worse.
Fri, Dec 28
...it is virtually inconceivable to me that this is something we would ever bring upstream in any form.
Dec 22 2018
Dec 20 2018
Dec 19 2018
Dec 18 2018
@amckinley, for general context on where I'm headed here:
Dec 12 2018
This doesn't seem to be cropping up terribly often and I think this use case is fairly weak.
This might happen eventually, or as a side effect of T7303, but the use case here is pretty narrow and there's currently no customer interest so I don't currently anticipate building it.
Password management is in good shape after T13043 , and this would now be fairly easy to implement in a general way by adding a check in PhabricatorAuthPasswordEngine->isUniquePassword().
Dec 11 2018
Dec 10 2018
When users click "Create Subtask", we now look for a list of possible subtask forms.