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

[packrat]

Same problem. Changing the computer date/time to an earlier computer date fixed the problem.

Didn't want to leave date/time incorrect on computer, causes other issues. Downgraded to 7.12.125 as others suggested without issue. Once finished, unchecked the "Automatically check for update" under general settings to prevent it from returning; at least until the issue has been corrected.

First time I remember ever having an issue with Firetrust in all the years we have used the product, as releases have always been stable!

[Lantern]

This is the 2nd time on the latest version that it does not work or gives errors. to .downgrate to .125 version and everything works again. time to move on to something better. disappointed again

[jmharo]

I'm getting this error also. As of last night my MailWasher will not even connect any longer to get mail, so it's totally useless now. My Event Log tab is just filling up with errors now. If I can figure out how to do it, I'm going to try to go back to a previous version if possible.

[HookyB]

Same here! Mailwasher Pro stops getting mails with unknown error, list shows also database corrupted. Setting the clock back to 9 september as mentioned in this forum and it seems to work again. Hope they can fix this asap.

[driedeker]

same here from this morning same error as all others.

[rkrazor]

This is pretty weird, there shouldn't be any dependency on any outside service which stops people checking their email. Looking in to it.

Any updates on this?

[DaveOzric]

Yes, changing the computer date indeed fixes this issue. How strange is that.

[daven]

Me too. Mailwasher is getting very unreliable nowadays. I am looking for alternative ways to block spam going forward

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

Diagnosis: <EVENT><NAME>MWPEXCEPTION</NAME><ID>556401dcfaff3bce64da69a237211c0a</ID><DT>2023-11-12 08:33:59</DT><MWPEXCEPTION><UID>Exception a5d1cf3d25311a26c64d7c098c4385a3</UID><AID>Acct-2125808254</AID><SOURCE>MWPfetch::FetchThread()</SOURCE><MESSAGE>StdException - Unknown exception</MESSAGE><ADDXML></ADDXML></MWPEXCEPTION><ORDINAL>0</ORDINAL></EVENT>

[VikingOriginal]

Yup, same issue here, as of this morning...

Very frustrating!

Awaiting fix.

[drivinhome]

Also having the same issues

[Digerati]

Same here

[Rover]

I expect, as it is very early in the morning in New Zealand on Monday, something will come through later

Might be a silly assumption, but I'm going with that

[philsbbs]

I cannot change the time as I use sync time servers so cannot test it but like many love to hear more about the issue/solution.

[MrBill]

Add me to the list...

[philsbbs]

Moderator/ Admin of forum is it worth merge the posts / topics all relating to this error.