Hi, Thanks for all your response. looks like their DNS MX record not set correctly. Here is the some more answers. > They have not defined an MX record for this doamain - use "nslookup > -q=mx tsgcapital.net" to check MX record(s). What is your DNS server? > Most DNS servers (and all which follow the stardards) can handle this by > falling back to the "nslookup tsgcapital.net" A record but I have > learned that Microsoft DNS (for one) does not handle this properly. > > There are ways around the problem, such as adding a record to your > /etc/hosts file which is not good because the IP could change and you > would never know it, or by having tsgcapital.net add an MX record to > their DNS (which they should do anyway). > > Blaine Owens Because there is no MX record for this domain: dig tsgcapital.net mx ; <<>> DiG 9.2.1 <<>> tsgcapital.net mx ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10713 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;tsgcapital.net. IN MX ;; AUTHORITY SECTION: tsgcapital.net. 10800 IN SOA tsgcapital.net. valentinotrubiani.hotmail.com. 2003073100 28800 14400 3600000 86400 ;; Query time: 2390 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Tue Aug 19 14:39:59 2003 ;; MSG SIZE rcvd: 97 So all mail will queue for 5 days and the get purged, unless they populate an MX record before the 5 days are up.... _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Wed Aug 20 11:18:10 2003
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:18 EST