ConfigServer Community Forum

Unfortunately I am not aware of a way to accomplish this. If you read this knowledgebase article: https://support.configserver.com/en/knowledgebase/article/ive-made-changes-to-the-filetype-rules-conf-file-but-mailscanner-is-still-blocking-the-filetypes-i-want-to-allow-or-allowing-the-filetypes-i-wan...

The only effect whitelisting will have is that the email will not be scanned for spam. It will still be scanned for dangerous file attachments and dangerous content (the {Disarmed} tag). Stopping MS from tagging "internal" email is not simple to do. I think you would have to create a rules...

We can confirm that csf does not use log4j so it is not vulnerable to any log4j vulnerabilities.

I'm afraid we have no other solution for you. As you say, it is only people with root access who can access the mailcontrol interface, people can logon to the server anyway and read those emails directly if they wanted to, so the added risk seems fairly minimal.

If you are referring to MailControl in the MailScanner Front-End, if you disable storage of all emails in quarantine (this setting is under MailScanner Performance), the content of emails will not be available in MailControl (and nor will you be able to release them from quarantine or train spamassa...

Try this knowledgebase article:

https://support.configserver.com/en/kno ... n-i-fix-it

We have seen this when the ca-certificates rpm has not been upgraded on the server. Try upgrading that rpm or force reinstalling it with:
If that doesn't work, check whether your os needs updating with

It would be better to temporarily stop exim and you would also need to stop tailwatchd so that exim is not automatically restarted. Then restart both tailwatchd and exim when you are finished with your changes.

The rules files in general are not designed to manually edited. They WILL be overwritten by settings in the WHM MSFE plugin or the user cPanel MSFE plugin. I can only guess that is what was happening. But I have no idea why you were seeing localdomains added to the WHITELIST file. I assume you are t...

I'm not sure what exactly you are asking about. The MailScanner Front-End never automatically whitelisted local domains, and we never recommended manually doing this. If there were local domains in the whitelist in /usr/mailscanner/etc/rules/spam.whitelist.rules, then they must have been added eithe...