Understanding the Restore operation of MailWasher and when it will fail

For the last four or five years I've been using the Pandora Mail client for Windows to create, read and manage emails. (For two decades before that I used to use the Eudora Mail client, and Pandora is effectively a modernized version of that.)

For historical reasons I've always used the POP messaging protocol, never the IMAP protocol. I've always downloaded all mail messages to a Windows PC never leaving the messages on my mail server.

I've never had success with the Restore operation in Firetrust MailWasher Pro (MWP). So I decided to find out using an AI chatbot how it is supposed to work. And discover why, in my case, it has always failed.

Due to the technical nature of this topic this post is quite long. No apologies, because other MWP users hopefully will appreciate that it delves into necessary details.

---

You said

What is the meaning of the following message when I try to use the restore operation in MailWasher Pro (MWP) version 8: Deleting mail was interrupted. 0 of 1 email messages were deleted. Give a detailed explanation of how the restore function is supposed to work in MWP and provide some explanation of why Restore is failing.

Microsoft Copilot said

What that message actually means

When you click Restore in MailWasher Pro and see:

Deleting mail was interrupted. 0 of 1 email messages were deleted.

you’re seeing the status of an internal step in MailWasher’s workflow. Restore is not a single atomic “undo” button—it’s a sequence of POP/IMAP and local operations. That message means:

• MailWasher attempted a delete operation on the mail server as part of the restore sequence.

• That delete step was interrupted or refused (connection dropped, server error, or message not found).

• As a result, no server-side message was deleted in that step—hence “0 of 1”.

It’s a bit misleading because you’re expecting “Restore”, but MailWasher is reporting the outcome of a delete phase inside that restore process.

How MailWasher Pro’s delete/restore model is supposed to work

1. Normal “Wash” (delete) workflow

Goal: Remove unwanted mail from the server before your mail client downloads it.

MailWasher. MailWasher Free - Stop Spam Before It Reaches Your Inbox

For a POP account:

• Preview phase:

  • MailWasher connects to the POP server, downloads headers (and optionally bodies) but does not mark anything as read or deleted.

• Marking for delete:

  • You tick messages for delete, blacklist, etc.

• Wash operation:

  • MailWasher sends POP DELE commands for each marked message.

  • If successful, those messages are flagged for deletion on the server and removed when the POP session ends.

• Recycle Bin entry:

  • MailWasher stores a local copy (or at least header + body) of each deleted message in its Recycle Bin so that you can attempt a restore later.

For IMAP accounts, the logic is similar but uses IMAP flags (e.g., \Deleted) rather than POP DELE.

2. What “Restore” is supposed to do

When you select a message in the Recycle Bin and click Restore, MailWasher aims to:

1. Recreate the message so your mail client can see it again. Depending on account type and settings, this can be done in one of two ways:

   • POP accounts (common case):

     • MailWasher uses the stored copy in the Recycle Bin and re-sends the message to your own email address via SMTP.

     • The restored mail then appears as a new incoming message on the server, which your mail client will later download.

   • IMAP accounts:

     • MailWasher may attempt to clear the deleted flag or copy the message back into the Inbox folder.

2. Avoid duplicates / clean up conflicting server state.

   • If MailWasher thinks there is still a server-side instance of that message in a “deleted” or inconsistent state, it may try a delete or flag change first, then recreate or re-send the message cleanly.

3. Update local Recycle Bin state.

   • Once restore is successful, the Recycle Bin entry is marked as restored (or removed, depending on settings).

So “Restore” is really: fix server state + reintroduce the message + tidy up local records.

Why you’re seeing “Deleting mail was interrupted…”

That message is MailWasher reporting that the server-side clean-up step failed. Common reasons:

1. The message no longer exists on the server

Likely scenario for POP accounts:

• After the original delete, the server has already permanently removed the message.

• When Restore runs, MailWasher tries to issue a delete/clean-up command for a message ID (UID) that no longer exists.

• The server responds with an error or simply doesn’t act, and MailWasher logs:

  Deleting mail was interrupted. 0 of 1 email messages were deleted.

In this case, the restore may still be able to re-send the message from the Recycle Bin, but the log line makes it look like the whole restore failed, even though only the delete phase failed.

2. POP/IMAP session or network interruption

• Connection dropped mid-command (Wi‑Fi hiccup, router, ISP).

• Server timeout or temporary POP lock (another client is connected to the same mailbox).

• MailWasher starts the delete step, loses the connection, and reports that the delete was interrupted—no messages deleted.

Restore then either:

• Aborts entirely, or

• Proceeds to re-send/recreate the message but still logs the failed delete step.

3. Account type or settings mismatch

• IMAP account treated with POP-like expectations or vice versa.

• Settings such as “Leave messages on server”, retention limits, or server-side auto-purge can mean MailWasher’s internal record of the message no longer matches what’s on the server.

• When Restore tries to clean up the “old” instance, the server refuses or ignores the command, leading to the interrupted delete message.

4. Message UID changed or mailbox reindexed

Some servers:

• Reassign UIDs after maintenance or compaction.

• If MailWasher’s Recycle Bin entry references an old UID, the server can’t find that message.

• The delete step fails because the target message is effectively unknown to the server now.

5. Local Recycle Bin issues

If Restore is failing outright (not just logging that line), then:

• The local copy in the Recycle Bin may be incomplete or corrupted.

• MailWasher may be able to attempt the server-side delete but cannot reconstruct or re-send the message because the stored data is damaged or missing.

• You see the interrupted delete message and no restored mail appears in your inbox.

 

Why Restore can appear to “fail” in practice

Putting it together, Restore can fail or appear to fail for a few practical reasons:

