[CPANEL-25795] Mail failure - rejected by local scanning code
Hi
Right after last night's upcp update to WHM 70.0.32 release tier I received an email from the server with the subject
Mail failure - rejected by local scanning code
saying the following:
(name of the server is X'd out)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
A message that you sent was rejected by the local scanning code that
checks incoming messages on this system. The following error was given:
local configuration problem
------ This is a copy of your message, including all the headers.
------ No more than 100K characters of the body are included.
Received: from root by host.XXXXXXXXXXXX.com with local (Exim 4.89_1)
(envelope-from )
id 1fGIht-0000OG-Vh
for root@host.XXXXXXXXXXXX.com; Wed, 09 May 2018 02:45:12 -0400
From: "(Cron Daemon)"
From: "(Cron Daemon)"
To: root
To: root@host.XXXXXXXXXXXX.com
Subject: Cron /usr/local/cpanel/scripts/upcp --cron
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
Precedence: bulk
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
Message-Id:
Date: Wed, 09 May 2018 02:36:09 -0400
>>>>>>>>>>>>>>>>>>>>>>>>
I see this in SSH
exigrep root@host.XXXXXXXXXXXXX.com /var/log/exim_mainlog
2018-05-09 02:45:13 1fGIqe-0001Ye-UJ <= <> R=1fGIht-0000OG-Vh U=mailnull P=local S=1400975 T="Mail failure - rejected by local scanning code" for root@host.XXXXXXXXXXXXX.com
2018-05-09 02:45:13 1fGIqe-0001Ye-UJ => lfd R=virtual_user T=dovecot_virtual_delivery C="250 2.0.0 AMDOAvmY8lpJFwAA4qjuAg Saved"
2018-05-09 02:45:13 1fGIqe-0001Ye-UJ Completed
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
This server has been up and running fine for a few months- no configuration issues.
I am getting other mail from root without errors - just not getting the daily upcp cron update email without the mail delivery error.
There doesn't see to be any other email issues.
I can send mail just fine from webmail and fromemail software
I would normally just wait for upcp to run again or I would force it to run again and see if the problem is solved in the next update-but- I am a little concerned about running upcp or letting this server run it again tonight because my other servers say that the update was blocked
and they did not update to WHM 70.0.32 release tier and they do not have upcp errors. All servers were set for the release update preference in WHM and before last night - they were all using WHM 68.0.38 release tier. Today - I put the other servers back to the stable update preference so that they do not update for a while.
(What also worries me about the updates is that - The blocked update details say "Upgrade to the next LTS is blocked until Wednesday May 16, 2018" and I do not have updates set for LTS.
This seems strange)
The server that is having the problem - that did update to WHM 70.0.32 release tier - I turned off updates completely until I know that this issue is resolved. I can live with this issue - but - I can't afford other issues.
Nothing else has changed on the server except for the update to WHM 70.0.32 release tier
So - my questions
is anyone else having the same problem?
Is the issue resolved for tonight's update?
Is the WHM 70.0.32 release tier having this and other issues?
Thanks
Audrey
-
Hello @audrey, The information you provided suggests that ClamAV rejected the message due to it's contents, however I was unable to reproduce this behavior on a test environment. Do you mind opening a support ticket using the link in my signature so we can take a closer look at an affected system? You can post the ticket number here once it's opened and I'll link it to this forums thread. Thank you. 0 -
Thanks Michael You have never steered me wrong:) I always trust your advice!! I submit a ticket. Ticket ID "9536209" Take care 0 -
Hello @audrey, Thank you for taking the time to open the support ticket. I've added an internal note to the ticket linking it to this forums thread. You should receive a response from one of our Technical Analysts shortly. Thank you. 0 -
Hi Michael Thanks again I see that upcp ran last night and I received the email from cron and did not get any mail delivery errors from the server. I am sorry - apparently I missed the upcp email earlier today. I closed the ticket Hooray for all being good Take care Audrey 0 -
Hello Audrey, My concern is that this only happens during the initial update from version 68 to version 70 due to the additional output that occurs in the cPanel update log. As part of the support ticket, we can check to see if there's anything specific to your system (that we could replicate on a test system) that's resulting in message delivery failure notification. Do you mind reopening the support ticket and granting us access to the affected system? Thank you. 0 -
Hi Michael Thanks for being thorough!! I reopened the ticket. FYI - about 15 minutes ago I updated the kernel and rebooted this server Thanks again 0 -
We've received the same to one server (so far). Just updated to 70, had that "local configuration problem" error as well. Looking forward to hearing the results of this. 0 -
I started receiving those emails after the latest updates also, getting them from about 7 or 8 servers now. They look to be rejecting the UPCP email that is sent out. Same subject and has local configuration problem also, then includes the full header and the content of the UPCP email that was rejected. 0 -
Oops, not just the UPCP email being rejected, the output of a cron that a client has is being rejected also, so it's not just limited to the UPCP email. 0 -
Hi Michael, Got the same thing, but WHM is rejecting WHM update mails in my case. As I spent an hour, before finding the rejected cron job email telling me there was a WHM update, trying to see just how compromised my box was, I've opened a support ticket as well that includes full headers of the email received. Your Support Request ID is: 9541435 [2018-05-11 04:47:02 -0400] Running version '11.68.0.38' of updatenow. [2018-05-11 04:47:10 -0400] Target version set to '11.70.0.34' Server has not had anything updated to it since the WHM update. Best, Michael 0 -
Hello Everyone, Thank you for the continued feedback. We are now tracking reports of this issue as part of internal case CPANEL-20331. I'll monitor this case and update this thread with more information as it becomes available. Thank you. 0 -
I'll follow this thread too since I had the exact same errors (and some more amongst which an update_db_cache and a Dovecot error) since the update to v70.0.30 last night. 0 -
Following this thread. 0 -
Following... I had the same experience as the OP (UPCP ran and 15 minutes later the report email was rejected, the next UPCP, 24 hours later was normal). 0 -
Following this thread. Also encounter same issue. After upgrade from version 68 to 70 today. Cpanel version v70.0.41 0 -
Hello Everyone, We are continuing to track reports of this happening upon the initial update from version 68 to version 70, but have yet to reproduce the issue internally. Can anyone that experienced this issue run the following commands and let us know the output? grep '' /etc/redhat-release /var/cpanel/envtype cat /etc/exim.conf.localopts
Also, let us know of any specific third-party plugins (e.g. CSF/LFD, MailScanner) or custom Exim configurations that are enabled on affected systems. Thank you.0 -
It looks like this only happens during the update, not afterwards. We are now a couple of days later and until now the issue did not re-occur anymore. Which might explain why you can't reproduce it. It did not re-occur after the update from 11.70.0.30 to 11.70.0.42. This is the result of the command on our systems: [quote]root@srv ~ # grep '' /etc/redhat-release /usr/local/cpanel/version /var/cpanel/envtype ; grep CPANEL= /etc/cpupdate.conf /etc/redhat-release:CentOS Linux release 7.5.1804 (Core) /usr/local/cpanel/version:11.70.0.42 /var/cpanel/envtype:standard 0 -
Hello, To update, this was confirmed to happen during email delivery attempts while the exim.pl.local file was in the process of updating. This is solved in cPanel & WHM version 70.0.46: Fixed case CPANEL-20331: Avoid transient error when installing exim.pl.local. Version 70.0.46 is now published to the CURRENT build tier. I'll update this thread again once it's published to the RELEASE build tier. Thank you. 0 -
I should have posted this earlier, but got busy with other things ;) Adding it here in case something similar crops up again, so the great G can help us find it... Kevin (cPanel tickets) reported to me that he found this error on my server during the investigation: I was able to see in the logs that the message failed for the below message. == 2018-05-11 04:00:17 1fH3hn-0004ej-PW F= rejected by non-SMTP ACL: failed to expand ACL string "${if eq{$originator_uid}{${perl{user2uid}{nobody}}}{1}{0}}": Undefined subroutine &main::user2uid called. == Best, Michael 0 -
Hello, Version 70.0.46 is now published to the RELEASE release tier. Thank you. 0 -
One of my (last?) v68 servers auto-updated this morning, so this one final tidbit per a support ticket response: [QUOTE] >>> "Any v68 that updates is going to have this same issue?" That's correct, this fix was published to v70, 72, and 74 so v68 is likely to still have this error. You shouldn't experience this error after the update to v70. Let me know if we can assist you further! Kind regards, Cameron 0 -
I know this is an old thread, not sure if I should start a new one. I had a similar problem with today's upcp, got an email with the subject "Mail failure - rejected by local scanning code" and the first few lines: " A message that you sent was rejected by the local scanning code that checks incoming messages on this system. The following error was given: local configuration problem " Further down I think this is the versions it's updating from and to: [2019-02-25 00:51:06 +0000] Detected version '11.76.0.20' from version file. [2019-02-25 00:51:06 +0000] Target version set to '11.78.0.12' As a previous poster indicated, there's an error logged in /var/log/exim_mainlog: 2019-02-25 01:20:03 1gy4U7-00079z-06 F= rejected by non-SMTP ACL: failed to expand ACL string "${if eq{$originator_uid}{${perl{user2uid}{nobody}}}{1}{0}}": Undefined subroutine &main::user2uid called. 2019-02-25 01:20:04 1gy4w7-0000H8-BC <= <> R=1gy4U7-00079z-06 U=mailnull P=local S=1105309 T="Mail failure - rejected by local scanning code" for root@xxxx.xxxx.com So it looks like a "user2uid" function was not found for some reason. Any other info I could add here to be more useful? Thanks Nick 0 -
I have a customer having the same issue with email being rejected as well 2019-02-25 12:57:47 1gyLRj-0000hq-To <= <> R=1gyLLD-00080t-2L U=mailnull P=local S=1058328 T="Mail failure - rejected by local scanning code" for root@host.DOMAIN.TLD 2019-02-25 12:57:47 1gyLLD-00080t-2L F= rejected by non-SMTP ACL: failed to expand ACL string "${if eq{$originator_uid}{${perl{user2uid}{nobody}}}{1}{0}}": Undefined subroutine &main::user2uid called. The info requested previously /etc/redhat-release:CentOS Linux release 7.6.1810 (Core) /var/cpanel/envtype:standard cat /usr/local/cpanel/version 11.78.0.12 Seems the latest update completed properly though after being delayed for a couple days ==> /var/cpanel/updatelogs/update.1550947861.log <== [2019-02-23 12:52:58 -0600] W NOTE: A system upgrade was not possible due to the following blockers: [2019-02-23 12:52:58 -0600] W [INFO] - Upgrade to the next LTS is blocked until Monday Feb 25, 2019 in order to distribute upgrades over a number of days. If you wish to upgrade now, you can do so now with the force option. => Log closed Sat Feb 23 12:52:58 2019 ==> /var/cpanel/updatelogs/update.1551034262.log <== [2019-02-24 12:53:01 -0600] W NOTE: A system upgrade was not possible due to the following blockers: [2019-02-24 12:53:01 -0600] W [INFO] - Upgrade to the next LTS is blocked until Monday Feb 25, 2019 in order to distribute upgrades over a number of days. If you wish to upgrade now, you can do so now with the force option. => Log closed Sun Feb 24 12:53:01 2019 ==> /var/cpanel/updatelogs/update.1551120661.log <== [2019-02-25 12:57:47 -0600] [2019-02-25 12:57:47 -0600] Completed all updates => Log closed Mon Feb 25 12:57:47 2019 0 -
I am receiving the same mail Failure, on 2 production servers and a dns-only on upcp Cpanel version 11.78.0.12 Centos 7.6 Cloudlinux 7.6 Centos 6.10 Regards Pedro Dias 0 -
Hello I had no issue tonight, maybe only when an upgrade is done Here is the ticket 11540785 - Mail failure - rejected by local scanning code 0 -
Please inform myself with a resolution too! 0 -
I also had one again when upgrading the 27th of februari. But our Cpanel is rented with Hetzner so I don't know how to send in a ticket then 0 -
@rhm.geerts, Thank you for the report. We've received access to a couple of affected systems through support tickets, and we do not have a need for additional tickets at this time. I'll let you know if this changes. I don't have more information to report on the status of case CPANEL-25795 at this time, but I'll update this thread as soon as more details are available. Thank you. 0 -
Hello Everyone, This is fixed as part of an update to the Exim RPM in cPanel & WHM version 78.0.17: Fixed case CPANEL-25795: Update exim to version 4.91-5.cp1178 Thank you. 0
Please sign in to leave a comment.
Comments
31 comments