Facebook
Twitter
M
Mark Priest
Guest
Am I right in saying that you now have to pay extra for the SpamAssassin module?
-
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
CentOS2Alma discussion
Z
ZeroSixty
Guest
Typical SWsoft............new features equals more money! But I believe spamassasin has been an addon since 7.something...
J
jchost
Guest
I'm not sure how it can be a feature when its not even related to SWSoft products, but a popular opensource spam fighter. Spam fighting should come as standard for anything in this day and age.
Heck, we had to pay $50 for coldfusion support, and all that the "support" does is add configuring options in the httpd.include's for coldfusion files.
Granted I can easily get around that by adding coldfusion serving web accounts to the main httpd.conf, but if its that easy, why charge for it in the first place...
Heck, we had to pay $50 for coldfusion support, and all that the "support" does is add configuring options in the httpd.include's for coldfusion files.
Granted I can easily get around that by adding coldfusion serving web accounts to the main httpd.conf, but if its that easy, why charge for it in the first place...
Z
ZeroSixty
Guest
jchost - You'll find no argument from me. Completely agree with you. Since SWsoft got a huge cash injection from Microsoft (ok...before then) us little peeps are completely insignificant....................damn shame.
When it was owned by the original PSA owners it had huge potential..........and by that I mean customer service.....something SWsoft lacks in unless you are a partner.
When it was owned by the original PSA owners it had huge potential..........and by that I mean customer service.....something SWsoft lacks in unless you are a partner.
I had Spamassassin support in 7.5.4 via the plesk interface...
But after the upgrade to 8.0.0, I couldn't find the spamassassin configuration anymore (generally under mail config of a domain).
It was simply due to the automatic (by the update) server-wide deactivation of spamassassin. I could enable it again via the SpamAssassin panel in the server section.
But after the upgrade to 8.0.0, I couldn't find the spamassassin configuration anymore (generally under mail config of a domain).
It was simply due to the automatic (by the update) server-wide deactivation of spamassassin. I could enable it again via the SpamAssassin panel in the server section.
