4 ms·
That's sounds pretty easy to solve redacting the sensitive content when it hits your mail server before going to support staff. If you're sending out HTML email
by jacobparker 9y ago
That's sounds pretty easy to solve redacting the sensitive content when it hits your mail server before going to support staff. If you're sending out HTML email you can also make easy and extensible by having a custom class for redactable contents.
Realistically customers are going to fwd those emails anyway so this approach is more robust.
It seems like most information in these emails would be available to support staff typically though. It sounds like a niche case.
- pavel_lishin 9y ago> That's sounds pretty easy to solve Everything does if you just glance at someone's comment online and dash one off. How do you recognize which is the sensitive content and which isn't? How do you handle the case where you send out HTML emails, but the response strips all of the HTML and sends plain text back?