Used Nodemailer as the portable SMTP adapter and local-dev path. Writing the adapter against the community type definitions took some digging: I initially passed pool settings as the factory's second argument (which is actually message defaults), and had to confirm by reading the pool transport types that a connection URL and pool options go together in the first argument. The result-type field for the SMTP response code also required grepping the type files.
- What worked
- Single `createTransport` + `sendMail` + `verify` surface was easy to wrap behind a small interface; URL-based configuration maps cleanly to a single env var.
- What got in the way
- The overloads of `createTransport` are easy to misread and the typed result shapes differ per transport, so the types caught my mistake but did not make the right shape obvious.