Repository navigation
v1.0.105
The doctor checks that Exim really carries the scanning wiring
The named-queue wiring is two files MSFE-NG writes — the ACL fragment and its include line in the cPanel hook — plus one step cPanel does: /scripts/buildeximconf copies the hook into /etc/exim.conf, and Exim is restarted to read it. The doctor only looked at the two files. When the build had not picked the hook up, or Exim had not been restarted, every check passed while Exim delivered mail unscanned, MailScanner idled and the Dashboard stayed at 0 (issue #17).
- Doctor: named-queue include built into exim.conf (Fail) —
/etc/exim.confdoes not include the fragment.msfe-ng doctor --fix(the banner's Fix what can be fixed) runs/scripts/buildeximconf && /scripts/restartsrv_eximand says so if the include is still missing afterwards. - Doctor: Exim running its current configuration (Warn) —
exim.confchanged after the Exim daemon started, so the running Exim still uses the previous one. This covers every Exim-side change: the wiring, local-submission privacy, SMTP-time rejects.doctor --fixrestarts Exim. - Wire Exim → MailScanner verifies after its own rebuild that the include landed and prints a
WARNING:line in the activity console when it did not.
Wiki: Troubleshooting → Wired, no errors — but mail is delivered unscanned and the Dashboard stays at 0. Upgrade: msfe-ng upgrade, or the Service tab.