An unknown error has occurred. MailWasher is unable to determine the cause of this error.

[michaelkenward]

I get the impatience , but , in reality, some things need time to fix.

You can reduce the time it takes, and the impatience, if you test a new system properly before you unleash it on the world.

The answer in that other place that you expect everyone to read assiduously shows that this is not what happened.

The testing of the new database system was clearly incomplete.

They also committed the cardinal crime of any system update, do not do it on Sunday when there is no one around to pick up the debris and respond to the flood of broken systems reported here.

[Rover]

I get the impatience , but , in reality, some things need time to fix.

You can reduce the time it takes, and the impatience, if you test a new system properly before you unleash it on the world.

The answer in that other place that you expect everyone to read assiduously shows that this is not what happened.

The testing of the new database system was clearly incomplete.

They also committed the cardinal crime of any system update, do not do it on Sunday when there is no one around to pick up the debris and respond to the flood of broken systems reported here.

There is some validity to that, but there is also some other things , like how much you can test, 3rd party libraries, the list goes on and on, I mean this is a product from a smaller company, this is not like MS, Oracle, or a other really large ones. But this product has a niche, and I like it. And again I have no affiliation.

But, if I have detractor, it would be to inform users, that there are an issue, as opposed to relying on a community forum to push out that information, which is quickly buried in threads . Which could have been accomplished a few ways. 1) put a sticky announcement on this forum for news 2) Use the update methodology they have in place to inform you of a new version to inform there is an issue , even if it doesn't deliver a fix. 3) In 2 describe the working work around and explain that (remember, very few go to forums for an issue on a software issue, there is a certain population that will post (small compared to actual installs), then we have some that will just read (larger population but still small). Then we have the rest, who have no clue there is an issue, and I believe this issue is affecting a very large portion of the users. So letting them know is important,. even post something on the main website and take the hit, far worse to let them not know. Or find another avenue (ignore any of my typos, please)

[freestone]

Why not just pop a message up in Washer so I dont spend 2 hours trying to fix something I thought was isolated to me.

[Rover]

They also committed the cardinal crime of any system update, do not do it on Sunday when there is no one around to pick up the debris and respond to the flood of broken systems reported here.

As far as I know, this had nothing to do with a push out of an update on Sunday (depending on time zone), but rather a component that was date reliant and failed) . This happens with ssl/tls certificates that have an expiration , or something else in the code, incredibly hard to test for. I have been running version 173 for a while.

As , in my previous post, I am not giving FT a pass, but I also can have an understanding on the hill they are trying to climb. I get it that I come at this as a programmer, and yes I have done this with our own software.

They may have discovered the fix, but even distribution is tough.

[michaelkenward]

They also committed the cardinal crime of any system update, do not do it on Sunday when there is no one around to pick up the debris and respond to the flood of broken systems reported here.

As far as I know, this had nothing to do with a push out of an update on Sunday (depending on time zone), but rather a component that was date reliant and failed) .

Yes it is. The problem hit the world when, from reports here, no one was around to respond, let alone fix it.

Or was it just down to incompetence that they did not notice the date on which a date reliant component would affect users?

The responses here from Firetrust have been underwhelming.

Email and protecting it is, for some, mission critical.

[Rover]

They also committed the cardinal crime of any system update, do not do it on Sunday when there is no one around to pick up the debris and respond to the flood of broken systems reported here.

As far as I know, this had nothing to do with a push out of an update on Sunday (depending on time zone), but rather a component that was date reliant and failed) .

Yes it is. The problem hit the world when, from reports here, no one was around to respond, let alone fix it.

Or was it just down to incompetence that they did not notice the date on which a date reliant component would affect users?

The responses here from Firetrust have been underwhelming.

Email and protecting it is, for some, mission critical.

Somehow, I believe they know the amount of negative of press they are getting from this and are working on it. For me, I will wait.

[gingbat]

Issue resolved, please see:
viewtopic.php?f=16&t=58538&p=168432#p168432

Thanks!

[andrewraus]

Can confirm the update has downloaded & is working. Thanks

[Rover]

Issue resolved, please see:
viewtopic.php?f=16&t=58538&p=168432#p168432

Thanks!

All good here

[Rover]

All good here

[Velojet]

Yes!!! Back in business (Windows 10, MS Surface Pro)

[BamaInArk]

Can confirm the updated version, 7.12.188, is working fine. Checking for Updates within the MW application works.

[Brakedirt]

How about they fix it and deliver what I paid for?
I want to be able to click on a link and have my MailWasher fixed and working.

viewtopic.php?f=16&t=58538&p=168390#p168390

[peak4]

All good for me; I checked for updates, saw the new one and installed it.
Everything now behaves again.
However, if I visit the site as a new user, to download the latest version, I still get the "mailwasher_pro_setup_7_12_173" installer.

Bill

[Antispamneophyte]

Working great for me once again, on both machines.

Updating on the desktop was a piece of cake, but I had to uninstall and reinstall on the laptop to get the updated version.

Thank you so much, Firetrust!