With the GDPR becoming enforceable next week, I thought it would be good to point out a feature we added to PowerMTA v4.5r13 last quarter. Designed together with our partner Postmastery, it allows you to very easily remove or protect, by way of a secure hash, PII normally stored in PowerMTA’s accounting files. For example, to redact it, you’d configure:
<acct-file acct.csv> privacy-policy redact "redacted" ... </acct-file>
<acct-file acct.csv> privacy-policy siphash "secret" ... </acct-file>
to protect it with a hash. PowerMTA’s User’s Guide Section 11.3.1 has more details.
In this quarter’s v4.5r14, we’ll also be adding support for “negative” queue-filter patterns, allowing you to apply accounting file options such as these only to certain domains or Virtual MTAs:
<acct-file redacted.csv> queue-filter */vmta1 privacy-policy redact "redacted" ... </acct-file> <acct-file notredacted.csv> queue-filter !*/vmta1, */* privacy-policy retain ... </acct-file>
This way, the PII would be redacted from vmta1’s records, but not from any others.