Mailwasher

What works

This has been tested to varying extent on wine v6.4, 7.0, 7.1, 7.2.

Seems to work generally fine except for some issues (see "what does not work" section).

- Transferring config folder (before starting the application) from Windows to respective wine path worked without problems, all settings were recognized.

- Starts as expected

- Flagging emails as friend, spam etc.

- Editing, adding entries to friends, spam, filter lists.

- Setting / adding email accounts to check etc.

- Switching to email application (also wine, might not work with native linux email application).

- Processing emails (= deleting marked emails).

- Auto-deletion and marking of emails according to filters / lists.

- Tray icon is present, is animated if new email is found and is clickable.

Essentially everything seems to work except for what has been found and put into the "what does not work" section.

What does not

So far, recovering emails has been unsuccessful, although the application claims that the respective email was recovered successfully. This didn't work in v6.54, either, but that version confirmed that it was unsuccessful. This feature worked on Windows when it was last tested / used back in the beginning of 2020 with the then current v7.12.x with the same settings and email accounts that now fail with the current version on wine.

Further tests uncovered that recovery only works for emails that were sent from the same email address to which the recovered emails are sent to (e.g. only emails "from self" are really recovered successfully)...

Restore log says: "SmtpCmdResp: 554 Unauthorized sender address." -> This seems to be a problem with the email provider rather than Mailwasher.

Also, the program crashes when trying to view an email in html format. Error message: "Error HRESULT E_FAIL has been returned from a call to a COM component."

This might be due to the absence of a native iexplorer on wine.

One strange behavior is that the application, when being minimized, leaves (at least for some time and occasionally) an "untouchable" area on the desktop in the shape and size of the application's window where the mouse is not able to click anything. Other applications that were in the background of Mailwasher need to be actively "pulled to the front" to make the area which Mailwasher covered before being minimized be accessible.

Also, MailWasherPro.exe and as a result wineserver64 are running constantly (in "idle" - which is, of course, not idle if it keeps the cpu busy, but the application does nothing "visibly") at a higher cpu load % than it is the case for v6.54 and one would expect for Mailwasher being idle.

Workarounds

What was not tested

Firetrust login.

Sync to mobile.

Hardware tested

Graphics:

• GPU: Intel
• Driver: open source

Additional Comments

Initially, v7.12.57 was first successfully tested (see https://forum.winehq.org/viewt...). When writing up this test, v7.12.67 was found to be the latest version which immediately was installed and used for this review. Although, no differences between those two versions regarding behavior was noticed.

There seems to be no (major) downside to using v7.12.67 over v6.54. On the contrary: With v6.54, after starting the application there were several error messages that had to be acknowledged before proceeding. This nuisance is not present in v7.12.67.

But the high(er) cpuload in what would normally be considered idle mode might be a reason for some to stick with v6.54.