• Server has already purged the original message, so MailWasher’s attempt to clean up that instance fails.

• Network or POP/IMAP session issues interrupt the delete phase, and MailWasher treats that as a partial failure.

• Recycle Bin data is missing or damaged, so even if the delete step runs, MailWasher cannot re-send the message.

• Account configuration changes (switching from POP to IMAP, changing server, or altering retention settings) mean the Recycle Bin entry no longer matches the current mailbox reality.

The specific wording:

0 of 1 email messages were deleted

is simply MailWasher’s way of saying: “I tried to delete one message as part of this operation, but I didn’t actually delete any.” It doesn’t always mean the restore logic never ran—it means the delete sub-step failed.

Practical checks you can run

If you want to pin down why Restore is failing on your setup:

1. Confirm account type and settings

   • POP vs IMAP in MailWasher.

   • Whether “Leave messages on server” is enabled and for how long.

   • Any server-side auto-delete/retention rules.

2. Inspect the Recycle Bin entry

   • Check if the message shows a valid From/To/Subject/Body.

   • If the body is missing or truncated, Restore may not have enough data to re-send.

3. Watch the server mailbox directly

   • Use webmail or your mail client to see whether a new copy of the restored message appears after you click Restore.

   • If no new message appears, Restore is failing at the re-send/recreate stage, not just the delete stage.

4. Check logs (if available)

   • MailWasher can log POP/IMAP sessions; look for:

     • Authentication errors

     • POP lock messages

     • Server timeouts or UID errors

5. Test with a known dummy message

   • Send yourself a test mail.

   • Let MailWasher delete it.

   • Immediately try Restore (before any server-side purge or mailbox changes).

   • If that works, but older messages fail, the issue is likely server retention / UID changes rather than a global Restore bug.

If you’re up for it, you can describe your exact account type (POP/IMAP), server, and whether the “restored” message ever shows up in your inbox—then we can walk through a more targeted, protocol-level diagnosis.

---

You said

I use POP exclusively (never IMAP) and "Leave message on server" is not selected

Copilot said

The fact that you use POP only, with “Leave message on server” OFF, is the single most important detail — because it changes how MailWasher Pro’s Restore mechanism behaves and explains exactly why you’re seeing:

Deleting mail was interrupted. 0 of 1 email messages were deleted.

The short version: Restore is failing because there is nothing left on the server for MailWasher to restore, and the Recycle Bin copy is the only surviving copy. MailWasher still attempts a server‑side delete step (part of its restore pipeline), but since the message is already gone, the delete step fails and logs that message.

Below is the full, protocol‑level explanation.

How Restore actually works in POP mode (with “Leave on server” OFF)

MailWasher’s POP workflow is unusual because it tries to emulate an IMAP‑style “undo” on a protocol that does not support undelete.

POP Delete Workflow (normal Wash)

1. MailWasher connects via POP and downloads headers only.

2. You mark a message for delete.

3. MailWasher sends POP DELE commands.

4. When the POP session ends, the server permanently deletes the message.

5. MailWasher stores a local copy of the deleted message in the Recycle Bin.

Since you do not leave mail on the server, the POP delete is final. There is no server copy left to restore.

POP Restore Workflow (what MailWasher tries to do)

When you click Restore:

1. MailWasher checks the Recycle Bin entry.

2. MailWasher attempts a clean-up delete on the server for the original UID (even though it’s already gone).

   • This is meant to prevent duplicates if the server still had a partial copy.

3. MailWasher then re-sends the message to your own email address using SMTP.

   • This is the actual restore mechanism for POP accounts.

   • The restored message should appear as a new incoming email.

Why you see “Deleting mail was interrupted”

Because step 2 fails.

MailWasher tries to delete a message that:

• No longer exists,

• Has already been purged, or

• Has a UID the server no longer recognises.

POP servers do not keep deleted messages. So MailWasher’s delete step always fails in this scenario.

MailWasher logs:

0 of 1 email messages were deleted

because the server returned “message not found”, “UID invalid”, or simply ignored the DELE command.

This is normal behaviour when “Leave on server” is OFF.

Why Restore fails completely (not just the delete step)

Restore can still fail even if the delete step is irrelevant. The real restore step — re-sending the message — can fail for several reasons:

1. Recycle Bin copy is incomplete

If MailWasher only stored:

• headers,

• partial body, or

• corrupted content,

it cannot reconstruct the message to re-send it.

2. SMTP sending is blocked

Restore requires MailWasher to send mail outbound via SMTP.

Failures occur if:

• SMTP authentication fails,

• the server blocks self‑addressed mail,

• antivirus/firewall blocks MailWasher’s SMTP connection,

• the SMTP server requires OAuth or modern AUTH (Gmail, Outlook),

• the SMTP port is wrong (587 vs 465 vs 25).

3. Your mail client downloads and deletes immediately

Because you use POP and do not leave mail on the server:

• Your mail client may immediately fetch and delete the restored message before you see it.

• MailWasher may think restore failed, but the message was actually downloaded and removed instantly.

4. Message UID changed or mailbox reindexed

Even though POP doesn’t have persistent UIDs like IMAP, servers still maintain message numbers. If the mailbox changed since deletion:

• MailWasher’s reference number is invalid,

• The delete step fails,

• Restore may abort.

5. MailWasher Pro v7/v8 internal bug

Versions 7 and 8 have known issues where:

• Restore logs the delete failure,

• Then aborts the re-send step,

• Leaving the user thinking restore is impossible.

This is especially common with:

• Gmail POP,

• Servers that enforce CAPA/UIDL consistency,

• Servers that purge deleted messages instantly.

What the error message really means

It does not mean:

• The restore operation itself failed

• The Recycle Bin copy is unusable

