Alert messages are sent from Messaging Gateway (SMG) indicating that the Brightmail Engine / bmserver process has crashed with a signal 11 or signal 6.
Messaging Gateway may also begin holding messages in the Inbound and Outbound queues with a status of "421 4.4.7 [internal] Unable to process message at this time" and deferring new connections if the Inbound or Outbound queues have filled.
2023 Apr 10 13:18:04 +03 (err) runner: [17076] Job bmserver process 19166 exited, terminated on signal 6 (0x0086).
2023-04-10T13:09:28+03:00 (WARNING:778.3939928192): [36003] Spamhunter module: failure loading rules from file /data/scanner/rules/bm_ruleset.2.spamhunter_rules.1681117716/rules.
2023-04-10T13:09:28+03:00 (ERROR:778.3939928192): [36101] Spamhunter Module: no rulesets loaded.
2023-04-10T13:09:28+03:00 (ERROR:778.3939928192): [36002] Spamhunter module: failure loading rules.
2023-04-10T13:09:28+03:00 (ERROR:778.3939928192): [36008] Spamhunter module: initialization failure.
2023-04-10T13:09:28+03:00 (ERROR:778.3939928192): [27258] init_modules: error while calling init function for critical module libspamhunter. Restarting engine.
A malformed rule file caused the Brightmail Engine to repeatedly exit and restart. While the Brightmail Engine was in this state, messages could not be scanned and so accumulated in the Inbound and Outbound queues.
This issue is an extremely rare occurrence in which a malformed rule file that could not be loaded by the Brightmail Engine.
The issue was resolved via a subsequent anti-spam rule update which replaced the malformed rule file. For typical configurations, no messages were lost or went unscanned.