Several problems:
| arkadix-com.mail.protection.outlook.com |
10 |
This MX has no address, perhaps it is pointing to a CNAME? Run a DNSReport to find out! |
This may be caused by the fact that one or more of your DNS [nameservers] are not responding with a name:
|
WARN
|
TCP allowed |
Not all nameservers responded to queries via TCP. This means that queries that require TCP connections will get inconsistent answers, which can cause delays or intermittent failures. The nameservers that failed TCP queries are:
No Name Provided | 207.46.163.143 |
|
WARN
|
Nameserver software version |
One or more nameservers responded to version queries. This can be considered a breach of security. If a malicious person or program had access to a version-specific exploit for your DNS server, displaying the version info openly will make their attack much easier. This should be removed or obscured. The nameservers that responded to version queries are:
195.5.171.110 responded with "Microsoft DNS 6.1.7601 (1DB14556)"
195.5.171.111 responded with "Microsoft DNS 6.1.7601 (1DB14556)"
|
Therefore, we cannot determine the "A" or HOST RECORD for your MX server.
Remember, you cannot use CNAMES for mail servers, they are PROHIBITED. All MX servers MUST point to an "A" or "HOST" record.
MAIL
|
FAIL
|
All IP addresses public |
|
|
FAIL
|
Connect to mail server |
Using other tools, we are able to see that the PUBLIC IP address for your mail server is: NULL - NOT FOUND
However, that does not properly map to an rDNS IP address,
|
WARN
|
Reverse DNS entries for MX servers |
One or more addresses referenced by MX records do not have a matching reverse DNS entry. This can cause problems for mail deliverability for these servers. Some mail platforms will not accept or will delay email coming from mismatched addresses. The addresses without matching reverse DNS entries are:
195.5.171.110 has arkadix-com.mail.protection.outlook.com. | (null) listed.
195.5.171.111 has arkadix-com.mail.protection.outlook.com. | (null) listed. |
Summary: Setting up and running an e-mail server requires a thorough knowledge of:
the Windows Server 2008 and/or Windows Server 2012 operating systems
IIS
DNS
and all of the new antispam and mail delivery rules and regulations which have been put into place during the last two years.
I would start by making certain your DNS responds properly.
Then check that you have a valid "A" or HOST record pointing the FULLY QUALIFIED DOMAIN NAME of your MAIL SERVER to the IP ADDRESS of your SMARTERMAIL SERVER - right now it appears to point to OUTLOOK.COM [HINT HINT!]
Bruce Barnes
ChicagoNetTech Inc
brucecnt@comcast.net
Phonr: (773) 491-9019
Phone: (224) 444-0169
E-Mail and DNS Security Specialist
Network Security Specialist
Customer Service Portal: https://portal.chicagonettech.com
Website: https://www.ChicagoNetTech.com
Security Blog: http://networkbastion.blogspot.com/
Web and E-Mail Hosting, E-Mail Security and Consulting