SMTP error 4.2.4 Mailing list expansion problem

What SMTP error 4.2.4 means

The address you wrote to is a distribution list, and the system could not work out who is on it. Expansion is the step where one address becomes many, and it failed before any individual recipient was attempted. Reported in the 4 class it is transient, so the message is held and tried again rather than returned, usually alongside 450 or 452. Nothing is wrong with your message or with the list address itself.

Mailbox status
Sent by The mail system that holds the list, at the point it tries to work out the members
Rare

What SMTP error 4.2.4 Mailing list expansion problem actually means

Sending to a group looks like sending to one recipient but is not. The receiving system takes the list address, looks its membership up from a directory, and generates a delivery for each member. This code covers a failure in that lookup: the directory was unreachable, the query timed out, the membership could not be resolved, or the list is in a state that prevents expansion. Because the point of the 4 class is that the sender should try again, expansion is reattempted on the next cycle, which is why most occurrences resolve themselves unnoticed. It is distinct from a list refusing you on policy grounds, where retrying changes nothing.

The mailbox is a mailing list address and the mailing list was unable to be expanded. This code may represent a permanent failure or a persistent transient failure.
— RFC 3463

How 4.2.4 appears in a bounce

A server reporting this condition sends it alongside a three-digit reply code, and a bounce prints the two together. The registry lists these pairings for this status: 450 4.2.4, 452 4.2.4. Which one you get depends on the point in the conversation at which the server refused.

The leading 4 is the server's verdict rather than part of the code's identity: it marks this as a temporary failure, which means the sending server is still retrying.

What causes SMTP error 4.2.4 on a business phone system

The directory holding the membership was unavailableExpansion needs a directory query, and if that service is slow or briefly unreachable the expansion fails rather than delivering to a guessed subset. Recovery is automatic once the directory answers again.
A dynamic distribution group whose filter cannot be evaluatedDynamic groups build membership from an attribute filter at send time rather than from a stored list. A malformed filter, or one referencing an attribute that has been removed, produces an expansion that cannot complete.
Nested groups that cannot be fully resolvedGroups containing groups have to be walked to their leaves. A member group that has been deleted, sits in another directory or has become circular stalls the whole expansion, and the failure is reported against the outer list.
A hybrid setup where the group lives on the other sideIn a hybrid Exchange configuration a group synchronised from on-premise Active Directory may need expanding there. If the connector or synchronisation is unhealthy, expansion fails in a pattern following the synchronisation cycle.
A very large list hitting a resource limitExpanding a list of thousands of members takes time and memory, and under load it can be deferred rather than completed. Repeated deferrals on the same list at busy times point at size rather than at anything broken.

How to fix SMTP error 4.2.4

Give it time before treating it as a faultThis is a transient code and the sending system will retry. A single occurrence that does not repeat needs no action. Investigate when it happens consistently to the same list, or across several lists at once.
Send to one member directly as a testIf a named member receives mail normally while the list address fails, the fault is in the expansion rather than in mail flow or in the sender. That one test tells you where to look.
Inspect the group's membership in the admin centreOpen the group and confirm it lists members as expected. An empty membership, or a nested group showing as unavailable, identifies the problem straight away. For dynamic groups, check the filter still returns who you expect.
Check directory synchronisation health in a hybrid environmentConfirm synchronisation runs to schedule and the group object exists in both directories with matching attributes. Failures that come and go on a predictable cycle are usually synchronisation rather than the group.
Simplify deep nesting and prune very large listsFlatten groups three or four levels deep and remove members that no longer exist. Expansion gets faster and more reliable, and one dead nested group stops taking a working list down with it.

Fixing the underlying problem

This page explains the code. These guides walk through the fix in detail.

Questions about SMTP error 4.2.4

Will some members get the message and others miss it?

Generally not. Expansion failed before the individual deliveries were created, so the message is held as a whole and retried. Partial delivery is possible where a very large list is expanded in batches, so if that is your concern, ask the list owner rather than assuming.

How is this different from being refused permission to post to a list?

This is a mechanical failure to work out who the members are, and it is temporary. Being refused permission is a policy decision, comes back as a permanent security code, and means the list accepts posts only from certain senders. Retrying helps with the first and never the second.

Should the list owner do anything, or will it clear on its own?

Most single occurrences clear as the sending system retries. If it recurs, the owner should check the membership, look for nested groups that no longer exist and confirm any dynamic filter still resolves. Repeated failures on one list trace back to that list rather than the platform.

Related SMTP status codes

Source. SMTP error 4.2.4 Mailing list expansion problem is defined in RFC 3463 and registered in the IANA SMTP Enhanced Status Codes registry. The causes and fixes above are drawn from our own experience supporting UK business email systems.

All Email delivery & SMTP codes