Block a malformed password reset email request at dispatch; change a recipient's suppression state only when delivery evidence supports that decision. In a logistics portal, confusing those actions can turn a sender-domain deployment mistake into an account-recovery problem for every dispatcher who asks for help.
TL;DR: For malformed password reset email requests, verify the sending domain and DKIM configuration, validate the API JSON payload, and preview the template with the backend's actual reset-link variables. An invalid from domain or template render error calls for configuration or payload repair. A subsequent bounce calls for message-and-event inspection before suppressing an invalid recipient. Retrying everything is an operational policy, and a poor one.
The runbook below treats false suppression as the release hazard. A Node.js application remains the caller; a small Go program makes the decision boundary executable without pretending that local diagnostic fields are a provider's request schema.…