Checking the failed sequence we have the following:
2025 Aug 26 13:08:09 (info) systemd: [-] Starting SYSV: Symantec Mail Security MTA...
2025 Aug 26 13:08:09 (info) mta: [-] Starting MTA:
2025 Aug 26 13:08:44 (info) mta: [-] [FAILED]
2025 Aug 26 13:08:44 (notice) systemd: [-] mta.service: control process exited, code=exited status=1
2025 Aug 26 13:08:44 (err) systemd: [-] Failed to start SYSV: Symantec Mail Security MTA.
2025 Aug 26 13:08:44 (notice) systemd: [-] Unit mta.service entered failed state.
2025 Aug 26 13:08:44 (warning) systemd: [-] mta.service failed.
Checking MTA locks are present:
2025 Aug 26 12:00:09 +03 (err) runner: [34798] Error creating runner lock file. File already locked by: /opt/Symantec/Brightmail/scanner/sbin/runner PID=19080
2025 Aug 26 12:00:11 +03 (err) runner: [34810] Error creating runner lock file. File already locked by: /opt/Symantec/Brightmail/scanner/sbin/runner PID=19158
2025 Aug 26 12:00:13 +03 (err) runner: [34820] Error creating runner lock file. File already locked by: /opt/Symantec/Brightmail/scanner/sbin/runner PID=19203
The following steps may resolve the issue:
service mta status