I'm in the process of migrating accounts and believe I have found a bug. We have ServerA, where SpamAssassin is enabled, but many of the cPanel accounts have it disabled. We have ServerB with SpamAssassin enabled as well. The intent is to have it available for customers to use, but not enabled by default.
When we migrate accounts from ServerA to ServerB, whether SpamAssassin is enabled or not, it will automatically enable the file. This cause a lot of confusion with my customers as the ones that didn't have it enabled before were wondering why their emails suddenly had "[SPAM]" in the subject.
With SpamAssassin being enabled by default, I was surprised to see there was no way to set a global spam rating or change the default. A setting of 5 was setting a lot of false positives and causing more confusion. If it was set to 10, i probably would have left it alone since it would only flag the most obvious and we could make it more restrictive as necessary.
So to summarize, a cPanel account with it disabled by choice should not have it re-enabled upon transferring to a new server. I know enabling it creates a ".spamassassinenable" file, but a corresponding ".spamassassindisable" should exist when disabled on purpose. Unless this is a different issue?
When we migrate accounts from ServerA to ServerB, whether SpamAssassin is enabled or not, it will automatically enable the file. This cause a lot of confusion with my customers as the ones that didn't have it enabled before were wondering why their emails suddenly had "[SPAM]" in the subject.
With SpamAssassin being enabled by default, I was surprised to see there was no way to set a global spam rating or change the default. A setting of 5 was setting a lot of false positives and causing more confusion. If it was set to 10, i probably would have left it alone since it would only flag the most obvious and we could make it more restrictive as necessary.
So to summarize, a cPanel account with it disabled by choice should not have it re-enabled upon transferring to a new server. I know enabling it creates a ".spamassassinenable" file, but a corresponding ".spamassassindisable" should exist when disabled on purpose. Unless this is a different issue?