From: Scott Gifford <sgifford@suspectclass.com>
Subject: Re: Deleting mail from server with pop3
Date: 14 May 2002 03:42:15 -0400 [thread overview]
Message-ID: <lyvg9rnpk8.fsf@gfn.org> (raw)
In-Reply-To: <m3bsbjc2yf.fsf@peorth.gweep.net>
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> * Paul Moore <gustav@morpheus.demon.co.uk> on Sun, 12 May 2002
> | What I would prefer would be to delete each message immediately after
> | it has been downloaded. I looked at the code in pop3.el, and there
> | doesn't seem to be a way to achieve this as the code stands. And my
> | elisp skills are definitely not up to something like this...
>
> That is impossible given how POP works.
>
> The DELE command marks messages for deletion. The only time that a POP
> server will expunge messages from the spool is if the connection closes
> cleanly. That is, when the client sends a QUIT command. If the connection
> drops then the server will remove the DELE marks once the server timeout
> has elapsed.
Some servers work this way, some do not. I used to use cucipop, which
didn't delete messages until a QUIT (although it had a compile-time
option to do the opposite); now my hosting provider users QPOP, and
that *does* delete messages if I just terminate the connection without
sending a QUIT.
One (annoying) way to get this behaviour guaranteed by all POP servers
is to fetch each message in its own POP session. A compromise is to
fetch a batch of messages (5-10-25) in each session, so if you do get
duplicates, at least it won't be that many...
-----ScottG.
prev parent reply other threads:[~2002-05-14 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-12 20:05 Paul Moore
2002-05-12 21:23 ` Adrian Aichner
[not found] ` <m3bsbjc2yf.fsf@peorth.gweep.net>
2002-05-14 7:42 ` Scott Gifford [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=lyvg9rnpk8.fsf@gfn.org \
--to=sgifford@suspectclass.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).