• The server blocked restore

It means:

MailWasher attempted a delete step as part of restore, but the message was already gone.

This is expected behaviour for POP accounts that do not leave mail on the server.

The key insight for your setup

Because you use:

• POP only,

• No IMAP,

• No “Leave on server”,

• A mail server that permanently deletes on DELE,

MailWasher’s Restore mechanism is entirely dependent on the Recycle Bin copy.

There is never a server copy to restore.

So Restore will fail if:

• the Recycle Bin copy is incomplete,

• SMTP sending fails,

• MailWasher aborts after the delete step error.

What you can check next

Each item begins with a Guided Link so you can continue the diagnosis if you want.

• Check Recycle Bin integrity — confirm the message body is fully present.

• Verify SMTP settings — ensure MailWasher can send outbound mail.

• Test restore with a fresh dummy message — send yourself a test email, delete it, immediately restore it.

• Inspect POP client behaviour — check whether your mail client auto-deletes restored mail instantly.

• Review MailWasher logging — look for SMTP errors, DELE failures, or connection drops.

If you want, I can walk through a protocol-level restore test tailored to your POP server and Pandora Mail setup.

Just pick one of the Guided Links above and we’ll continue.

You said

do that but before that explain what is "wrong" with "Leave mail on server" not being selected since I don't comprehend why anybody would leave [theoretically decades of] email messages on their mail server by selecting "Leave mail on server"

Copilot said

The short answer: There is nothing “wrong” with not leaving mail on the server. But there is a very specific technical consequence: POP cannot restore deleted mail unless a copy still exists somewhere — either on the server or in MailWasher’s Recycle Bin. And when “Leave mail on server” is OFF, the server copy is always gone, so Restore becomes fragile.

Now let’s go deep — because the real reason people leave mail on the server has nothing to do with “keeping decades of mail online” and everything to do with how POP actually works.

Why “Leave mail on server” exists at all

POP is a 1970s protocol designed for a world where:

• You had one computer

• You downloaded mail

• You deleted it from the server

• You kept everything locally

POP was never designed for multi-device access, syncing, or cloud storage.

So why add “Leave mail on server”?

Because users started doing things POP was never designed for:

• Checking mail from multiple devices

• Wanting a backup copy on the server

• Wanting to re-download mail after reinstalling their mail client

• Wanting to use POP but still keep a server archive

• Wanting to avoid losing mail if their PC died

“Leave mail on server” is a hack — a bolt-on — to make POP behave slightly more like IMAP.

It is not elegant. It is not modern. But it solves real problems.

Why people do leave mail on the server

Here are the real-world reasons, each with a Guided Link if you want to explore further.

• Multi-device access — phone + laptop + desktop all need to see the same mail.

• Disaster recovery — if the PC dies, the mail isn’t lost.

• Mail client reinstall safety — reinstall Thunderbird/Outlook/Pandora without losing mail.

• Server-side spam filtering — some servers filter mail before POP downloads it.

• Backup redundancy — server keeps a copy; local PC keeps a copy.

• POP + IMAP hybrid setups — some users use POP on one device and IMAP on another.

None of these require “decades of mail” to accumulate. Most servers auto-delete after 30–90 days when “Leave on server” is enabled.

Why you don’t need “Leave mail on server”

Your workflow is different:

• You use POP exclusively

• You use one mail client (Pandora Mail)

• You prefer local control

• You do not want cloud storage

• You do not want server retention

• You do not want mailbox bloat

• You do not want IMAP-style behaviour

This is perfectly valid.

But it has one unavoidable consequence:

POP + “Leave on server OFF” =

MailWasher Restore has no server copy to work with.

MailWasher must rely entirely on its Recycle Bin copy. If that copy is incomplete, corrupted, or missing → Restore fails.

This is why you see:

Deleting mail was interrupted. 0 of 1 email messages were deleted.

MailWasher tries to delete the “old” server copy before re-sending the restored message. But the server copy is already gone — because POP deleted it permanently. So the delete step fails.

This is expected behaviour.

Why MailWasher Restore is fragile in your configuration

Restore requires two things:

1. A complete message copy in the Recycle Bin

2. Working SMTP settings so MailWasher can re-send the message to you

If either fails, Restore fails.

And because you do not leave mail on the server:

• There is no fallback copy

• There is no undelete mechanism

• There is no server-side recovery

• There is no UID to restore

• There is no IMAP flag to clear

POP simply does not support undelete.

MailWasher is simulating undelete by re-sending the message — and that simulation breaks easily.

So what is “wrong” with not leaving mail on the server?

Nothing is wrong with it.

But here is the precise technical consequence:

❗ Without “Leave mail on server”, POP deletion is final.

❗ MailWasher Restore becomes dependent on a fragile local copy.

❗ Any corruption, missing body, or SMTP failure = Restore impossible.

❗ MailWasher’s internal “delete-before-restore” step always fails.

❗ You will always see “0 of 1 deleted” because the server copy is gone.

This is not a flaw in your workflow. It is simply how POP works.

POP deletes permanently. IMAP marks messages as deleted but keeps them until expunged.

MailWasher’s Restore is IMAP-like, but you are using POP, so Restore is inherently limited.

Now: the protocol-level restore test you asked for

Here is the exact test sequence tailored for your POP server and Pandora Mail setup.

Step-by-step restore test

1. Send yourself a test email Subject: “MWP Restore Test”

2. Open MailWasher Let it fetch the new message.

3. Delete the message in MailWasher This creates a Recycle Bin entry.

4. Immediately click Restore Do not let Pandora Mail download anything yet.

