About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Postfix is refusing the sender (MAIL FROM) address because the sender's domain did not resolve as a mail domain. With the default smtpd_delay_reject = yes, the client receives the refusal as the answer to its RCPT TO command. The reply text is built in smtpd_check.c. The class name is the string Sender address, which smtpd_dsn_fix.h at tag v3.9.1 defines as #define SMTPD_NAME_SENDER "Sender address", and the reason string is Domain not found. The enhanced status the source passes for a sender is 4.1.8. With the default unknown_address_reject_code of 450, the client sees 450, 4.1.8, and Sender address rejected: Domain not found.
The client should try again later. That is what 450 means here. It does not mean the recipient was rejected, and it does not mean relaying was denied.
If the administrator has set unknown_address_reject_code=553, the same check sends 553 5.1.8, not 553 4.1.8. In smtpd_check_reject, after the reply text is built, the source comment reads "In any case, enforce consistency between the SMTP code and DSN code. SMTP has the higher precedence since it came here first." The next statement copies the first digit of the SMTP code over the first digit of the enhanced status, so the passed 4.1.8 becomes 5.1.8. The same rule turns 550 into 5.1.8. A search for 553 5.1.8 Sender address rejected: Domain not found therefore lands on this same check with a permanent code. The source is smtpd_check.c at tag v3.9.1, function smtpd_check_reject. The temporary-DNS path passes 450 itself, so it stays 450 4.1.8 whatever the parameter says.
What the symptom means
reject_unknown_sender_domain is documented in postconf(5): reject the request when Postfix is not the final destination for the sender address, and the MAIL FROM domain has no DNS MX and no DNS A record, or a malformed MX record such as a record with a zero-length MX hostname (Postfix 2.3 and later). The reply uses unknown_address_reject_code (default 450). A null MX, from Postfix 3.0, is a different reply: the source passes 550 with 4.7.27, so by the consistency rule above the client sees 550 5.7.27, and the text says the domain does not accept mail.
The source comment on the lookup is "fail if name has no A, AAAA or MX record". In the source, RR_ADDR_TYPES is T_A, T_AAAA when the build defines T_AAAA. The postconf sentence names MX and A. Treat a domain that has only AAAA as something to test with dig, not as a case the manual page spells out.
Two paths share the words Domain not found and the status 4.1.8:
- The lookup is not a retry. The numerical code is
unknown_address_reject_code. The default is 450. - The lookup is a temporary DNS failure (
DNS_RETRY). The source uses 450 directly, andunknown_address_tempfail_action(defaultdefer_if_permit) decides whether Postfix keeps looking for a reason to reject.
A malformed reply uses the text Malformed DNS server reply instead of Domain not found. If your bounce says Domain not found, it is the not-found path or the temporary path, not the malformed-reply path.
postconf(5) says not to change unknown_address_reject_code unless you have a complete understanding of RFC 5321. Leaving it at 450 keeps the rejection temporary.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| The sender domain has no MX and no A | 450 4.1.8, and dig shows neither | Query MX and A from the Postfix host |
| The DNS lookup failed temporarily | The same 450 4.1.8, and a later dig succeeds | Repeat the query. The retry path hard-codes 450 |
reject_unknown_sender_domain is in smtpd_sender_restrictions |
The reply comes at RCPT TO by default (smtpd_delay_reject), at MAIL FROM only when that is set to no |
postconf -n shows the restriction |
| The domain is a final destination for this Postfix | The restriction does not apply | postconf: the check runs when Postfix is not the final destination for the sender address |
| An administrator set the code to 550 or 553 | The text matches, but the reply is 550 5.1.8 or 553 5.1.8, not 450 4.1.8 |
postconf -n shows unknown_address_reject_code |
Prove the cause before changing anything
All of these are read-only.
1. Read the restriction and the code. postconf(1) shows explicit main.cf settings with -n, and defaults with -d:
postconf -n
postconf -d unknown_address_reject_code
The default of unknown_address_reject_code is 450. smtpd_sender_restrictions defaults to empty. The access readme's example sets it to reject_unknown_sender_domain.
2. Query the sender domain. The dig manual takes a name and a type. MX and A are types it names:
dig example.com MX
dig example.com A
Run these on the Postfix server. A record that your laptop sees, and this server does not, is a resolver problem on the mail host.
3. Read the log line with the reply. In the source, the reject is logged by log_whatsup as a line that starts with the queue ID, or NOQUEUE when no queue ID exists yet, then reject:, the name of the SMTP command that was being answered (state->where), from, the client name and address, and the reply text. postconf(5) gives smtpd_delay_reject the default yes: Postfix waits until the RCPT TO command before it evaluates smtpd_sender_restrictions. A default install therefore logs NOQUEUE: reject: RCPT from, and only a server with smtpd_delay_reject = no logs reject: MAIL from. Search the mail log for Sender address rejected: Domain not found, which appears in both cases, and read the command name before from in the line you find. A temporary DNS failure and a missing domain give the same text, so repeat the dig queries before you decide.
Fix
There are two different fixes. Use the first when the sender domain should exist, and the second only when you have decided to accept mail from domains that do not resolve.
Fix 1: the sender domain has no MX or address record
The zone of the sender domain is usually not yours, so the change is made by the owner of that domain, or by you if the domain is yours. Save the records that exist now. Each answer goes to its own file:
dig <sender-domain> MX > mx-before.txt
dig <sender-domain> A > a-before.txt
dig <sender-domain> AAAA > aaaa-before.txt
Risk: the next step adds or changes a record in the DNS zone of the sender domain. Every receiver that looks up that domain, not only this Postfix server, sees the new record once its cache expires, and a wrong MX sends the domain's mail to the wrong server.
Ask the owner of the zone, or edit it yourself if it is yours, to publish an MX record, or an A record, that points at the host that really handles the domain's mail. Re-query with the dig commands above until the answer appears from the Postfix host.
To undo it: if you changed an existing record, put back the value that the matching saved file shows. If the saved file showed no record, delete only the record you added.
Fix 2: stop using the check
First find which restriction list holds reject_unknown_sender_domain. This is read-only:
postconf -n | grep reject_unknown_sender_domain
The line that prints starts with the parameter name, for example smtpd_sender_restrictions. The rest of this section calls that parameter <restriction-parameter>. If nothing prints, the restriction is not set in main.cf, and this fix does not apply.
Save the current value of that parameter. The answer goes to its own file:
postconf -n <restriction-parameter> > restriction-before.txt
Risk: the next step edits main.cf and reloads Postfix. It stops the unknown-sender-domain check for every sender. Mail from domains with no MX and no A will no longer be refused for that reason. Setting the whole list empty would also remove every other restriction on it, so the command below keeps the rest of the saved list.
Set the parameter to the saved list without reject_unknown_sender_domain. postconf(1) edits main.cf with -e and name=value pairs, and the manual says to use quotes when the value contains spaces:
postconf -e '<restriction-parameter>=<saved list without reject_unknown_sender_domain>'
postfix reload
postfix reload re-reads the configuration. Running processes terminate at their earliest convenience.
To undo it: run postconf -e '<restriction-parameter>=<saved list>' with the exact value that restriction-before.txt holds, then postfix reload.
Do not set unknown_address_reject_code to 550 to "clear" a 450. That turns a temporary miss into a permanent reject. postconf tells you not to change it without understanding RFC 5321.
Example (illustrative): a partner sends from news.example.net. Postfix answers 450 4.1.8. dig news.example.net MX from the mail server returns no MX and no A, while a query an hour later returns an MX. The lookup was a temporary failure. The administrator leaves the code at 450 and does not remove the restriction. The partner's next attempt succeeds.
Confirm the fix
postconf -nshows the restrictions you meant to keep.- From the Postfix host, the sender domain has an MX or an A record.
- A new message from that sender is no longer refused with
Sender address rejected: Domain not found. A later 450 with the same text means the lookup failed again.
What to watch afterwards
- A domain that expires, or loses its MX, will start failing again. The check is doing what it was set to do.
- Temporary DNS failures use the same sentence as a missing domain. Look at a second dig before you delete the restriction.
- After you edit
main.cf, runpostfix reload. postfix(1) says the reload command re-reads configuration files and that running processes terminate at their earliest convenience.
Read next
Related articles you may want next.
- TroubleshootingPostfix 550 5.1.1 User unknown: local recipient table or virtual mailbox tablePostfix rejected a recipient with 550 5.1.1 User unknown. See whether the table is local or virtual, then add the address or relax the reject code only while you check the map.Read article
- TroubleshootingPostfix: Host or domain name not found. Name service errorPostfix logged Host or domain name not found. Name service error. Read the name and record type in the log, then compare dig on the mail server with the DNS it should be using.Read article
- TroubleshootingPostfix 554 5.7.1 Relay access denied: who may send through the serverPostfix 554 5.7.1 Relay access denied: check mynetworks, SASL authentication and relay_domains, and fix it without turning the server into an open relay.Read article
Risks and limits
- The enhanced status is
4.1.8only while the SMTP code is 4xx. With 550 or 553 the first digit follows the SMTP code and the reply is5.1.8. - postconf's sentence names MX and A. The source also queries AAAA when
T_AAAAis defined. If a domain has only AAAA, test it. Do not assume the manual page's wording lists every address type. reject_unverified_senderis a different restriction fromreject_unknown_sender_domain, and its default code is also 450.
Sources
- Postfix Configuration Parameters — Postfix, no date shown, accessed 22 November 2026
- postconf(1) — Postfix, no date shown, accessed 22 November 2026
- postfix(1) — Postfix, no date shown, accessed 22 November 2026
- Postfix SMTP relay and access control — Postfix, no date shown, accessed 22 November 2026
- smtpd_check.c — Postfix tag v3.9.1, no date shown, accessed 22 November 2026
- smtpd_dsn_fix.h — Postfix tag v3.9.1, no date shown, accessed 22 November 2026
- BIND 9 manual pages: dig, version 9.20.22 — ISC, no date shown, accessed 22 November 2026
This article was originally published on .