See T13069 for mail stamp plans.

I'm just going to merge this into T10448.

I suspect this is actually more like: actions on Ponder answers are not covered by the "Ponder Questions" email preferences, because a "Ponder Answer" is not the same type of object as a "Ponder Question".

This is similar to T9982. Complete that task first, which describes the SQL migration process in more detail.

I think we got rid of this since it was kind of weird and overlapped a lot with tokens.

https://nylas.com/

All the cool companies use Phabricator.

I should switch to Nylas since they use Phabricator.

Airmail on Mac, it has a few quirks with our HTML emails, but I haven't tried to debug it yet. I'm sure we're doing something weird since all other HTML seems fine in it.

I think we're relying on white-space: pre-wrap; right now. We could explicitly do \n -> <br /> conversion which might fix newlines, at least.

Which client do you use? I imagine the html relies on <br> or something, but would \n vs. \r\n be involved at all?

maybe by 2050 email will work most of the time for most people

I use a crappy email client

The actual diff is further down and rendered correctly for me, at least -- that's just how we currently render "added one line to the middle of a 500 line document" right now:

No, that's this stuff from T7643#179240:

I got a super long email from Phriction today, is that also an EditEngine freebie?

This will vanish for free when we move to EditEngine, or it could be special cased before that by either:

Yes, this is probably pretty straightforward to implement by mostly copying Maniphest's implementation.

@epriestley I assume application emails are abstracted like Maniphest?

That's exactly what I needed.
I thought I could create one global rule to do this. But if I get this right, I have to create multiple rules for every single project to add as subscriber :D

Ok this has been removed now.

(yes it does)

Closing as Ponder no longer has voting

This is confusing, I assume you're changing the settings for "Ponder Questions". There isn't a set of mail preferences for "Ponder Answer".

This was fixed in connection with T9825.

This probably requires $types[] = PhabricatorTransactions::TYPE_EDGE; in PonderAnswerEditor->getTransactionTypes(). It would be vaguely nice to do this more automatically/consistently, but probably not worth pursuing some grander approach at this time. T9789 is probably on the horizon and represents a better opportunity.

I think I just configured remarkup.ignored-object-names wrong when I added S3, should be OK now going forward.

Q175: Should I Reuse Device Keys?

I've seen this once, but I couldn't duplicate why it happened. Possibly fixed already? Open a full ticket if you do hit a repro case.