ConfigServer Community Forum

cool, sounds like a plan. Thanks!
I'll get back to you.

right, that is what this thread is about, it was a bug where something automated in whm/cpanel would re-write changes made to the spam.whitelist.rules file. Even if you went to fix the problem, the file would re-generate with the localdomains whitelisted. dohm had found msbe.pl in /usr/mscpanel usin...

we moved away from configserver fe because of this, but we don't like the new solution either. is this still an issue, or has it been fixed?
I could see how whitelisting localdomains made sense years ago, but is completely wrong today. We'd like to move back to configserver fe if its been fixed.

dohm, that is exactly what is happening to us. spam coming in on the domain, which is whitelisted if processed with the whitelisted domain deleted, gets marked as spam properly. but any time we change a rule, or if a couple of days go by, the whitelisted domains come back. I think whitelisting the d...

Where do the spam.whitelist.rules get built from, and how can I make my changes permanent? I've checked every domain/whm user's cpanel mailscanner whitelist settings, so I know the rules are not coming from the user whitelists. I thought it might be the cron job rebuilding the spam.whitelist.rules f...