Skip to main content

All hosts for 'domain.com' have been failing for a long time

Comments

12 comments

  • cPanelLauren
    Hello @thepaperdragon The output you posted doesn't seem to include any errors. Do all the domains fail or just the john.diaz@domain.com?
    0
  • thepaperdragon
    Hello @thepaperdragon The output you posted doesn't seem to include any errors. Do all the domains fail or just the john.diaz@domain.com?

    All domain failed or bounce-back. Return-Path: <> Received: from hosting.domain.com by hosting.domain.com with LMTP id 2MSpDvcc31uxLQAAmrBV5Q ; Mon, 05 Nov 2018 00:23:19 +0800 Return-path: <> Envelope-to: john.diaz@domain.com Delivery-date: Mon, 05 Nov 2018 00:23:19 +0800 Received: from mailnull by hosting.domain.com with local (Exim 4.91) id 1gJLBH-000331-57 for john.diaz@domain.com; Mon, 05 Nov 2018 00:23:19 +0800 X-Failed-Recipients: light_walker2005@domain.com, topman99@domain.com, john.diaz@domain.com Auto-Submitted: auto-replied From: Mail Delivery System To: john.diaz@domain.com Content-Type: multipart/report; report-type=delivery-status; boundary=1541348599-eximdsn-1707879264 MIME-Version: 1.0 Subject: Mail delivery failed: returning message to sender Message-Id: Date: Mon, 05 Nov 2018 00:23:19 +0800 X-From-Rewrite: unmodified, actual sender is mailnull --1541348599-eximdsn-1707879264 Content-type: text/plain; charset=us-ascii This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: light_walker2005@domain.com all hosts for 'domain.com' have been failing for a long time (and retry time not reached) topman99@domain.com all hosts for 'domain.com' have been failing for a long time (and retry time not reached) john.diaz@domain.com all hosts for 'domain.com' have been failing for a long time (and retry time not reached) --1541348599-eximdsn-1707879264 Content-type: message/delivery-status Reporting-MTA: dns; hosting.domain.com Action: failed Final-Recipient: rfc822;john.diaz@domain.com Status: 5.0.0 Action: failed Final-Recipient: rfc822;topman99@domain.com Status: 5.0.0 Action: failed Final-Recipient: rfc822;light_walker2005@domain.com Status: 5.0.0 --1541348599-eximdsn-1707879264 Content-type: message/rfc822 Return-path: Received: from [::1] (port=47974 helo=hosting.domain.com) by hosting.domain.com with esmtpa (Exim 4.91) (envelope-from ) id 1gJLBG-00032r-4y; Mon, 05 Nov 2018 00:23:18 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 04 Nov 2018 08:23:18 -0800 From: john.diaz@domain.com To: john.diaz@domain.com Cc: topman99@domain.com Subject: Test Mail Message-ID: <87393b3d2663472c00ab06a8e3af56c7@domain.com> X-Sender: john.diaz@domain.com User-Agent: Roundcube Webmail/1.3.3 X-OutGoing-Spam-Status: No, score=-1.0 Test Mail. --1541348599-eximdsn-1707879264--
    0
  • cPanelLauren
    Hi @thepaperdragon If they're all failing you may want to check your dns resolvers. They can be found at /etc/resolv.conf
    or by going to WHM>>Networking Setup >>Resolver Configuration. Documentation on this can be found here: Resolver Configuration - Version 74 Documentation - cPanel Documentation In most cases (unless your provider requires specific resolvers) I'd test by adding different nameservers here. Off the top of my head there's CloudFlare's resolvers: 1.1.1.1 1.0.0.1 and Google's 8.8.8.8 8.8.4.4 I'd test changing these and seeing if your mail sends successfully
    0
  • thepaperdragon
    Thanks Lauren. I changed the resolver of my provider with the following: 1.1.1.1 1.0.0.1 8.8.8.8 Then, I tried to send test email to 3 domain. I noticed that it stuck/queue in Mail Queue Manager, so many frozen emails majority from info@domain.com sender.
    0
  • cPanelLauren
    Hi @thepaperdragon Are you indicating that you did not get the same error message but noticed that there are a lot of emails stuck in queue? If this is the case you'll want to identify if the mail is legitimate or not. Checking the /var/log/exim_mainlog
    should also provide some insights into how the mail is being sent
    0
  • thepaperdragon
    Hi @thepaperdragon Are you indicating that you did not get the same error message but noticed that there are a lot of emails stuck in queue? If this is the case you'll want to identify if the mail is legitimate or not. Checking the /var/log/exim_mainlog
    should also provide some insights into how the mail is being sent

    I did not received the error message right away that's why I checked it in Mail Queue Manager. Here is the bounce-back error message: Return-Path: <> Received: from hosting.domain.com by hosting.domain.com with LMTP id IIpCHVDV4VsbfAAAmrBV5Q ; Wed, 07 Nov 2018 01:54:24 +0800 Return-path: <> Envelope-to: john.diaz@domain.com Delivery-date: Wed, 07 Nov 2018 01:54:24 +0800 Received: from mailnull by hosting.domain.com with local (Exim 4.91) id 1gK5YW-0008GJ-CT for john.diaz@domain.com; Wed, 07 Nov 2018 01:54:24 +0800 X-Failed-Recipients: light_walker2005@domain.com, john.diaz@domain.com Auto-Submitted: auto-replied From: Mail Delivery System To: john.diaz@domain.com Content-Type: multipart/report; report-type=delivery-status; boundary=1541526864-eximdsn-987734006 MIME-Version: 1.0 Subject: Mail delivery failed: returning message to sender Message-Id: Date: Wed, 07 Nov 2018 01:54:24 +0800 X-From-Rewrite: unmodified, actual sender is mailnull --1541526864-eximdsn-987734006 Content-type: text/plain; charset=us-ascii This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: light_walker2005@domain.com retry timeout exceeded john.diaz@domain.com all hosts for 'domain.com' have been failing for a long time (and retry time not reached) --1541526864-eximdsn-987734006 Content-type: message/delivery-status Reporting-MTA: dns; hosting.domain.com Action: failed Final-Recipient: rfc822;john.diaz@domain.com Status: 5.0.0 Action: failed Final-Recipient: rfc822;light_walker2005@domain.com Status: 5.0.0 --1541526864-eximdsn-987734006 Content-type: message/rfc822 Return-path: Received: from [::1] (port=59334 helo=hosting.domain.com) by hosting.domain.com with esmtpa (Exim 4.91) (envelope-from ) id 1gK59r-0007Gi-Cl; Wed, 07 Nov 2018 01:28:57 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 06 Nov 2018 09:28:55 -0800 From: john.diaz@domain.com To: john.diaz@domain.com Cc: topman99@domain.com Subject: Test Mail (3 DOMAIN) In-Reply-To: <0a671a406b6714146290632b78bb56fb@domain.com> References: <0a671a406b6714146290632b78bb56fb@domain.com> Message-ID: <9f31d38d17204b674eb56a130c20f059@domain.com> X-Sender: john.diaz@domain.com User-Agent: Roundcube Webmail/1.3.3 X-OutGoing-Spam-Status: No, score=-1.0 Test Mail. --1541526864-eximdsn-987734006--
    The recipients are my personal email accounts, it is legit. I just use it for email testing. Our domain has no problem in incoming emails, the only problem is the outgoing emails, we received bounce-back, not receive by the recipients. Thanks.
    0
  • cPanelLauren
    Hi @thepaperdragon Can you confirm that you're using the following:
    • SPF
    • DKIM
    • A valid PTR record
    If these three items are configured I'd lean towards a DNS issue, though it's hard to be sure without access to the server or knowing the domain name. You might try one of the tools like mxtoolbox to check mail server to ensure it's configured properly as well. If none of your mail is being sent you might also check with your provider to ensure that they allow SMTP on port 25
    0
  • thepaperdragon
    Port 25 is not allowed by our Provider, we are using Port 587 for outgoing email. We already subscribed to MXTOOLBOX and they delisted our blacklist. But still the issue recurring.
    0
  • cPanelLauren
    Hi @thepaperdragon If port 25 is being blocked can you do the following and let me know if the issue persists? - Go to WHM>>Service Configuration>>Service Manager -> Exim Mail Server on Another port. -Click the checkbox for enabled, monitored and fill in the box with 26 to allow exim to listen on port 26. -Click Save at the bottom which should restart exim. Thanks!
    0
  • Rolando Lopez
    It happened to me and i did a traceroute to mail server ip address from 2 different networks and i verified that network were i had this error connection was rejected, even if you ping the ipaddress, you will have timeout, wich means it is a blocking policy in other side server.
    0
  • mathx
    Same exact problems here (and I dont see a more recent thread). It looks to me like this is a cached response as I dont even see a delivery attempt, just instafail at 'lookuphost' without a reason. I do not think this is a resolver problem, I can look stuff up no problem, and ping it (careful, host(1) ignores /etc/hosts, so could be something hidden in there, not in my case), but I do not get a proper error response 2019-05-23 12:43:50 cwd=/tmp 4 args: send-mail -i -- person@mydomain.com 2019-05-23 12:43:50 1hTqoo-0007EE-LC <= root@server.mydomain.com U=root P=local S=517 T="test" for person@mydomain.com 2019-05-23 12:43:50 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc 1hTqoo-0007EE-LC 2019-05-23 12:43:50 1hTqoo-0007EE-LC ** person@mydomain.com R=lookuphost T=remote_smtp: all hosts for 'mydomain.com' have been failing for a long time (and retry time not reached) 2019-05-23 12:43:51 cwd=/var/spool/exim 7 args: /usr/sbin/exim -t -oem -oi -f <> -E1hTqoo-0007EE-LC 2019-05-23 12:43:51 1hTqop-0007EN-0G <= <> R=1hTqoo-0007EE-LC U=mailnull P=local S=1866 T="Mail delivery failed: returning message to sender" for root@server.mydomain.com
    I can telnet to the mx record for the mydomain.com above port 25 no problem. How do I force it to try again to see what the actual failing reason is? Setting log_selector to +all doesnt help with any additional detail. [EDIT] *SOLVED* Never saw this mentioned in the few threads about this problem here. cd /var/spool/exim/db rm wait-dkim_remote_smtp* retry* wait-remote_smtp* service exim restart
    And then new and queued mail got sent out (because whatever other underlying problem I had solved earlier with another change, but somehow exim didnt get told about it despite having restarted it a few times to increase logging or other reasons).
    0
  • cPanelLauren
    Thank you for sharing @mathx
    0

Please sign in to leave a comment.