Fortinet FortiMail-100, Install Manual

Page: 162 / 174

Troubleshooting tools Testing the installation
FortiMail™ Secure Messaging Platform Version 4.0 Patch 1 Install Guide
162 Revision 2
http://docs.fortinet.com/ • Feedback
If the host is not reachable, you can use traceroute to determine the router hop or host at
which the connection fails:
FortiMail-400 # execute traceroute 192.168.1.10
traceroute to 192.168.1.10 (192.168.1.10), 32 hops max, 72 byte
packets
1 192.168.1.2 2 ms 0 ms 1 ms
2 * * *
For more information on CLI commands, see the FortiMail CLI Reference .
Nslookup
It is critical that FortiMail has good access to DNS services to properly handle SMTP
sessions and apply antispam scans, including FortiGuard Antispam. If DNS queries fail,
they will be recorded in the event log.
Figure 56: Event log when DNS queries fail
If a DNS query fails or resolves incorrectly, you may want to manually query your DNS
server to verify that the records are correctly configured. You can do this from the FortiMail
unit using CLI commands.
For example, you might query for the mail gateway of the domain example.com
(commands that you would type are highlighted in bold; responses from the FortiMail unit
are not bolded):
FortiMail-400 # execute nslookup mx example.com
example.com mail exchanger = 10 mail.example.com.
or query to resolve mail.example.com and antispam.fortigate.com (the domain name of a
FortiGuard Distribution Network server) into IP addresses:
FortiMail-400 # execute nslookup host mail.example.com
Name: mail.example.com
Address: 192.168.1.10
FortiMail-400 #
execute nslookup host antispam.fortigate.com
Name: antispam.fortigate.com
Address: 212.95.252.120
Name: antispam.fortigate.com
Address: 72.15.145.66
Name: antispam.fortigate.com
Address: 69.90.198.55
For more information on CLI commands, see the FortiMail CLI Reference .