Receiving but unable to send email to defined receiver
I use two different cPanel accounts. One of them (let's call it archive) is used for archiving purposes only.
So I set up an email forwarder from my productive cPanel account to the archive postbox.
This setup worked for a longer time without any problems, but since around two weeks or so, I receive error messages, saying that
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:
[EMAIL='mailarchiv@datenhafen.me'>mailarchiv@a[/EMAIL]rchive
(ultimately generated from system-filter)
retry time not reached for any host after a long failure period
When checking the exim_mainlog, I can see a lot of similar entries, but no real error messages. A complete sequence for a mail might look like:
What I have already done was to delete possibly corrupted exim files using
This will give me around two to three days of ease before the situation occurs again. The behaviour ist already described here, but unfortunately without a final solution. Thank you for your help - and a Happy New Year! Best regards, Philip
When checking the exim_mainlog, I can see a lot of similar entries, but no real error messages. A complete sequence for a mail might look like:
2016-01-01 16:24:34 1aF1ZC-0004P8-5Y H=shout01.mail.de [213.128.151.216]:60198 Warning: Message has been scanned: no virus or other harmful content was found
2016-01-01 16:24:38 1aF1ZC-0004P8-5Y H=shout01.mail.de [213.128.151.216]:60198 Warning: "SpamAssassin as deubnero detected message as NOT spam (-1.1)"
2016-01-01 16:24:38 1aF1ZC-0004P8-5Y <= <> H=shout01.mail.de [213.128.151.216]:60198 P=esmtps X=TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256 CV=no S=20306 id=E1aF1YS-0004Ow-DV@hostname T="Mail delivery failed: returning message to sender" for mailarchiv@archive
2016-01-01 16:24:38 1aF1ZC-0004P8-5Y SMTP connection identification D=domain.tld O=mailarchiv@productive E=mailarchiv@archive M=1aF1ZC-0004P8-5Y U=user ID=500 B=redirect_resolver
2016-01-01 16:24:38 1aF1ZC-0004P8-5Y SMTP connection outbound 1451661878 1aF1ZC-0004P8-5Y domain.tld mailarchiv@archive
2016-01-01 16:24:38 1aF1ZC-0004P8-5Y => mailarchiv R=virtual_user T=virtual_userdelivery
2016-01-01 16:24:38 1aF1ZC-0004P8-5Y ** mailarchiv@archive (mailarchiv@domain.tld) R=dkim_lookuphost T=dkim_remote_smtp: retry time not reached for any host after a long failure period
2016-01-01 16:24:38 1aF1ZC-0004P8-5Y Frozen (delivery error message)
2016-01-01 17:12:51 1aF1ZC-0004P8-5Y Message is frozen
What I have already done was to delete possibly corrupted exim files using
#cd /var/spool/exim/
#rm retry retry.lockfile wait-remote_smtp wait-remote_smtp.lockfile
#/etc/init.d/exim restartThis will give me around two to three days of ease before the situation occurs again. The behaviour ist already described here, but unfortunately without a final solution. Thank you for your help - and a Happy New Year! Best regards, Philip
-
So I set up an email forwarder from my productive cPanel account to the archive postbox.
You should check the domain name for archive itself, for issues.R=dkim_lookuphost T=dkim_remote_smtp: retry time not reached for any host after a long failure period
0 -
You should check the domain name for archive itself, for issues.
Unfortunately, I do not have full access to the server hosting the archive domain. I can only access it via cPanel. Furthermore, it has to be an issue between my productive system and the archive system, as any email sent from e.g. GMail is received without any problem. Seemingly only the mail forwarding is affected.0 -
This will give me around two to three days of ease before the situation occurs again.
Hello :) Do you have enough disk space and inodes available in the /var directory? EX:df -h df -i
Thank you.0 -
Hello, both space and inodes are available in the necessary quantity on the productive system (Space > 4TB, nodes > 8 billion). It must be somehow related to the interaction between the productive and the archive system, as external emails are delivered without any problem and only mails, forwarded or created by the productive system are an issue (no matter to which mailbox). Thank you for your support! 0 -
It must be somehow related to the interaction between the productive and the archive system, as external emails are delivered without any problem and only mails, forwarded or created by the productive system are an issue (no matter to which mailbox).
You may also want to check if any firewall rules are enabled on either server that could filter emails, as it looks like a connection failure message. Thank you.0 -
I checked this too, but it turned out to be something very different. After discussing this issue multiple times with my hoster, it turned out that my productive system was blocked by the archive system. This is solved in the meantime, so thank you for your help, but it works again! Br, Connor 0 -
I am happy to see the issue is now resolved. Thank you for updating us with the outcome. 0
Please sign in to leave a comment.
Comments
7 comments