“Referral was returned from the server” is an error message that appears when an email server rejects a message because it has been referred to another server, usually due to a misconfigured mail relay or an authentication issue. The fix typically involves checking your outgoing mail server settings, verifying authentication, or updating the server address to the correct one. This article explains what the error means, why it happens, and how to resolve it.
What Does “Referral Was Returned from the Server” Mean?
This error is most commonly seen in email clients like Microsoft Outlook, Thunderbird, or mobile mail apps when they try to send an email through an SMTP (Simple Mail Transfer Protocol) server. The server responds with a referral code (often a 3xx response like 354 or a custom message) that tells the client to try a different server or path. However, if the client cannot follow that referral—because it’s not configured to do so—it displays the error and fails to send the message.
In simpler terms, the server is saying, “I’m not the right one to handle this; go talk to that other server.” But your email program doesn’t know how to do that, so it gives up and shows the error.
Common Causes of the Error
Several misconfigurations can trigger this error. The most frequent include:
- Wrong SMTP server address – You might be using an outdated or incorrect server name (e.g., smtp.oldprovider.com instead of smtp.newprovider.com).
- Authentication required but not enabled – Many SMTP servers require you to log in with your full email address and password. If “Use Authentication” is unchecked, the server may refer you elsewhere.
- Port or encryption mismatch – Using the wrong port (e.g., 25 instead of 587) or the wrong encryption method (SSL vs. TLS) can cause the server to issue a referral.
- Relay restrictions – The server may only allow relaying for specific domains or IP addresses. If yours isn’t allowed, it might refer you to a different relay.
- Multiple MX records – In rare cases, the domain’s mail exchanger (MX) records point to multiple servers, and the one you’re contacting wants you to use another.
How to Fix the Error
Follow these steps in order, as they go from most common to least common fixes:
- Check your SMTP server address – Look up the correct outgoing mail server for your email provider (e.g., smtp.gmail.com for Gmail, smtp.office365.com for Microsoft 365). Update it in your email client’s account settings.
- Enable authentication – In your email client, find the “Outgoing Server” or “SMTP” settings and make sure “Require authentication” is checked. Use the same username and password as your incoming mail.
- Verify the port and encryption – Most modern SMTP servers use port 587 with STARTTLS, or port 465 with SSL. Port 25 is often blocked or restricted. Try switching to 587 and enabling STARTTLS.
- Check your relay permissions – If you’re using a corporate or university email server, contact your IT department. They may need to add your IP address or authenticate you before allowing relaying.
- Test with a different client – Try sending the same email from a webmail interface (like Gmail in a browser) or a different email app. If it works there, the problem is in your client’s configuration.
- Update your email client – Outdated software may have bugs that prevent it from following server referrals. Install the latest updates and restart the app.
How Email Referrals Work
Email referrals are part of the SMTP protocol. When a client connects to a server, the server can respond with a “referral” (a 3xx code) that includes the address of another server. This is often used in load-balancing or when a domain has multiple mail servers. For example, if you send to user@example.com and example.com has two MX servers, the first one might say, “I’m busy, try the second one.” Most email clients handle this automatically, but some don’t, especially if the referral is for a different domain or requires a new connection.
In practice, this is rare because most servers are configured to accept mail directly. But when it happens, you see the error.
Common Misconceptions
One common myth is that this error means your email was blocked as spam. That’s not true—it’s a technical routing issue, not a content-based rejection. Another misconception is that changing your password will fix it. Unless the password is wrong, it won’t. The error has nothing to do with your inbox being full or your account being suspended.
Some users also think that using a VPN or changing their DNS settings will help. In most cases, it won’t, because the problem is in the SMTP configuration, not your network.
When to Contact Your Email Provider
If you’ve tried all the steps above and still get the error, it’s time to contact your email provider’s support team. Provide them with the exact error message, the time it occurred, and the SMTP server address you’re using. They can check their server logs to see why the referral is being issued.
This is especially important if you’re using a custom domain email (like yourname@yourcompany.com) because the issue might be on the domain’s DNS settings. A misconfigured MX record can cause the server to refer you to a non-existent host.
Frequently Asked Questions
Why do I see “Referral was returned from the server” only when sending to certain recipients?
This can happen if the recipient’s domain has multiple MX records and your server tries to use a different one. It’s not a problem with your settings—it’s a routing quirk. Try resending the email; sometimes it goes through on the second attempt.
Does this error mean my email was sent?
No. The error occurs before the email is accepted by the server, so the message is not sent. Check your “Sent” folder to confirm; if it’s not there, the email was not delivered.
Can I bypass the referral by using a different port?
Sometimes. If your server is configured to use port 25 and the referral is due to relay restrictions, switching to port 587 (submission) may help because that port is specifically for authenticated mail submission.
Will clearing my email client’s cache fix this?
Unlikely, but it doesn’t hurt. The error is a server response, not a local cache issue. However, if your client has stored an old server address, clearing cache and re-adding the account can help.
Is this error related to my internet connection?
No. The error comes from the email server, not your network. If you can browse the web, your internet is fine.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Microsoft Surface Duo: The Foldable Phone Story
- Samsung SM-T813 Hard Reset: Step-by-Step Guide
- Mafia Clash Codes: Real Meanings & Usage
- Remove Programs from Mac: Full Uninstall Guide
- Project Sentinel Morning Digest: Data Stack Failure Alerts
- Best KVM VPS Hosting: Top Picks & Guide