On 11/30/2011 12:53 AM, John H Meyers wrote:
> The purpose of "leave on server" is also basically
> to let other clients and computers download the same mail,
> and the purpose of "delete from server when deleted locally"
> is to save those other clients and computers
> the bother of downloading unwanted mail,
> only to have to be deleted again on the other client or computer.
In other words, the entire original intent
of both "leave on server" and "until I delete them"
was to help users maintain "home and office" computers
(or two POP users in the same office needing to work on the same mail)
in approximately the same state, or something analogous to that.
Now imagine that we've set an option
so that merely "filing" an incoming POP message,
on machine #1, in a folder relevant to its subject,
will cause the ultimate deletion of it anyway on the POP server,
because where we "file it" is not in the original "Inbox"
Now we go to our second, separate client machine
and download all new mail.
Do we get a copy of that same mail on machine #2?
No, because merely "filing it" on machine #1
will have made it unavailable to download to machine #2.
That's why the option in question,
rephrase-able in "POP speak" as "until I delete or even file them,"
is not the default, to say the least :)
That option is pretty much a confusion of IMAP with POP,
is how I see it.
Some server-side systems do exist in which
the same original IMAP "Inbox" on an incoming server
can also be accessed via POP protocol,
causing the moving of the message by an IMAP client
to make it unavailable to a POP client,
which seems to be how some deep thinkers may have concluded
to talk TB devs into providing an option
that makes some POP client have the same effect as another IMAP client,
however totally different these usually are, with IMAP clients
normally performing "move" _only_ at the server end of things,
while POP clients normally perform "move" _only_ on the client side,
far away from (and having no effect upon) any POP server.
Why didn't the mere existence of the unusual option,
which he not only knew of but had already set,
not satisfy the OP completely?
If it was because a case where a _manual_ "move" [case b]
between local mailboxes produced different results than
a "filtering move" between local mailboxes [case c],
then fine, this should have been the focus of the complaint,
but nowhere can I see where comparing to "copying" [case a],
where a message is simply filed in two places instead of one,
has any bearing on the matter, other than obviously not having
"moved" the original out of the "Inbox," which matters only
when the unusual option has been set.
In actual implementation of common options to "delete mail
left on a POP server if it's already been locally deleted,"
the information signifying "it was deleted"
is probably most often left in a simple database
equivalent to "popstate.dat" in TB, which remembers things
by means of "server-side message ids received by virtue of
a UIDL pop command" (not to be confused with "Message-ID"s
which come in message headers, which are completely unrelated :)
The most clever of clients takes note of messages being
actually finally deleted from a "Trash" mailbox,
and rushes over to change their status in "popstate.dat"
(hopefully made possible by the UIDL ids having been also remembered
in the .msf files which accompany all mailboxes including Trash),
so that upon the next contact with any POP server
("hey, do I have any new mail"?) there's a note in "popstate.dat"
which reminds TB to send the POP server a DELE command for those messages,
if indeed a brand new UIDL command has just listed their uids again,
even though all trace of those particular messages has otherwise
vanished from all other internal local storage files,
as "deleted" normally means.
This entire system naturally opens another opportunity for surprises
if a user has made any copies of some incoming messages,
or has "filed them in two or more places," to put it another way,
or has "downloaded all message headers" [again] to see what's
still hanging around on the POP server, and reviews that list,
to subsequently do Eudora-like things such as manually pick and choose
any of those to be [re]fetched or deleted now,
without regard to aging or anything else.
Suppose we have "filed the same message in two or more places" in TB,
and have NOT even set the unusual "delete if not still in Inbox" option,
and now we get an inexplicable urge to "eliminate duplicates" from TB.
If we forget having set even the "until I delete them" option,
our mere elimination of _duplicates_ in our local files
will end up inexorably causing "popstate.dat" to collect notes
to tell our old POP server to wipe those same messages off the server anyway,
even though we have _not really deleted them_ locally (we have only
deleted _duplicates_, if you're following this), and if we do all this
before we go home and check mail on our second computer,
or our co-worker comes back from lunch and checks mail on her computer,
then she's out of luck, because we weren't paying total attention
to the subtle implications of what we were doing!
If you are enjoying this post and haven't got a headache from reading it,
then hopefully what you can learn from it is that if you've routinely
been using "leave on server" and also have "until I delete them" set,
then remember to turn off "until I delete them" before you go around
deleting any duplicates (or even partially downloaded or "headers-only"
sorts of duplicates), because otherwise you'll have defeated "leave on server"
for all the messages you've just trimmed down to "I still have one copy
of that very important message in my mailboxes here,
so I presume that they're still on the server too" :)
The very safest thing to do, especially on Friday,
when "TGIF" is inclined to cause mental lapses
even worse than "texting while operating an email client,"
is to leave "until I delete them" off when not really sure
that you are focusing on work,
and pay the small price (a/k/a "insurance premium")
of (carefully) deleting them again on your other POP client :)
I've had to console workers who didn't find this out in time,
so take advantage of this free class in "Professional POPping,"
my fellow TB'ers :)
Oh darn, there's "just one more thing," as "Lieutenant Columbo"
(played by Peter Falk) used to say -- if your "POP server"
(and potentially also IMAP server) is provided by Gmail
(to which some ISPs even outsource their email systems),
then "moving out of Inbox" on the _server_ side
does _not_ stop POP from downloading it anyway,
unless you've moved it all the way to "Spam" or "Trash" or "Delete Forever";
in fact, so much is different about Gmail, as opposed to what "normal" POP
(or IMAP) servers do, that you should not even think about it until a Monday :)
--