"No such recipient here" Error

This error occurs when sending email to an address that the server believes should exist locally but doesn't. It's one of the most common issues during domain migration to MXroute.

When This Error Happens

You'll typically see this error in these scenarios:

• During migration: You've just added your domain to MXroute but haven't created all email accounts yet
• Between domains on same account: Sending from one domain to another when both are in your MXroute account
• Testing before migration: Attempting to test email delivery before completing your move to MXroute

Why It Happens

When you add a domain to DirectAdmin, MXroute's servers immediately consider themselves authoritative for that domain's email. This means:

1. The server checks if the recipient domain is in its local domain list
2. If yes, it attempts local delivery (ignoring MX records)
3. If the recipient mailbox doesn't exist locally, it returns "No such recipient here"

The server won't check external MX records or attempt delivery elsewhere once it recognizes the domain as local.

Solutions

If You're Still Migrating

Option 1: Complete the migration first

• Finish creating all necessary email accounts
• Complete your domain migration
• Then test email delivery

Option 2: Temporarily disable local routing (if you must test now)

1. Go to DirectAdmin → Email Routing
2. Select your domain from the dropdown
3. Uncheck "Use this server to handle emails for [domain]"
4. Important: Remember to re-enable this after updating your MX records

If the Domain Won't Receive Mail on MXroute

If you're only using MXroute for sending, or this domain receives mail elsewhere:

1. Go to DirectAdmin → Email Routing
2. Select the domain from the dropdown
3. Uncheck "Use this server to handle emails for [domain]"
4. Leave it unchecked permanently

Critical Warning

If you disable local email routing temporarily for testing:

• You must re-enable it after pointing your MX records to MXroute
• Failing to do so will cause all incoming email to be rejected
• Set a reminder to reverse this setting after migration

Best Practices

1. Complete setup before testing: Create all email accounts before sending test messages
2. Migrate systematically: Move all related domains together to avoid cross-domain issues
3. Document your changes: Keep track of any routing modifications you make

Related Issues

If you forget to re-enable local routing after migration, you may encounter:

• Incoming emails being rejected
• "MXroute is blocking our email" complaints
• Delivery failures from external senders

Always verify your Email Routing settings match your actual mail hosting configuration.