MagicSpam support Clustering??
MagicSpam support Clustering??
I am contemplating purchasing MagicSpam for our MailEnable server. We are currently running 2.x Enterprise in a cluster environment. We are going to upgrade to the latest MailEnable 6.x Enterprise version and would like to know if clustering is tested or supported yet with MagicSpam.
Re: MagicSpam support Clustering??
Thank you for your post sbyrd!
We have had a couple of implementations for MagicSpam for MailEnable where cluster environments have been successful. This stated, this is really dependent on *how* the cluster has been configured.
We encountered a case where a cluster had been configured with MailEnable modified to use a SQL database for its back end settings as opposed to the standard Registry - which is understandable. However, the modified structure ended up completely ignoring registry settings which is where the settings are normally stored to enable 3rd party plugins such as MagicSpam - and as it turns out since the SQL structure had been custom built specific for that instance, it had no understanding of later developments such as plugin support that MailEnable had since created.
Another case instance was one where a cluster of MailEnable servers had been put together as a group of standalone servers with common mail storage backend, but had been set up to automatically synchronize all settings between servers based on a scheduled task. Technically this would have worked but the installer had placed MagicSpam on only a single server - which in turn caused the MagicSpam settings to be overwritten and removed on each synchronization.
The short answer to all of this is that MagicSpam is not, at this time, supported within a cluster environment due to the multitude of possible cluster configurations that might exist in the wild. While it *may* work within such an environment in specific cases, our team is not able to offer support or troubleshooting.
This said - is there anyone on the board that has any success stories to share with MagicSpam and Cluster configurations under MailEnable?
We have had a couple of implementations for MagicSpam for MailEnable where cluster environments have been successful. This stated, this is really dependent on *how* the cluster has been configured.
We encountered a case where a cluster had been configured with MailEnable modified to use a SQL database for its back end settings as opposed to the standard Registry - which is understandable. However, the modified structure ended up completely ignoring registry settings which is where the settings are normally stored to enable 3rd party plugins such as MagicSpam - and as it turns out since the SQL structure had been custom built specific for that instance, it had no understanding of later developments such as plugin support that MailEnable had since created.
Another case instance was one where a cluster of MailEnable servers had been put together as a group of standalone servers with common mail storage backend, but had been set up to automatically synchronize all settings between servers based on a scheduled task. Technically this would have worked but the installer had placed MagicSpam on only a single server - which in turn caused the MagicSpam settings to be overwritten and removed on each synchronization.
The short answer to all of this is that MagicSpam is not, at this time, supported within a cluster environment due to the multitude of possible cluster configurations that might exist in the wild. While it *may* work within such an environment in specific cases, our team is not able to offer support or troubleshooting.
This said - is there anyone on the board that has any success stories to share with MagicSpam and Cluster configurations under MailEnable?
Who is online
Users browsing this forum: No registered users and 2 guests