Error: "User isn't located here" (550 5.1.1)

Created by Alice Joynson-Ellis, Modified on Sun, 15 Nov at 7:22 PM by Curtis Hammock

When someone attempts to send an email to your Purelymail domain, the sender may receive a Non-Delivery Report (NDR bounce notice) with the following error:

550 5.1.1 <recipient@yourdomain.com>: Recipient address rejected: User isn't located here

What This Error Means

This rejection occurs when Purelymail's incoming mail servers accept a connection for your domain but cannot find any active mailbox, alias, catch-all rule, or prefix routing rule that matches the recipient address.


Common Causes & How to Fix

  1. Typo in Recipient Address:

    Check the bounce notice to verify the exact spelling before the @ sign. If the sender misspelled your address, have them resend to the correct mailbox name.

  2. Mailbox Not Yet Created:

    Ensure a user mailbox exists for that address under Users in the Account Admin portal (see How to Create and Manage Users (Mailboxes)).

  3. Full Email Address Entered in Routing Rule Match Field:

    When creating a routing rule under Routing > Add New Rule, enter only the username portion (e.g. sales) into the match field. If you enter sales@yourdomain.com, Purelymail attempts to match sales@yourdomain.com@yourdomain.com, which never matches and causes a 550 5.1.1 bounce (see How to Create Email Aliases & Forwarding Rules).

  4. Missing Catch-All Rule:

    If you want your domain to accept messages sent to any unassigned address, configure a catch-all rule under Routing by setting Match to Any address except valid user addresses (catchall) (see Setting Up Catch-All Rules and Domain Prefix Routing).


Still Need Help?

If you've followed these steps and are still running into trouble, check our Purelymail Support guide.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article