nodemailer

10.2.1 · 22 Oct 2026MIT-023.7M / weekRepository Homepage npm Atom feed

Same major only

1 release in betweenevery note read

Other targets from 2.1.0Newest 2.x2.7.2 Clears its 15 advisories10.0.6 Latest10.2.1

0
changes to make: 0
advisories fixed: 7
new: 0
fixes

Security

15 advisories still affect 2.2.0

Nodemailer: CRLF injection in Nodemailer List-* header comments allows arbitrary message header injectionmoderate · GHSA-268h-hp4c-crq3
Command injection in nodemailercritical · GHSA-48ww-j4fc-435p
Nodemailer: resolveContent() on a MailMessage bypasses disableFileAccess/disableUrlAccess when called with the legacy signaturemoderate · GHSA-8m3c-c648-2xjj

Upgrading to 10.0.6 clears them.

Release by release

2.2.0
18 Feb 20167 new
- new
  Added new method verify to check SMTP configuration
- new
  Added new message option list for setting List-* headers
- new
  Add simple proxy support with getSocket method
- new
  Added new message option textEncoding. If textEncoding is not set then detect best encoding automatically
- new
  Added new message option icalEvent to embed iCalendar events. Example here
- new
  Added new attachment option raw to use prepared MIME contents instead of generating a new one. This might be useful when you want to handcraft some parts of the message yourself, for example if you want to inject a PGP encrypted message as the contents of a MIME node
- new
  Added new message option raw to use an existing MIME message instead of generating a new one

2 other lines we could not sort, mostly version bumps

Removed the need to use clone dependency
2.2.0
Direct transport uses STARTTLS by default, fallbacks to plaintext if STARTTLS fails
2.2.0

Upgrade to 2.2.0

npm install nodemailer@2.2.0

What 2.2.0 needs

Reading 2.2.0's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 2.2.0. Read once, not stored.

After upgrading

Run the type checker, the linter and the tests.
Build, and look for new deprecation warnings.
Update peer dependencies the new version asks for.
15 advisories still affect 2.2.0.