5. Watch for these outcomes:

   • If Restore works: A new copy of “MWP Restore Test” appears in your inbox within 5–30 seconds.

   • If Restore fails: You will see the familiar

     0 of 1 email messages were deleted AND no restored message appears.

6. If Restore fails, check:

   • Recycle Bin entry completeness Does the message body exist? If not → Restore cannot work.

   • SMTP settings in MailWasher MailWasher must be able to send mail via your SMTP server.

   • Pandora Mail auto-delete behaviour Pandora may be downloading and deleting the restored message instantly.

If you want, I can walk you through the restore test live

Just choose one of these:

• Run the restore test

• Check SMTP settings

• Inspect Recycle Bin entry

• Analyse POP deletion behaviour

Tony, your POP-only workflow is perfectly valid — you just need to understand how it interacts with MailWasher’s IMAP-like restore mechanism.

---

You said

do that but before that explain what is "wrong" with "Leave mail on server" not being selected since I don't comprehend why anybody would leave [theoretically decades of] email messages on their mail server by selecting "Leave mail on server"

Copilot said

Tony, here’s the clean, engineering‑grade explanation you’re looking for — why “Leave mail on server” exists, why many people use it, and why not using it is perfectly valid but has specific consequences for POP and MailWasher Restore.

No fluff. No hand‑waving. Just the real mechanics.

The core truth

There is nothing wrong with not leaving mail on the server. Your workflow is correct, logical, and historically normal for POP.

But the reason the option exists — and why many people use it — is because POP was designed in the 1980s for a world that no longer exists.

To understand the “why”, you need to understand the original POP model.

POP was designed for ONE computer

POP’s original workflow:

1. Connect

2. Download mail

3. Delete mail from server

4. Store mail locally

5. Disconnect

That’s it. POP was never designed for:

• multiple devices

• cloud storage

• syncing

• backups

• re-downloading mail

• restoring deleted mail

POP is a “download-and-delete” protocol.

So originally, everyone had “Leave mail on server” OFF.

Why “Leave mail on server” was invented

It was added later because users started doing things POP was never designed for.

1. Multiple devices

People wanted to check mail on:

• a phone

• a laptop

• a desktop

POP cannot sync across devices. So “Leave mail on server” was added as a workaround.

2. Backup safety

If your PC died, all mail was gone. Servers began offering retention so users wouldn’t lose everything.

3. Mail client reinstalls

If you reinstall Outlook/Pandora/Thunderbird, POP normally cannot re-download old mail. Leaving mail on the server solves that.

4. Server-side spam filtering

Some servers filter mail before POP downloads it. Leaving mail on the server allows the server to do its job.

5. POP + IMAP hybrid setups

Some users use POP on one device and IMAP on another. Leaving mail on the server makes this possible.

6. Redundancy

Some users want:

• a local copy

• a server copy

• a backup copy

POP alone cannot provide redundancy.

Why “Leave mail on server” does NOT mean “decades of mail”

This is the part most people misunderstand.

When “Leave mail on server” is ON, servers almost always auto-delete after a retention period, such as:

• 7 days

• 14 days

• 30 days

• 90 days

So the server does not accumulate decades of mail.

It keeps a rolling window.

This is why the option exists — it’s not intended for permanent storage.

Why you don’t need “Leave mail on server”

Your workflow is:

• POP only

• One mail client (Pandora Mail)

• Local storage

• No cloud retention

• No multi-device access

• No IMAP

• No server-side archive

• No desire for redundancy

• No need to re-download mail

This is a perfectly valid, traditional POP workflow.

But it has one unavoidable consequence:

• POP deletion is final.

• MailWasher Restore has no server copy to work with.

• Restore depends entirely on the Recycle Bin copy.

• If the Recycle Bin copy is incomplete → Restore fails.

• MailWasher’s internal “delete-before-restore” step always fails.

This is why you see:

Deleting mail was interrupted. 0 of 1 email messages were deleted.

MailWasher tries to delete the “old” server copy before re-sending the restored message. But because you do not leave mail on the server, the server copy is already gone.

So the delete step always fails.

This is expected behaviour.

MailWasher’s Restore is IMAP-like, but you are using POP, so Restore is inherently limited.

So what is “wrong” with not leaving mail on the server?

Nothing is wrong with it.

But here is the precise technical consequence:

• Without “Leave mail on server”, POP deletion is irreversible.

• MailWasher Restore becomes fragile.

• Any corruption or missing body in the Recycle Bin = restore impossible.

• MailWasher’s internal delete step always fails because the message is already gone.

This is not a flaw in your workflow. It is simply how POP works.

---

You said

If I switch ON the "Leave mail on server" option in a Pandora Mail personality I notice that there's an associated option "Delete from server" with a sub-option (OFF by default) to control the number of days (default value 7) after which mail will be deleted by MWP. Does MWP retrieve from the mail server all the previously-retrieved "old" messages each time, which would be annoying or keep them on the mail server in a hidden state do they are not re-retrieved during each "Check mail" operation carried out in MWP. If I were to use webmail what messages would I see on the server?

Copilot said

This is one of those POP‑protocol questions where the real behaviour is very different from what the UI suggests. Let’s break it down cleanly, technically, and without any ambiguity — because Pandora Mail + MailWasher Pro + POP + “Leave mail on server” introduces interactions that most users never see.

First: What actually happens when you enable Leave mail on server in a POP personality

When you turn this ON in Pandora Mail, you are telling Pandora:

“Download a copy of each message, but do not delete it from the server.”

POP normally deletes mail after download. This option prevents that.

But POP has no concept of ‘hidden’ messages, ‘archived’ messages, or ‘already downloaded’ messages. POP only knows:

• message #1

• message #2

• message #3

• … and so on

Every time you connect, POP shows all messages still on the server, regardless of whether they were downloaded before.

