Password Reset Email for Property Compliance: Node.js API or SMTP Relay?

When implementing a password reset email feature in a Node.js application, there are two main options: using a server-side email API or utilizing an SMTP relay. The primary trade-off between the two approaches is ownership. By owning the email API, you have full control over the template, recipient rules, token or notice ID, and audit record. On the other hand, using an SMTP relay allows you to leverage an organization's existing infrastructure for sending emails.

For a property management product, it is recommended to use a server-side email API for password reset emails. This ensures that the template ownership, recipient rules, and the audit record are all managed by your application. By doing so, you can provide a compliant and reliable password reset experience for your tenants.

The key to a successful password reset email implementation lies in building a record of the message before choosing a transport. This record should include an opaque message ID, purpose, recipient reference, template version, locale, creation time, and a hash of the rendered content. It is essential not to store the reset token in the audit record, but rather a hash or token ID with a short expiry enforced by the account service.

To avoid potential failures, create an outbox row with the message details before sending the password reset email. This outbox row should be committed with the password-reset request or notice creation. A worker then picks up the outbox row and delivers the email. Mark the row with an idempotency key derived from the message ID to prevent duplicate emails in case of retries.

When it comes to template ownership, it is crucial to keep templates in an application-controlled source or a versioned template store. This ensures that legal wording, locale, and review history are under your product's control. For compliance notices like "inspection access required," store the template version alongside the delivery attempt to maintain a clear audit trail.

The TypeScript delivery adapter should guarantee a narrow interface that depends on generic user-facing responses, server-only secrets, bounded retries for HTTP 429 status codes, and an outbox ID used as the idempotency key. By abstracting the transport URL and field mapping behind an adapter, you ensure that the application remains decoupled from the specific email delivery mechanism.