When we saw the new release and that in the changelog it was addressing DKIM issues it seemed very important for us to do the update without waiting as there was many posts about DKIM issues and that we were ourselves having some issues with DKIM and different customer domains.
So we are now running 7978 since 5th november.
During the night after the upgrade, the CPU went 100% and services were unavailable. We had to restart the service in emergency.
Today it had to be restarded again due to the same issue.
As you were aware of this issue, I find it extremly unprofressional to silently remove the release after publishing it and not giving a warning to your customers that it can possibly have an issue that you are aware of.
I can't believe what I'm reading here!
You could at least inform of the issue with a community post or at least leave the release changelog online, remove the download link and add a warning to the changelog about the issue. But here you just silently hide the issue. What method is this really?
Also in different post Kyle suggested that we shouldn't downgrade a SmarterMail once it was updated to a new build due to possible issues, but it seems that yourselves are downgrading to resolve issue of new build ?
Should we then downgrade too ?
Really again, we are surprised on what you did here. Removing the download link I can understand, but hiding completly the existance of the release like it never existed... o_O
PS: I did a dotTrace the 2nd time it went 100% cpu and out of control. I can upload it to you if it helps finding the issue. If so please tell me where I should upload it.