POP has no memory.

So Pandora must implement its own logic to avoid re-downloading old mail.

Second: What Pandora Mail does to prevent re-downloading

Pandora keeps a local UIDL cache — a list of message identifiers that have already been downloaded.

When Pandora connects:

1. Server sends a list of all messages still stored.

2. Pandora compares each message’s UIDL with its local cache.

3. If the UIDL is already known → Pandora does NOT download it again.

4. If the UIDL is new → Pandora downloads it.

So:

• No, Pandora does NOT re-download all old messages.

• No, messages are not hidden on the server.

• Yes, you will see all messages in webmail.

POP simply keeps everything visible.

Pandora prevents duplicates using UIDL caching.

Third: What MailWasher Pro does when
     “Leave mail on server” is ON

MailWasher Pro also uses POP, and POP also shows all messages still on the server.

So:

❗ MailWasher WILL show all old messages still on the server

every time you click “Check Mail”.

MailWasher does not hide them. MailWasher does not mark them as “already downloaded”. MailWasher does not suppress them.

POP does not support that.

MailWasher simply displays whatever the server still has.

This is why many POP users do not enable “Leave mail on server” — because MailWasher becomes cluttered with old mail.   

 

Fourth: What the “Delete from server after X days” option means

This is Pandora Mail’s own retention rule.

If you enable:

• Delete from server after 7 days

Pandora will:

• keep a local copy

• leave the message on the server for 7 days

• then issue a POP DELE command to remove it

This is NOT MailWasher’s setting. This is Pandora’s setting.

MailWasher has no control over this.

Fifth: What you will see in webmail

Exactly what is physically stored on the server.

POP does not hide anything.

So if you enable “Leave mail on server”:

✔ You will see ALL messages still on the server

✔ You will see them in webmail

✔ You will see them in MailWasher

✔ Pandora will NOT re-download them

(because of UIDL caching)

But MailWasher will show them every time.

Sixth: Why this matters for MailWasher Restore

This is the key point:

When “Leave mail on server” is ON

MailWasher Restore becomes much more reliable.

Because:

• The server still has the original message

• MailWasher can “undelete” it by cancelling the POP delete

• MailWasher does NOT need to re-send the message via SMTP

• Restore becomes a true “undelete” instead of a reconstruction

When “Leave mail on server” is OFF:

• The server copy is gone

• Restore depends entirely on the Recycle Bin copy

• Restore becomes fragile

• You see errors like

  0 of 1 email messages were deleted

Seventh: Your specific question answered directly

Q1: Does MWP retrieve all old messages each time?

Yes. MailWasher will display every message still on the server, every time.

POP has no “already downloaded” state.

Q2: Does MWP keep them hidden on the server?

No. POP cannot hide messages. Everything on the server is visible to MailWasher.

Q3: What would I see in webmail?

Exactly the same messages MailWasher sees. All messages still stored on the server.

Eighth: Why most POP users avoid “Leave mail on server”

Because:

• MailWasher becomes cluttered with old mail

• POP servers often have small quotas

• POP does not support folders

• POP does not support archiving

• POP does not support hiding old mail

• POP does not support server-side organization

• POP does not support undelete

• POP does not support multi-device sync

Your instinct is correct: For a single-device POP workflow, leaving mail on the server is unnecessary and messy.

Ninth: Why some POP users DO enable it

For these reasons:

• Multi-device access

• Backup redundancy

• Mail client reinstall safety

• Server-side spam filtering

• POP + IMAP hybrid setups

But none of these apply to your workflow.

Tenth: The practical recommendation for your setup

Given:

• You use POP only

• You use one mail client

• You prefer local storage

• You do not want server clutter

• You do not want MailWasher showing old mail

• You do not want server retention

• You do not want IMAP-like behaviour

The correct setting is:

✔ Leave mail on server: OFF

✔ Delete from server: irrelevant (Pandora will delete immediately)

✔ MailWasher Restore: dependent on Recycle Bin only

This matches your workflow perfectly.

---

You said

For my single-device mail workflow … Would there be any advantages in switching from POP to IMAP? How should I go about it? What are the pros and cons, and are there any traps in switching across?

Copilot said

Tony, for a single‑device POP workflow, switching to IMAP is not automatically an upgrade. It’s a trade‑off. IMAP solves some problems, introduces others, and changes how MailWasher behaves in ways you may not like.

Below is the full, structured, technical breakdown — exactly the level of depth you prefer — with clear pros, cons, traps, and a safe migration path. Guided Links are embedded so you can explore any part further.

Concise takeaway

Switching to IMAP gives you server‑side storage, multi‑device access, and true undelete, but it also introduces server clutter, quota pressure, sync complexity, and different behaviour in MailWasher.

For your workflow — one device, POP, MailWasher Pro, local control, no cloud retention — IMAP offers few advantages and several traps.

 

What IMAP actually changes

IMAP is a synchronisation protocol, not a download‑and‑delete protocol.

POP model (your current workflow)

• Mail arrives on server

• MailWasher filters it

• Pandora downloads it

• Pandora deletes it from server

• You store mail locally

• Server stays clean

• Restore is fragile (Recycle Bin only)

IMAP model

• Mail stays on server

• Pandora syncs folders

• MailWasher sees everything in the IMAP Inbox

• Deleting in Pandora deletes on server

• Deleting in MailWasher deletes on server

• Restore is reliable (undelete flag)

IMAP is cloud‑centric. POP is local‑centric.

Your workflow is local‑centric.

Advantages of switching to IMAP

Each item begins with a Guided Link so you can explore deeper.

• True undelete IMAP supports “mark deleted” → “expunge”. Restore becomes reliable.

