Fixing the 550 No Such User Here email error
- Mail file permissions are not readable or are incorrect.
- The email address was typed incorrectly.
- MX records are incorrect ( pointing to the wrong server ).
- Email does not route correctly ( Remote / Local domains ).
This error can go both ways, meaning, people sending to your server may get the error and when you send from your server to another you may get the error. Depending on where the error bounce is generated from will determine what you can do about fixing the error.
If you get "550 No Such User Here" bounces sending from your server to another server, you most likely will need to contact the host or email administrator of the server you are emailing to fix it.
If you are getting complaints that people sending to your server are getting this bounce, you can check / change the settings on your servers end. Below are the reasons why the 550 error may occur when you email.
Mail file permissions are not readable or are incorrect
[root@vps#### ~]$ fixperms userna5
This will reset all your file and folder permissions to folders 755 and files 644 for teh cPanle user userna5. If the email bounce is coming to you when you send to another server and it's permissions related, the person you are emailing will need to contact their hosting provider to fix the permissions on their end.
The email address was typed incorrectly
MX records are incorrect ( pointing to the wrong server )
[root@vps#### ~]$$ dig your-domain.com mx ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.6 <<>> your-domain.com mx ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8149 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3 ;; QUESTION SECTION: ;your-domain.com. IN MX ;; ANSWER SECTION: your-domain.com. 14400 IN MX 0 your-domain.com. ;; AUTHORITY SECTION: your-domain.com. 54747 IN NS ns2.inmotionhosting.com. your-domain.com. 54747 IN NS ns.inmotionhosting.com. ;; ADDITIONAL SECTION: your-domain.com. 13322 IN A 220.127.116.11 ns.inmotionhosting.com. 11994 IN A 18.104.22.168 ns2.inmotionhosting.com. 11994 IN A 22.214.171.124
The example above shows that domain your-domain.com points to the ns.inmotionhosting.com and ns2.inmotionhosting.com nameservers and that the MX routes to the InMotion Hosting server.
Make sure your nameservers are pointing to us. If your nameservers do not point to our server, then your domain will not route to our server unless you make special DNS changes at the host the nameservers point to.
Make sure the MX records for your domain are sending to the correct server. If your domain does point to the correct server, check the MX records to see if the email is pointing to the correct server in the cPanel MX entry.
If your nameservers and DNS are correct, then you will need to check the email routing. If the bounce message is from you sending to another server, then the person receiving the email will need to check with their email provider for a resolution.
Email does not route correctly ( Remote / Local domains )
To find out if your domain is on the receiving email servers DNS nameserver, you can DIG the domain for their nameservers. Once you get the nameservers for the receiving domain, you can check the DNS for your domain using their nameservers. Below will explain in detail.
Dig the receiving server domain to find the nameservers:
Below shows what a DNS MX record DIG looks like for notyourdomain.com.
[root@vps#### ~]$ dig notyourdomain.com mx ; <<>> DIG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.6 <<>> notyourdomain.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8587 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;notyourdomain.com. IN A ;; ANSWER SECTION: notyourdomain.com. 14400 IN MX 0 notyourdomain.com. ;; AUTHORITY SECTION: notyourdomain.com. 85619 IN NS ns1.somenameserver.com. notyourdomain.com. 85619 IN NS ns2.somenameserver.com. ;; ADDITIONAL SECTION: notyourdomain.com. 13322 IN A 126.96.36.199 ns2.somenameserver.com. 18391 IN A 188.8.131.52 ns1.somenameserver.com. 18391 IN A 184.108.40.206 ;; Query time: 1 msec ;; SERVER: 220.127.116.11#53(18.104.22.168) ;; WHEN: Thu Mar 7 06:08:06 2013 ;; MSG SIZE rcvd: 136
The results of this DIG shows that the nameservers for the receiving server notyourdomain.com has the nameservers of ns1.somenameserver.com and ns2.somenameserver.com. The MX record points to notyourdomain.com which has an IP that points to the server the nameservers are on. Next you can check your domain in the receiving server nameservers.
Checking if your domain is in another servers DNS:
Now that you have the receiving server nameservers for the notyourdomain.com domain, you can DIG the DNS records at the receiving servers end to see if your domain is in their DNS nameserver. The following is an example of the DIG command in shell that will look up your-domain.com on the notyourdomain.com server.
dig @ns1.somenameserver.org absolutewebdev.com ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.6 <<>> @ns1.somenameserver.org your-domain.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11023 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;your-domain.com. IN A ;; ANSWER SECTION: your-domain.com. 14400 IN A 22.214.171.124 ;; AUTHORITY SECTION: your-domain.com. 86400 IN NS ns2.somenameserver.org. your-domain.com. 86400 IN NS ns1.somenameserver.org. ;; ADDITIONAL SECTION: ns1.somenameserver.org. 14400 IN A 126.96.36.199 ns2.somenameserver.org. 14400 IN A 188.8.131.52 ;; Query time: 66 msec ;; SERVER: 184.108.40.206#53(220.127.116.11) ;; WHEN: Fri Mar 8 06:16:18 2013 ;; MSG SIZE rcvd: 140
The previous response shows that your-domain.com is in the DNS on the notyourdomain.com server. This means that the emails sent to notyourdomain.com are seeing your-domain.com in their DNS, looking for the email address on the notyourdomain.com server, and rejecting it because there is no email address on the server.
To fix this, you will need to contact the hosting company or the domain owner that you are sending to, telling them that your emails cannot go through to their server because your domain is in their DNS. They will ned to "Kill the DNS", change the routing to remote on the receiving server, or remove your domain from their DNS nameserver.
If your domain is not in their DNS nameserver:
If your-domain.com was NOT found in the nameserver on the receiving server you will get the following not found response.
dig @ns1.inmotionhosting.com google.com ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.6 <<>> @ns1.inmotionhosting.com google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 63529 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;google.com. IN A ;; Query time: 0 msec ;; SERVER: 18.104.22.168#53(22.214.171.124) ;; WHEN: Fri Mar 8 06:20:03 2013 ;; MSG SIZE rcvd: 28
In this case, you can try checking your email routing. If you are sending from your server with us, you will need to set the email routing to local in your MX entry of your cPanel. If you are using a 3rd party application like Google APPs, you will need the routing set to remote.
If this does not fix the problem, then you will want to contact tech support to find out if there is a routing issue with your DNS.
Support Center Login
Social Media Login
2014-10-11 4:12 am
I am getting the following error: :
This is the mail system at host outbound.mailhostbox.com.
I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can delete your own text from the attached returned message.
The mail system
<firstname.lastname@example.org>: host augur-me.com[126.96.36.199] said: 550 No Such
User Here (in reply to RCPT TO command)
Please provide the solution.
2014-10-12 4:22 pm
Did you try the instructions above to fix your error? If so, and you are still getting the error, you may need to contact your hosting company. The dig records are showing your domain is with GoDaddy. You may need to contact them if you are certain you have gone over the instructions and the email address exists on the server.
2015-07-06 11:06 am
kindly assist me am getting this erro ; 550
550 This domain is not hosted here please help
2015-07-06 4:05 pm
That error means the domain you are trying to send an email to does not exist on the server.
2014-12-06 11:36 am
1. I can send and receive e-mail from my Outlook 2010 account: email@example.com
2. I have four other Outlook accounts. I can not send e-mail to my real-cos email address from any of them. I receive an immediate "550 no such user here" message.
3. I receive e-mails forward from my real-cos account to my rcngroup account in Outlook 2010.
4. I do not receive e-mails to my Outlook based or webmail real-cos from my yhaoo account or from contact forms on my webstsites.
Will app reciate your assistance.
2014-12-08 2:11 pm
Very happy to report that this issue was resolved with the help of Aaron at Inmotion support. Too much for me to fully understand or explain which is why I am grateful for the quick, knowledgeable assisatance. Many thanks!
2015-06-29 3:06 am
Mails not working
Delivery to the following recipient failed permanently: firstname.lastname@example.orgTechnical details of permanent failure:Google tried to deliver your message, but it was rejected by the server for the recipient domain gtholidays.in by mail.gtholidays.in. [188.8.131.52].The error that the other server returned was:550 <email@example.com> No such user here----- Original message -----DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gtholidays.in; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=egxIjJUqoZvo4LvxUUPbXxed6XBvy9zfm89rN0uvdw8=; b=NggyCIirYstaiiCtWnZUhZ+mOH5iv/V4pzSlTK/orP/ftTR/FHHk5z3a7pkLHQAx/y XaxxFzhUAxbAk6ye/amqsLdKlsuQgA5M6yRWcRYlkQWf7BLQUv3gk17xW9fgJwFF1p92 AVOfbbTZ2ZSKS2l7O5oBj+jlHWdq9TWjAk0jQ=X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=egxIjJUqoZvo4LvxUUPbXxed6XBvy9zfm89rN0uvdw8=; b=V17SFIhPJlQWTfxE1WjjugXyw8d66B7nJJ9QqdSWw7Jh948Toy2C+bXZmezA75WsFk 7NcDpVxYYqiOTesIWGOifU2Kt6LB6qa+a3QbHh5V3S+7FySgB3JMxRlTncpSslk4l9Ct ET0NBXmH/bJs37w/1fVxscLxJoBKxmh1aDgXPgNPrfm7gY/G2Hp+crXg8zHh8aLMoxgd Kos2UkELSBqR58RiacfTG0R2/eTlDbZoCZrqNARjP8w7aOSHsiIkFB1HHhKbBOQhD2a2 C0qIFgyZrpO2WZfI5gHa6UfdgPtctbvKZHfRRDiAVNpp+NZkyhoHqETAnZUxdwDBmpUN 5Xwg==X-Gm-Message-State: ALoCoQmwPAkXqsPWXOljZAnb2G0/uH9Epk8c+SUwJZwem0x00s13YXC7B2stfcwKTLc0tNdxZwbqMIME-Version: 1.0X-Received: by 10.152.25.227 with SMTP id f3mr12386065lag.67.1435561260898; Mon, 29 Jun 2015 00:01:00 -0700 (PDT)Received: by 10.114.22.132 with HTTP; Mon, 29 Jun 2015 00:01:00 -0700 (PDT)X-Originating-IP: [184.108.40.206]In-Reply-To: <CADAPHL-Xy5ioJUPod6NASfr79dqb1N7s8_iHXEjW69ZRtUQr1A@mail.gmail.com>References: <CADAPHL8x_i2h3wrWx8xz=29UbnoGo60gXL8WTcoVWNCSpMGCKw@mail.gmail.com> <CADAPHL-Xy5ioJUPod6NASfr79dqb1N7s8_iHXEjW69ZRtUQr1A@mail.gmail.com>Date: Mon, 29 Jun 2015 12:31:00 +0530Message-ID: <CADAPHL-0rERCKe0PpL126pdWo_5s=+Y_=kdnD5H05C9CihyS8Q@mail.gmail.com>Subject: Re: testFrom: "GT Holidays (P) Ltd" <firstname.lastname@example.org>To: Suresh Elangovan <email@example.com>Content-Type: multipart/alternative; boundary=089e0160bc440272300519a2a739emptyOn Mon, Jun 29, 2015 at 12:30 PM, GT Holidays (P) Ltd <firstname.lastname@example.org>wrote:> test>> On Mon, Jun 29, 2015 at 12:30 PM, GT Holidays (P) Ltd <email@example.com>> wrote:>>> test>>>>
2015-06-29 1:42 pm
It appears you are getting this error when trying to send the email to another server. You will want to check out our article aboce, but the most relevant information from that article is below:
"If you get "550 No Such User Here" bounces sending from your server to another server, you most likely will need to contact the host or email administrator of the server you are emailing to fix it."