Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
postfix issues 1
- Thread starter 76768
- Start date
-
1
- #2
It means that the mail server you are looking for is either unavailable or the MX records for that server are not properly configured.
Basically DNS problem more than mail server problem.
QatQat
Life is what happens when you are making other plans.
Basically DNS problem more than mail server problem.
QatQat
Life is what happens when you are making other plans.
it can be his dns settings' problem, but it could also be that a remote Mail server's MX record is not configured properly and 76768 may be getting that error when sending mail to it.
QatQat
Life is what happens when you are making other plans.
QatQat
Life is what happens when you are making other plans.
Try:
That should tell you if your DNS request is reaching your DNS server and accurately pulling the MX record for hotmail.com.
When I just did it, I got 8 IP addresses back on 2 mail servers. Plus names for 4 different mail servers.
pansophic
Code:
dig hotmail.com MXThat should tell you if your DNS request is reaching your DNS server and accurately pulling the MX record for hotmail.com.
When I just did it, I got 8 IP addresses back on 2 mail servers. Plus names for 4 different mail servers.
pansophic
- Thread starter
- #6
- Thread starter
- #7
Actually i changed my nameserver ip and got the following from the dig hotmail.com MX command. However i still get the same error. Do i have to setup MX records??? Thanks
;; QUESTION SECTION:
;hotmail.com. IN MX
;; ANSWER SECTION:
hotmail.com. 261 IN MX 5 mx1.hotmail.com.
hotmail.com. 261 IN MX 5 mx2.hotmail.com.
hotmail.com. 261 IN MX 5 mx3.hotmail.com.
hotmail.com. 261 IN MX 5 mx4.hotmail.com.
;; AUTHORITY SECTION:
hotmail.com. 64958 IN NS ns5.msft.net.
hotmail.com. 64958 IN NS ns1.msft.net.
hotmail.com. 64958 IN NS ns2.msft.net.
hotmail.com. 64958 IN NS ns3.msft.net.
hotmail.com. 64958 IN NS ns4.msft.net.
;; QUESTION SECTION:
;hotmail.com. IN MX
;; ANSWER SECTION:
hotmail.com. 261 IN MX 5 mx1.hotmail.com.
hotmail.com. 261 IN MX 5 mx2.hotmail.com.
hotmail.com. 261 IN MX 5 mx3.hotmail.com.
hotmail.com. 261 IN MX 5 mx4.hotmail.com.
;; AUTHORITY SECTION:
hotmail.com. 64958 IN NS ns5.msft.net.
hotmail.com. 64958 IN NS ns1.msft.net.
hotmail.com. 64958 IN NS ns2.msft.net.
hotmail.com. 64958 IN NS ns3.msft.net.
hotmail.com. 64958 IN NS ns4.msft.net.
No you do not necessarily need a DNS server runnning on your server.
Yes you do need correctly configured DNS settings (/etc/resolv.conf) in order to resolve DNS queries and send emails.
OK let's make some clarity here:
The MX records in a domain will point traffic on port 25 (SMTP) to a mail server that receives mail for that domain.
This means that, to send mail out all you need is to be able to find a domain through your DNS resolvers (primary, secondary DNS servers etc..). WHen you send a message to
friend@remotedomain.com
the DNS server that is handling remotedomain.com will have a MX entry to point mail traffic to a mail server handling mail for remotedomain.com. So, to send out mail you need no MX records configuration.
To receive mail instead, when somebody sends mail to you@yourdomain.com, their server will resolve yourdomain.com and query the DNS server that is handling yourdomain.com for a MX record. Once received information about MX records will send mail to your mail server.
This means that, if you are handling the DNS for your domain then you have to worry about configuring MX records. If you use a Domain service from your ISP, or from a Dynamic domain service (DynDNS, Enom, etc...) you have to make sure that the MX records are properly configured there.
Now the question is, are you handling your DNS directly or you are using a provider for that service?
QatQat
Life is what happens when you are making other plans.
Yes you do need correctly configured DNS settings (/etc/resolv.conf) in order to resolve DNS queries and send emails.
OK let's make some clarity here:
The MX records in a domain will point traffic on port 25 (SMTP) to a mail server that receives mail for that domain.
This means that, to send mail out all you need is to be able to find a domain through your DNS resolvers (primary, secondary DNS servers etc..). WHen you send a message to
friend@remotedomain.com
the DNS server that is handling remotedomain.com will have a MX entry to point mail traffic to a mail server handling mail for remotedomain.com. So, to send out mail you need no MX records configuration.
To receive mail instead, when somebody sends mail to you@yourdomain.com, their server will resolve yourdomain.com and query the DNS server that is handling yourdomain.com for a MX record. Once received information about MX records will send mail to your mail server.
This means that, if you are handling the DNS for your domain then you have to worry about configuring MX records. If you use a Domain service from your ISP, or from a Dynamic domain service (DynDNS, Enom, etc...) you have to make sure that the MX records are properly configured there.
Now the question is, are you handling your DNS directly or you are using a provider for that service?
QatQat
Life is what happens when you are making other plans.
- Thread starter
- #9
well, I am assuming that you are leaving your DNS management to DynDNS DNS servers.
I am also assuming that your server is up and reacheable from the Internet.
let's say that your linux box is called linux.mydomain.com and you can see it from outside (i.e. ssh linux.mydomain.com)
In this case, (I am not familiar with DynDNS interface) you should have an applet to configure Mail settings in the DynDNS portal.
a value that would work is exactly the one above
Linux.mydomain.com and with MX value to 10.
Note:
If you cannot reach your server from the internet at all then you may still be experiencing problems with passing your dynamic Ip address to DynDNS.
to verify this ping your domain, write down the numerical IP you will get from your ping probes and the visit
the above page will return your public IP address
Make sure that the two are the same.
QatQat
Life is what happens when you are making other plans.
I am also assuming that your server is up and reacheable from the Internet.
let's say that your linux box is called linux.mydomain.com and you can see it from outside (i.e. ssh linux.mydomain.com)
In this case, (I am not familiar with DynDNS interface) you should have an applet to configure Mail settings in the DynDNS portal.
a value that would work is exactly the one above
Linux.mydomain.com and with MX value to 10.
Note:
If you cannot reach your server from the internet at all then you may still be experiencing problems with passing your dynamic Ip address to DynDNS.
to verify this ping your domain, write down the numerical IP you will get from your ping probes and the visit
the above page will return your public IP address
Make sure that the two are the same.
QatQat
Life is what happens when you are making other plans.
- Thread starter
- #11
My laptop which is where my server was installed to for some reasons just refuse to detect the hard drive. I don't really know what happened; I didn't do anything to it. I will have to figure out what happened so until then i will not be able to escalate the issue with my mail server. Thanks again
- Status