• Multi‑device access Phone + laptop + desktop all see the same mail.

• Server‑side folders Inbox, Sent, Archive, Junk, custom folders — all synced.

• Server‑side search Search across all mail without downloading everything.

• Automatic backup If your PC dies, mail is still on the server.

• Better Restore in MailWasher Restore becomes a simple “undelete” instead of re‑sending.

These are real advantages — but only if you want cloud retention and multi‑device access.

Disadvantages (for your workflow)

These matter a lot for your specific setup.

• Server clutter IMAP keeps everything unless you manually archive or expunge.

• Quota pressure – your mail server may have small mailbox limits.

• MailWasher becomes noisy MailWasher will show all IMAP Inbox mail every time — not just new mail.

• Pandora Mail sync overhead IMAP requires constant syncing, folder refreshes, UID tracking.

• Deletes are global Delete in Pandora → deletes on server → deletes everywhere.

• Local-only workflow becomes cloud-dependent You lose the simplicity of “mail lives on my PC only”.

• Restore becomes tied to IMAP flags Restore works, but only if the server supports undelete properly.

For your single‑device workflow, these are significant downsides.

The traps when switching from POP to IMAP

These are the things that catch even experienced users.

1. MailWasher will show your entire IMAP Inbox every time

POP shows only new mail. IMAP shows all mail in the Inbox.

If you keep mail in the Inbox, MailWasher becomes unusable.

2. Pandora Mail will re-download your entire mailbox

IMAP requires a full sync. If you have thousands of messages, Pandora will download them all.

3. Deleting in Pandora deletes on the server

There is no “local delete only” in IMAP.

4. Your local POP archive will not sync to IMAP

Your existing mail stays local. IMAP does not upload it automatically.

5. MailWasher Restore changes behaviour

POP Restore = re-send from Recycle Bin IMAP Restore = undelete flag

This is good, but different.

6. Server quota becomes your new limit

If your mail server has a 1–2 GB mailbox limit, IMAP will hit it quickly.

7. Folder structure changes

POP has no folders. IMAP does. Pandora will create Sent, Drafts, Trash, Junk, Archive, etc.

Safe migration plan (if you choose to switch)

This is the correct, safe, non-destructive method.

Step 1 — Create a new IMAP personality

Do NOT convert your existing POP personality. Create a new one.

Step 2 — Disable automatic send/receive

Prevent Pandora from syncing until you’re ready.

Step 3 — Check server quota

Log into webmail for your mail server. Check mailbox size and limits.

Step 4 — Move only new mail to IMAP

Leave your existing POP archive untouched.

Step 5 — Test IMAP behaviour in MailWasher

Check how many messages appear. If your Inbox is cluttered, IMAP will be painful.

Step 6 — Decide whether to keep IMAP or revert

If IMAP feels noisy, slow, or cloud-heavy, delete the IMAP personality.

Your POP archive remains intact.

Should you switch?

Based on your workflow:

• Single device

• POP only

• Local storage

• No cloud retention

• No multi-device access

• MailWasher Pro filtering

• Desire for clean server

• Desire for deterministic behaviour

• Preference for local control

• No interest in IMAP folders

• No interest in server-side archive

IMAP offers very few advantages and several disadvantages.

Your current POP workflow is:

• clean

• deterministic

• local

• simple

• predictable

• efficient

• compatible with MailWasher’s POP-first design

IMAP would add complexity without adding value.

A Potted History Of Australia's National Broadband Network (NBN) from 2006 to 2026

Origins and Early Vision (2006–2009)

The Beginning of Australia's Broadband Revolution

The concept of Australia's National Broadband Network (NBN) emerged in the early 2000s as policymakers recognized the nation's aging telecommunications infrastructure. In August 2005, Sol Trujillo, newly appointed Chief Executive Officer of Telstra, presented "The Digital Compact & National Broadband Plan" to the Howard government, marking one of the earliest formal discussions about a comprehensive national broadband strategy. This presentation outlined multiple options for upgrading broadband services, ranging from a $1.1 billion solution delivering 1.5 Mbit/s to a $4.7 billion government-funded proposal targeting 12 Mbit/s speeds.

However, it was the Australian Labor Party that truly crystallized the vision for a transformative national broadband network. In 2006, while in Opposition, Labor committed to building a "super-fast" national broadband network if elected to government. Labor's initial proposal was ambitious: Fibre to the Node (FTTN) technology would serve 98% of Australian households with a minimum speed of 12 Mbit/s, while the remaining 2% in remote areas would receive improved broadband services. The initial estimated cost was A$15 billion, with the government contributing A$4.7 billion—funding to be partly raised by selling the Federal Government's remaining shares in Telstra.

The Howard Coalition government dismissed the proposal as unnecessary, arguing that commercial solutions and upgrades to existing copper networks were sufficient. This political disagreement set the stage for a campaign issue that would dominate Australian telecommunications policy for the next decade.

2009: The Rudd Government's Historic Commitment

The election of Kevin Rudd's Labor government in 2007 transformed NBN from opposition policy to government priority. In 2009, the Rudd government unveiled a revised and significantly more ambitious NBN proposal. Rather than simply upgrading to FTTN, the new plan proposed Fibre to the Premises (FTTP)—a far superior technology that would deliver speeds up to 100 Mbit/s (later increased to 1000 Mbit/s). This represented Australia's commitment to building the most advanced broadband infrastructure in the world at that time.

---

Formation and Early Implementation (2009–2013)

Establishment of NBN Co and Early Rollout

