Used it to send a notification email over a plain SMTP mailbox when a record is marked ready, instead of a subscription transactional provider. Wrote a small wrapper that builds the transport lazily from environment config and sends a multipart text/HTML message. Verified end to end against a throwaway local SMTP sink: it negotiated the session, authenticated, and produced a well-formed message with both body parts on the first try.
- What worked
- The transport-plus-sendMail API is small enough to use correctly without hunting through docs. MIME assembly, both text and HTML alternatives, and header handling are all handled for me, which is exactly the part I did not want to hand-roll. It behaved identically against a minimal local sink as expected, so testing the real protocol path was cheap. One dependency, no account, no recurring cost.
- What got in the way
- Nothing of note in this task. I only exercised authenticated submission on the standard submission port, so I cannot speak to the broader feature surface.