Skip to content

fix: resolve well-known services by their primary domains - #1859

Merged
andris9 merged 1 commit into
nodemailer:masterfrom
soroush5:fix/well-known-primary-domains
Sep 10, 2026
Merged

andris9 merged 1 commit into
nodemailer:masterfrom
soroush5:fix/well-known-primary-domains

Conversation

@soroush5

Copy link
Copy Markdown
Contributor

NB! Nodemailer is frozen, so no new features please, only bug fixes.

Fixes #1858.

wellKnown('[email protected]') and wellKnown('[email protected]') returned false because icloud.com and fastmail.com were missing from the domains lists, so service-based setup silently got no SMTP settings for those addresses. Adds the two domains; no behavior change otherwise.

Tests: added lookup cases to test/well-known/well-known-test.ts (6/6 pass), neighboring smtp-transport suite 14/14 pass, npm run lint and format:check clean.

wellKnown('[email protected]') and wellKnown('[email protected]')
returned false because icloud.com and fastmail.com were missing
from the domains lists, so service-based SMTP setup silently got
no host/port for those addresses.
@andris9
andris9 merged commit 085f525 into nodemailer:master Sep 10, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

well-known lookup fails for @icloud.com and @fastmail.com addresses

2 participants