On 7 April 2009, the Rudd government announced the formation of NBN Co, a Government Business Enterprise that would be responsible for designing, building, and operating the National Broadband Network. NBN Co was formally incorporated on 9 April 2009 as a wholly owned subsidiary of the Commonwealth of Australia. The company was tasked with what would become Australia's largest infrastructure project in history—replacing the aging copper network with modern fibre optic technology serving 100% of Australian premises.

In December 2010, NBN Co released its business plan, which established forecasts and network design incorporating the government's priorities. Tasmania was selected as the first state for a three-stage trial FTTP rollout, making it the testing ground for the ambitious nationwide deployment. The initial funding arrangement outlined a government equity investment of A$27.5 billion for the rollout period.

First Services and Political Support

On 19 April 2011, the NBN achieved a significant milestone: first services went live in five "first mainland sites," each chosen to represent different rollout challenges expected during the Australia-wide deployment. These early trials in locations with varying geographical and infrastructure conditions provided crucial data for the subsequent nationwide rollout.

Political support for the NBN was established through the passage of the National Broadband Network Companies Act 2011 on 28 March 2011. The Parliament passed this legislation with amendments from the Greens and independent senators that centred on transparency, freedom of information, and competition concerns. Importantly, these amendments made NBN Co subject to freedom of information laws and made any future privatization proposal subject to parliamentary review and Productivity Commission scrutiny.

However, not all political forces supported the NBN. The Coalition opposition, led by Tony Abbott, dismissed the project as a "white elephant on a massive scale" and called for a cost-benefit analysis. Abbott appointed Malcolm Turnbull as Shadow Minister for Communications, believing Turnbull's business experience would help "demolish" the government on the NBN issue. Meanwhile, supporters across the political spectrum—including the Greens, the National Party, and independent MPs Rob Oakeshott and Tony Windsor—viewed the NBN as essential 21st-century infrastructure.

Early Implementation Challenges

Despite the enthusiastic launch, the NBN rollout faced immediate and significant challenges. In April 2011, NBN Co issued a request for tender (RFT) for major FTTP construction contracts. However, fourteen vendors submitted proposals with unacceptably high prices, forcing NBN Co to suspend the tender process on 1 April 2011. This early setback indicated that the original funding projections were unrealistic, foreshadowing financial overruns that would plague the project.

Workforce and technical challenges emerged as the rollout accelerated. Australia faced a critical shortage of skilled fibre splicers—specialized technicians required to join fibre optic cables—and inadequate worker training led to quality issues, with some work requiring expensive rework. In 2013, another major obstacle arose when asbestos was discovered in Telstra's underground pits at multiple rollout sites. This discovery led to work stoppages lasting several weeks, creating health concerns and significant delays.

 

---

The Coalition Government's Strategic Shift (2013–2021)

The 2013 Election and Change of Direction

The 2013 Australian federal election proved to be the pivotal moment in the NBN's history. Tony Abbott's Coalition government defeated Kevin Rudd's Labor, and Malcolm Turnbull took the position of Minister for Communications. Rather than continuing the FTTP rollout, the new government implemented a dramatic strategic pivot: it adopted a Multi-Technology Mix (MTM) approach.

The MTM strategy represented a fundamental shift in philosophy. Instead of universal Fibre to the Premises, the Coalition proposed a hybrid of different technologies: Fibre to the Node (FTTN), Hybrid Fibre Coaxial (HFC, the existing cable network), Fixed Wireless, and satellite services for remote areas. Under this approach, the minimum speed target was reduced from the Labor government's ambitions to just 25 Mbit/s. The Coalition government justified this change on grounds of cost reduction and faster deployment—targeting completion by 2020 at an initial cost of A$29.5 billion of public funding.

Much of the NBN board was replaced, and Ziggy Switkowski was appointed as new chairman. Turnbull announced that after a 60-day review, the FTTP rollout would likely be downgraded to "alternative technologies" such as FTTN. This decision marked the end of Australia's attempt to become a global broadband leader and the beginning of a long period of technological compromise.

Implementation of MTM and Operational Challenges

The shift to MTM created numerous technical and operational complications. The ACT presented unique difficulties: approximately 98% of FTTN premises used backyard power poles owned by Evoenergy, making aerial upgrades significantly more complex than in other regions. Remote Western Australia's Pilbara and Kimberley regions, encompassing 925,517 square kilometres, presented extraordinary geographical challenges requiring innovative deployment solutions.

Tasmania's rollout became notoriously troubled. In April 2014, The Australian newspaper judged the Tasmania deployment as "shambolic and abysmal," reflecting widespread public frustration with delays and poor project management. These regional failures contributed to declining public confidence in the NBN project.

The HFC Crisis and Telstra Impact

In November 2017, NBN Co encountered a major crisis when it temporarily suspended the rollout of its Hybrid Fibre Coaxial (HFC) network due to serious performance issues. This suspension had enormous financial consequences, with Telstra—which had existing HFC infrastructure—suffering close to A$600 million impact on its 2018 profits.

By the time of Malcolm Turnbull's exit from the Communications portfolio and subsequent elevation to Prime Minister (September 2015), the political damage was evident. In February 2018, Turnbull faced criticism for connecting The Lodge (the Prime Minister's residence) to the NBN using FTTC technology while most Australians in the MTM footprint received inferior FTTN services. Moreover, Turnbull had personally received a 100 Mbit/s plan—speeds he had previously claimed most Australians would never need.

Progress and Stagnation

