mail.google.com is currently unreachable.

SMTPPING can be used for sending a test message.You will want to review the mail logs and/or Message Tracking to see if reasons for possible rejections are shown. If the connectivity tests return a rejection then additional troubleshooting may be required. If the telnet returns Connected and a 220 banner then you can retry delivery using the delivernow all command, or from the GUI you can navigate to Monitor > Delivery Status and click Retry All Delivery. If the host is unreachable, we can first check for the DNS MX records using dig and then test connectivity using telnet. delivery routed through an incorrect interface or IP address of the interface is not properly NAT/routed through the firewall) Step 3 - Testing SMTP Connectivity connection refused or no route to host) or the SMTP conversation is timing out Up - Reachable and actively accepting messagesĭown - Positively down (e.g. Some examples of the Host up/down status and what it may mean (not all-inclusive):

Status as of: Thu Aug 13 14:37:17 2020 EDTįrom the GUI, this can also be seen under Monitor > Delivery Status. More information on the output can be found: here. Step 2 - Verify the Host Status of a Destination Domainįrom the CLI, you can utilize the hoststatus command combined with the domain in question to review the Host up/down state. Bounced Bouncedįrom the GUI, you can navigate to Monitor > Delivery Status. Hosts marked with '*' were down as of the last delivery attempt. Active Recipients will signify the number of messages held waiting to be delivered. Step 1 - Verify the Number of Messages Pending Deliveryįrom the CLI, you can utilize the tophosts command sorted by Active Recipients to review items sitting in the delivery queue. The steps below will go over the process for taking a closer look at messages queued for delivery and troubleshooting SMTP connectivity. This could be for a variety of reasons, but commonly because the ESA is unable to reach the destination host and/or the messages are being throttled or rejected by the next-hop MTA. This means that the message has been processed by the ESA, but that for some reason the ESA is unable to complete delivery of the message to the next-hop MTA. When troubleshooting issues concerning email delivery, you may see in the Message Tracking or mail logs that the last state of a message shows queued for delivery. For Cloud Email Security (CES) customers, more info on CLI access can be found here.This document describes the actions that can be taken for troubleshooting emails that are queued for delivery aka held on an Email Security Appliance (ESA) and pending to be delivered.

Mail.google.com is currently unreachable.