I was just wondering if anyone else was having this issue or is there a way to rebuild the SpamAssassin for Mailenable?
We use MagicSpam for filtration and we have been experiencing issues with SpamAssassin crashing so I contacted MagicSpam support and they seem to think it has something to do with the Mailenable implementation of SpamAssassin.
We have made a bunch of changes in MagicSpam and nothing seems to fix it, the only workaround that I have found is to run a powershell script that restarts the "MagicSpam SpamAssassin Service Daemon".
Apparently, when we made the changes it took MagicSpam out of the equation for the issue even though whenever the service "MagicSpam SpamAssassin Service Daemon" is restarted, the Mailenable service runs for an hour or so then crashes again.
The service currently states "Running" but when you go into Servers -> Localhost -> Extensions -> Message Filter -> SpamAssassin and run the 'Test' we get the error "Failed to ping the SpamAssassin server. Please ensure the details are entered correctly, and that the SpamAssassin server is running".
We have tested:
- Host : 127.0.0.1
Port : 783
Check boxes : Unchecked
- Host : localhost
Port : 783
Check boxes : Unchecked
Jason
