MAil broke after upgrade to 11.38

[RyanHost]

get the following errors when trying to force the mail server to deliver mail, plus no mail is being received by the server from out side.

LOG: MAIN
cwd=/usr/local/cpanel/whostmgr/docroot 4 args: exim -v -M 1UZzxR-0005I6-Vg
delivering 1UZzxR-0005I6-Vg
LOG: MAIN PANIC
failed to expand condition "${perl{should_archive_outgoing_message}}" for archive_outgoing_email router: Undefined subroutine &main::should_archive_outgoing_message called.

LOG: MAIN PANIC
failed to expand condition "${perl{check_mail_permissions}}" for check_mail_permissions router: Undefined subroutine &main::check_mail_permissions called.

LOG: MAIN PANIC
failed to expand condition "${perl{enforce_mail_permissions}}" for enforce_mail_permissions router: Undefined subroutine &main::enforce_mail_permissions called.

LOG: MAIN PANIC
failed to expand condition "${perl{increment_max_emails_per_hour_if_needed}}" for increment_max_emails_per_hour_if_needed router: Undefined subroutine &main::increment_max_emails_per_hour_if_needed called.

LOG: MAIN
== [email protected] R=dkim_lookuphost defer (-1): dkim_lookuphost router failed to expand "${perl{mailtrapheaders}}": Undefined subroutine &main::mailtrapheaders called.\n

 

[simonas]

Try
/scripts/eximup --force

 

[JaredR.]

Try
/scripts/eximup --force

That will not do anything, since the original poster stated he updated to cPanel 11.38. eximup is deprecated in cPanel 11.36 and later. This is what will happen if you try to run it:

# /usr/local/cpanel/scripts/eximup --force
scripts/eximup is deprecated. exim is now updated by the rpm.versions system when you run upcp.
#

mysqlup and ftpup are likewise deprecated. We explained this in detail in our release notes for cPanel 11.36:

cPanel & WHM 11.36 Release Notes

check_cpanel_rpms verifies all RPM packages provided by cPanel, and is the closest equivalent to the scripts that have been deprecated.

http://docs.cpanel.net/twiki/bin/vi...ReleaseNotes#New scripts in the /usr/local/cp

In the case of this mail problem, it would be best if you can submit a ticket. There is no charge for submitting a ticket, and looking at this problem directly will help us to determine if there is a problem in cPanel 11.38 that needs to be fixed, or an isolated problem on your server.

 

[crasx]

I have the same issue, were you able to fix this?

 

[JaredR.]

Please submit a ticket so that we can investigate your problem directly.