- User Since
- Aug 7 2012, 12:25 AM (341 w, 4 d)
Oct 22 2018
Apr 21 2018
Sep 11 2017
kind of sad this isn't called pherret
May 22 2017
Mar 30 2017
Mar 5 2017
Feb 14 2017
closed per user request
(dropped this since I don't have time to fully test, but I might come back to this in the future)
Feb 10 2017
Feb 9 2017
From: email@example.com To: firstname.lastname@example.org, email@example.com Reply-to: firstname.lastname@example.org Subject: Yellow Blosums 2
Some more thoughts: even if we can't control the Reply-to in all cases, phabricator can look at the TO header and perhaps choose not to send mail if it looks like it was already sent to a given user. Of course, given the above, this is spoofable.
Unless I'm missing something, I think the instructions here cause X to receive two mails (they are on "To" for both).
Feb 1 2017
Jan 31 2017
Jan 27 2017
Jan 18 2017
Jan 13 2017
Jan 1 2017
Dec 29 2016
Agreed. I suspect that this was mostly the case of seeing two "A" words near each other (and possibly just being used to ↓+A+enter
one complaint we (FreeBSD) get when we enable abandon for anyone is that the top action is abandon, not accept, and this causes it get used accidentally. Does this change that behavior?
Dec 28 2016
FWIW #Twitter has multiple users of this feature and we'd likely get complaints if it broke
updated advisory; https://legalhackers.com/advisories/PHPMailer-Exploit-Remote-Code-Exec-CVE-2016-10045-Vuln-Patch-Bypass.html
I don't think this changes the plan you suggest, just linking for completeness.
Dec 22 2016
You should reask this in https://secure.phabricator.com/ponder/
Maniphest is for bugs and feature requests, not help
T5505 is related
Dec 19 2016
Nov 28 2016
Nov 24 2016
Nov 23 2016
Nov 21 2016
Performance concern. At least one use case requires us to scour *all diffs and all diff ids*. Also a desire to avoid having deprecated calls in our codebase.