The new HSphere looks like a good update. I look forward to it. I have a couple of question about the upgrade:
Points to note:
Custom php variable changes may not work for new hosting accounts.
I don’t understand what’s being said in the quote. Would you please explain further? I use PHP pretty extensively and want to know what changes or limitations will affect me and my customers.
Due to compatibility reason, dspam will no longer be available for mail servers using it.
Is this a temporary thing or are you saying dspam is going away entirely? What if anything will be its replacement?
PHP is changing the way it works with the update, it may means on unix servers a few config changes are needed to bring sites up after the upgrade.
It is moving to a fast_cgi means isntead of modphp to my understanding.
This is to allow php4/5 running.
Dspam is going away, we spent a lot of money with psoft on making the plugin to allow external MX and they left us out to dry We tried all we could to keep it up and going but it isn’t happening. We spend a lot on dspam with the developer as well only for him to sell out on us and almost disappear at times…oh well.
For what it is worth I have only spamassassin on a number of domains and it is working well these days.
Dspam is the main reason for the delay in the updates overall, we are trying to keep the clusters as in sync as possible and did not want one upgraded and the other behind.
We’ve evaluated the position and decided we are best to go forward, forgoing dspam.
Dspam was not enough of a ‘hit’ as a service for us to deploy it in cluster2, as many may have noted.
I have some domains with external DNS configs.
Does this mean I have to change MX records to include the normal mailservers instead of the dspam-ones?
Not any provider provides email-services without serious anti-spam filtering. Spamassasin is not a serious product in my opinion. What will be the next step for jodo?
Those won’t change. it is the auto setup of them during creation of mail domains that will change.
Spamassassin is a serious in fact enterprise product. It is the only offering by many providers, MANY.
We will see where it goes and what the options are later but there are and have been addons for SA for a long time for working much better htan the years before dspam was installed.
this means that dspam will remain intact for current domains and for domains which MX-records are manually changed to dpsam?
I hope to have a good solution. If that can be made through SA (with addons) fine for me. However until today the SA-implementation at Jodo was not very successfull in killing ‘modern’ spam. For example it did not check with external spam-listings (like spamcop SCBL) etc.
But keep up the good work! Working on this subject is better than doing nothing (keeping everything the same as it was before).
btw we’ve always checked with spamcop, we don’t use every blocklist out there as many of them will make false positives on a huge rate, but spamcop is one that we’ve used and trusted for a while.
We tried all we could to keep it up and going but it isn’t happening. We spend a lot on dspam with the developer as well only for him to sell out on us and almost disappear at times…oh well.