MailWasher is a mailbox screening program that sits before the user’s normal email client. It connects to a POP3 or IMAP account, lists messages still held by the mail server, and lets the user inspect or mark them before downloading ordinary mail. The wash action deletes selected junk from the server, after which the user opens Outlook, Thunderbird, or another client to receive what remains. MailWasher is therefore a gate in front of email, not a replacement for writing and organizing messages.
Server-side preview
The message list comes from the mail server. MailWasher can show sender, subject, classification, and a preview without asking the main client to download the complete mailbox first. Plain-text preview avoids much of the active content in an HTML message, and blocking external images prevents a remote tracking image from loading merely because the user inspected the mail.
A preview is still message content. Links can lead to fraudulent sites, and an apparently familiar sender can be forged or come from a compromised account. The useful decision is whether to keep, delete, or investigate the message, not whether the preview makes it look polished.
The wash step
Messages marked for deletion disappear from the server when the user runs the wash action. Only after that step does the normal mail client collect the remaining messages. This two-stage routine is the central behavior of MailWasher, and it can confuse someone who expects the inbox in Outlook to change immediately after marking a row.
A wrong classification also has a real consequence because the deletion happens before the normal client receives the message. The recycle bin can help restore deleted mail when recovery data and server behavior permit it, but it should not replace a careful check of unfamiliar senders, invoices, account notices, or one-time login messages.
Account details
Each account needs the correct POP3 or IMAP server, port, encryption method, username, and authentication flow. Gmail, Outlook, Yahoo, and other services may use OAuth instead of accepting the account password directly. A login that works in a web browser does not prove that a manually entered mail-server address is correct.
IMAP also changes what the list can show. MailWasher can hide messages already marked as read, so its count may differ from another client or webmail. Folder selection, cached message state, and server synchronization should be checked before assuming that mail vanished.
Filter order
Friends, blacklist entries, learning filters, remote block lists, and custom rules can all contribute to a classification. Their value depends on order and specificity. A broad rule that rejects a common word can catch legitimate mail, while automatically trusting every address in a contact list can admit a forged sender.
Custom regular expressions are flexible but easy to make expensive or overly broad. Firetrust’s own change history notes that regex filters can slow checking. A small rule set tested against known good and bad messages is easier to maintain than many overlapping rules whose final decision is hard to explain.
Daily routine
MailWasher works best when the user checks new rows, corrects uncertain classifications, runs the wash action, and then opens the mail client. Leaving both programs to fetch the same account at the same moment can make the visible lists change while a decision is being made. The extra step is deliberate: it gives the user a chance to remove unwanted mail before the main inbox stores it.
