Compare nodemailer vs sendgrid for email use cases, including package popularity, downloads, ecosystem fit, and practical tradeoffs.
Unable to load comparison data. Please try again later.
Send emails from Node.js – easy as cake! 🍰✉️
See nodemailer.com for documentation and terms.
Nodemailer is developed by the team behind EmailEngine, a self-hosted email API that turns any Gmail, Microsoft 365, or IMAP account into a REST endpoint, with managed OAuth2, webhooks for incoming mail, and built-in sending. If you would rather call an HTTP API than maintain IMAP and SMTP connections yourself, that is what it is for.
Nodemailer targets Node.js 20 and later. The ES module build also runs on Bun (tested against the latest release) and on Cloudflare Workers with the nodejs_compat compatibility flag. On Workers only the SMTP based transports apply, sendmail needs a child process, and the runtime does not allow turning certificate validation off, so tls.rejectUnauthorized: false fails there with an error.
Pass an AbortSignal in the message options to cancel one sendMail() call:
await transporter.sendMail({ from: 'sender@example.com', to: 'recipient@example.com', text: 'Hello', signal: AbortSignal.timeout(30_000) });
This is supported by SMTP and pooled SMTP transports. A pre-aborted signal prevents processing; aborting later stops subsequent plugin processing, removes a queued message, or closes the SMTP connection assigned to that message. Other deliveries in the pool can continue. Both promise and callback forms report an error named AbortError, with code: 'EABORT' and the signal's reason as cause. The signal listener is removed when the send finishes.
Cancellation stops local processing; it does not prove that the SMTP server has not already accepted the message. Do not retry a cancelled send automatically on that assumption.
Work already started by a plugin or a custom getSocket hook requires that code's cooperation to stop. Nodemailer ignores late plugin completion and destroys a socket handed back after cancellation. Plugins can read mail.data.signal to cancel their own work.
Other bundled transports (stream, JSON, sendmail and SES) ignore the signal once the message is handed to them, so the message is sent normally. A signal that is already aborted, or aborts while plugins run, still cancels the send with EABORT on every transport, as that happens before the transport is called. A signal value that is not an AbortSignal fails the send with ECONFIG. Custom transports can opt in with supportsAbortSignal: true; their send() must register its abort listener synchronously, check for a pre-aborted signal, stop the work it owns, invoke its callback once, and remove the listener on completion.
When an SMTP connection closes, Nodemailer ends the socket and destroys it if the server has not closed its side within socketCloseTimeout milliseconds (default 5000). Set it to 0 to destroy the socket right away. This applies to SMTP and pooled SMTP, including aborted sends and transporter.close({ force: true }). It does not tell you whether the server accepted a message that was in flight.
Documentation for Nodemailer can be found at nodemailer.com.
Nodemailer 10 and later require Node.js 20 or newer. The package ships both ES module and CommonJS builds, so import nodemailer from 'nodemailer' and const nodemailer = require('nodemailer') both work. If you need to run on an older Node.js version, stay on the 9.x line.
Gmail either works well, or it does not work at all. It is probably easier to switch to an alternative service instead of fixing issues with Gmail. If Gmail does not work for you, then don't use it. Read more about it here. If the blocker is OAuth2 setup rather than Gmail itself, EmailEngine handles the OAuth2 flow and token refresh for you.
Check your firewall settings. Timeout usually occurs when you try to open a connection to a firewalled port either on the server or on your machine. Some ISPs also block email ports to prevent spamming.
It's either a firewall issue, or your SMTP server blocks authentication attempts from some servers.
secure option. This should be set to true only for port 465. For every other port, it should be false. Setting it to false does not mean that Nodemailer would not use TLS. Nodemailer would still try to upgrade the connection to use TLS if the server supports it.false to skip chain verification or upgrade your Node versionlet configOptions = { host: 'smtp.example.com', port: 587, tls: { rejectUnauthorized: true, minVersion: 'TLSv1.2' } };
Node.js uses c-ares to resolve domain names, not the DNS library provided by the system, so if you have some custom DNS routing set up, it might be ignored. Nodemailer runs dns.resolve4() and dns.resolve6() to resolve hostname into an IP address. If both calls fail, then Nodemailer will fall back to dns.lookup(). If this does not work for you, you can hard code the IP address into the configuration like shown below. In that case, Nodemailer would not perform any DNS lookups.
let configOptions = { host: '1.2.3.4', port: 465, secure: true, tls: { // must provide server name, otherwise TLS certificate check will fail servername: 'example.com' } };
Nodemailer 10 and later are written in TypeScript and ship their own type definitions, so @types/nodemailer is no longer needed and should be removed from your project to avoid conflicting declarations. The type names follow the layout of the old definitions, so references such as Mail.Options, SMTPTransport.Options or Transporter<SMTPTransport.SentMessageInfo> keep compiling, and the most used types (SendMailOptions, Transporter, SentMessageInfo, Attachment, Address) are exported from the package root. The modules under nodemailer/lib/ are declared with a default export, so import a class as import SMTPTransport from 'nodemailer/lib/smtp-transport' (with esModuleInterop in a CommonJS project). The import SMTPTransport = require(...) and import * as SMTPTransport from ... forms still resolve the type aliases such as SMTPTransport.Options, but they refer to the module rather than to the class, so the class itself has to be imported with a default import. For older Nodemailer versions, the community maintained type definitions still apply.
If you are having issues with Nodemailer, then the best way to find help would be Stack Overflow or revisit the docs.
Nodemailer is licensed under the MIT No Attribution license
The Nodemailer logo was designed by Sven Kristjansen.