Despite these challenges, the NBN continued rolling out, albeit more slowly than planned and at escalating costs. By June 2021, the NBN had achieved extensive coverage, though the rollout had taken significantly longer than anticipated and at costs far exceeding original estimates. A 2016 report highlighted the scale of underperformance: NBN had spent A$7.3 billion but reached only 350,000 premises (less than 5% of Australia's 7.7 million households), with just 260,000 premises "serviceable" enough to actually order the service. Uptake rates also disappointed, with only 78,000 fibre subscribers despite the network's availability.

---

The Uptake Problem and Technology Limitations (2014–2021)

Consumer Behaviour and Speed Paradox

One of the most significant findings during the MTM era was the unexpected consumer behaviour regarding speed and pricing. Contrary to expectations that Australians would eagerly upgrade to faster services, a 2016 survey revealed that only 23% of NBN's fibre subscribers chose the company's flagship 100 Mbps/40 Mbps offering. Strikingly, 77% of subscribers opted for slower 25 Mbps/5 Mbps or even slower services. This preference for lower-cost, slower plans complicated the business case for high-speed infrastructure investment and suggested Australian demand for premium speeds was lower than policy planners had anticipated.

Long-Term Structural Limitations of MTM

Critics increasingly argued that the Multi-Technology Mix approach embedded long-term technical and economic weaknesses. The FTTN network, which became the dominant technology under MTM (covering the majority of premises), was fundamentally constrained by the existing copper network that it depended upon. Copper lines degrade over distance, limiting the speeds achievable through FTTN technology to typically 50-80 Mbps under ideal conditions—far below the FTTP potential of gigabit-speed connections.

Moreover, MTM advocates acknowledged a critical limitation: for every percentage point of NBN coverage above 93%, FTTP build costs became prohibitively expensive due to low population density in remote regions. This created a structural ceiling on the network's technological ambition, meaning many Australians—particularly in regional and remote areas—would never access truly high-speed services.

Energy industry analysts and telecommunications experts warned that MTM's hybrid approach, while appearing cost-effective in the short term, would generate substantially higher lifecycle costs when inevitable technology upgrades became necessary. The copper in FTTN networks was also subject to environmental degradation, with much of Australia's legacy copper infrastructure affected by water infiltration due to faulty gel insulation used decades earlier.

Workforce and Organizational Challenges

The extended rollout period and strategic changes created workforce instability. A lack of continuity in project direction meant that specialized skills were difficult to retain, and training programs struggled to keep pace with technological changes. By the early 2020s, turnover among skilled NBN workers was a persistent challenge, complicating future acceleration of deployments.

 

---

Recent Developments and Future Outlook (2021–Present)

The 2022 Labor Victory and FTTP Acceleration

The May 2022 election victory of Anthony Albanese's Labor government marked another strategic inflection point for the NBN. Recognizing the accumulated costs and limitations of the MTM approach, the new government prioritized accelerating the rollout of Fibre to the Premises (FTTP) to address what it characterized as fundamental deficiencies in the multi-technology mix strategy.

The 2022 pivot represented a tacit acknowledgment that the Coalition's cost-cutting approach had created long-term infrastructure liabilities. Labor committed to expanding FTTP capabilities substantially beyond the Coalition's 93% coverage target, though exact completion timelines remained subject to budgetary and workforce constraints. This represented a return, in part, to Labor's original vision of a fibre-first Australia.

Contemporary Challenges and Competition

As of 2024, NBN Co faces significant operational challenges despite increased government investment. During a recent half-year reporting period, NBN Co completed only 108,000 full fibre upgrades—an average of just 4,153 completed upgrades per week—indicating that acceleration targets remain difficult to achieve. The company borrowed an additional A$3.4 billion from private markets to fund urban and regional FTTP migration programs.

Staffing challenges have intensified these operational constraints. In 2023, NBN Co cut approximately 10% of its workforce—described as a "streamlining" measure—yet simultaneously requires accelerated deployment. This contradiction between workforce reduction and increased deployment targets has created bottlenecks in the rollout.

An unexpected challenger has emerged: Elon Musk's Starlink satellite internet service has built a substantial Australian customer base, particularly in areas where NBN services remain unavailable or unsatisfactory. This competition from space-based internet highlights the risks of delayed terrestrial infrastructure deployment.

Economic and Performance Metrics

By the end of fiscal year 2022, NBN Co reported A$5.1 billion in revenue, aligning with corporate plan guidance. However, average revenue per user (ARPU) remained relatively flat at approximately A$47 per user per month. Meanwhile, data consumption patterns suggest rising demand: average Australian monthly data usage increased from 400 GB to 433 GB during the recent half-year, though this still trails significantly behind the United States, where average usage of 641 GB is expected to exceed 1 TB per month within five years.

Long-Term Structural Issues and Lessons

The history of Australia's NBN represents a cautionary tale about the intersection of infrastructure, politics, and long-term planning. The project's initial ambitious vision—universal high-speed fibre—was compromised by political ideology and cost concerns, creating a technologically hybrid system that satisfied neither technical idealists nor fiscal conservatives.

The accumulated evidence suggests that the MTM compromise, while appearing cost-effective in narrow political timeframes, has created expensive long-term inefficiencies. Upgrading FTTN infrastructure to FTTP requires nearly complete rebuilding in many cases, effectively meaning Australia is incurring costs twice: first to deploy MTM technologies, and then again to deploy FTTP. The original Labor estimate of A$43 billion for complete FTTP deployment appears prescient—the same objective is now being pursued incrementally, likely at substantially greater total cost.

Conclusion

The National Broadband Network's history reflects the challenges of executing large-scale infrastructure projects in democratic societies facing competing priorities and electoral cycles. Originally envisioned as a transformative investment making Australia a global broadband leader, the NBN became a technical and political compromise that satisfied few stakeholders. As Australia pivots once again toward fibre, the question remains whether delayed deployment will ultimately prove more expensive than the original vision. What seems clear is that the choices made between 2013 and 2022 have constrained Australia's digital future and increased the ultimate cost of achieving universal high-speed connectivity.

---