CRITICAL issue with forwarding (Bug)

[supportweb]

Hi Support,

We have been alerted to an issue that we are facing on Webmail.

The issue is with forwarding emails.

If we try forwarding an email directly from inbox or sent items the loading bar comes up but nothing else happens, Eventually we refresh the page to go back to our inbox.

If you open the email and click forward we get a server runtime error (please see screenshot of error attached).

Reply or Reply All do not have an issue(we have advised our customers to click reply and manually edit address for now)

I have tested on Google Chrome and Mozilla Firefox and had the same issue. Please can this be looked into urgently as this appears to be affecting every user using webmail on our server since the last update.

[Admin]

Hi,

If you have this issue please download the file from the link below:

https://www.mailenable.com/hotfix/MEWebBin_1043.zip

Extract this to the following directory:

Mail Enable\bin\Netwebmail\bin

This will resolve the problem and will work for either version 8, 9 or 10.

[supportweb]

Hi Admin, thanks for the prompt response.
I can confirm this worked for us.

[bitechbobbrenner]

We were experiencing the same problem and the above fix corrected the issue. Thank you for your attention!

[purebulk]

I receive an error that says this action can't be completed because the file is open in another program. What files or service do I need to stop in order to copy these in the correct folder?

[purebulk]

After hours I stopped all services on the server with the Mailenable console and tried to extract the files into the said directory and five files would not extract because they were open by another program. Is there any thing special one has to do to get these files in there?

[dedicate-it.net]

You have to stop your IIS and W3SVC to get webmail files to unlock -

[dcol]

This fix did NOT work for me. I just reverted back to 10.42 and all is working again. There is nothing I need in 10.43 anyways.
Just shows how limited ME support is. Introducing a serious bug like this is not acceptable. This just fuels the fire with switching email servers when my support renewal comes up. What is the point on paying for support when you get few untested updates which have serious bugs.