Expand all | Collapse all

Clients can't email host

  • 1.  Clients can't email host

    Posted 13 days ago
    Our Server IP is cleaned, no spamming on the IP found/No issues. All records are correct however we're still seeing emails from the domain/ip sent to the below getting timed out/failing. Our client thinks its us. I've checked our IP in the PBL as well as on Symantec's site, found no issues.

    IP Address is

    Sample of the bounced messages are below.
    Delay reason: []:
    SMTP error from remote mail server after RCPT TO:<>:
    421 Service Temporarily Unav

    No action is required on your part. Delivery attempts will continue for some
    time, and this warning may be repeated at intervals if the message remains
    undelivered. Eventually the mail delivery software will give up, and when
    that happens, the message will be returned to you.

  • 2.  RE: Clients can't email host

    Posted 12 days ago
    I can see that the MX records for are set up correctly as;
    • 10 -
    • 20 -
    That should mean that the client should send to the top record,, but the error message seems to imply that they are sending to That server is a deliberate trap for spammers that will often try to send to the lowest priority route in the hope that they can bypass security measures. If the client sends to the top MX record then the email should be successfully delivered.

  • 3.  RE: Clients can't email host

    Posted 12 days ago
    Hi, how does one sending an email choose where to send to?

    our client is simply sending an email to , where/how can they select choose where it goes on the backend? you're saying my client is using instead of

    let me know what we the hosting provide/my client the person trying to email needs to do to ensure messages we send go through

    same client is also receiving the same errors sending to
    host []
    SMTP error from remote mail server after RCPT
    421 Service Temporarily Unavailable: retry timeout exceeded

    Im guessing the same issue.

  • 4.  RE: Clients can't email host

    Posted 12 days ago
    The issue will be with whatever setup the sender has for outbound mail, presumably a mail server. That should always send to the primary MX record for a given domain, but it is sending to the secondary. That should only happen if the primary is unavailable, but our infrastructure is global and high availability so that should never happen. I'm sorry, I don't know anything about mail server setup or why that server may be picking the secondary MX record to send to, but that is where the problem lies. Note that any cluster#a record is a honey trap for spammers and will fail.

  • 5.  RE: Clients can't email host

    Posted 12 days ago
    So you're saying the sender has to change their records to fix this issue with getting mails to the correct MX for these recipients?  especially when they have no issues emailing anyone but 2 clients who's bounceback are both showing messagelabs error?

    Do you have any suggestions of what should be changed at the senders end in order for them to email these 2 domains and hit the correct

    We will check the senders records to verify. can you please confirm these IP's aren't blocked at your end and We checked the Symantec reputation and both show no issues but reading through your forums, I've seen you check the ips to see if they're blocked.

  • 6.  RE: Clients can't email host

    Posted 12 days ago
    The records are set up correctly. Those IPs aren't blocked, the issue is at the senders end. The client mail server is trying to send an email, looking up the recipient domain in DNS and choosing the secondary MX record as the destination instead of the first. That is where the issue lies.

    It may be worth the customer checking the routing from their mail server to to see if it is accessible. If that cannot be reached for some reason then the default action for the mailserver is that it should use the secondary server, which will just result in the error they are seeing.