Can I fix a 5.1.4 by changing how I address the email?

Usually not. The conflict is in the recipient’s directory, so the same address will keep failing until their admin removes the duplicate.

Why did this address work last week?

A recent change on their side, such as a new contact object or a sync run, most likely created the second match.

5.1.4 bounce: destination address ambiguous

5.1.4Destination mailbox address ambiguousPermanent: retrying will not help

Typical wording

550 5.1.4 <j.smith@example.com>: Destination mailbox address ambiguous

What it means

X.1.4 is "Destination mailbox address ambiguous" in RFC 3463. The receiving system looked the recipient up and found more than one match, so it refused to pick one. The message did reach the right organisation; it just could not decide which person should get it.

You see it mostly with directory-backed systems: Exchange or Active Directory with two objects that both carry the same proxy address, LDAP lookups that return two entries, or older systems that matched on partial names. In Exchange, duplicate proxy addresses are the classic cause. It is rare on consumer mailbox providers, which enforce unique addresses.

Unlike 5.1.1, the problem is too many matches, not zero. A 4.1.4 can appear when the receiving server treats the conflict as something an admin will fix shortly, in which case the sender retries for a while. Either way, nothing on the sender’s side can resolve it.

Likely causes

Two mailboxes, contacts, or groups in the recipient’s directory share the same email address or proxy address.
A mail-enabled contact was created for a person who also has a mailbox in the same tenant.
A directory sync from on-premises created a duplicate object in the cloud directory.
An LDAP recipient filter matches on a pattern that now returns several entries.

How to fix it

As the sender, forward the bounce to the recipient or their IT team; the duplicate lives in their directory and only they can remove it.
As the recipient’s admin, search the directory for every object holding the address quoted in the bounce, including contacts, groups, and soft-deleted mailboxes.
Remove the address from all but the intended object, then wait for directory sync and address book updates to complete.
Send a test message from an outside account to confirm delivery before telling senders to retry.

Checks that apply

Your domain or sending IP (fills in the checks below)

MX Lookup Identifies the provider hosting the domain, which tells the admin which directory to search for the duplicate.
MailFlow Monitor Sends a monitored test message after the cleanup so you can confirm the address now resolves to one mailbox.

FAQ

Can I fix a 5.1.4 by changing how I address the email?: Usually not. The conflict is in the recipient’s directory, so the same address will keep failing until their admin removes the duplicate.
Why did this address work last week?: A recent change on their side, such as a new contact object or a sync run, most likely created the second match.

All 191 bounce codes