From: Florian Weimer <fw@deneb.enyo.de>
Cc: "(ding)" <ding@gnus.org>
Subject: Re: POP3 fragile?
Date: Wed, 16 Jul 2003 02:08:04 +0200 [thread overview]
Message-ID: <87oezvl4ez.fsf@deneb.enyo.de> (raw)
In-Reply-To: <m37k6j5oop.fsf@peorth.gweep.net> (Stainless Steel Rat's message of "Tue, 15 Jul 2003 19:56:54 -0400")
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> * Florian Weimer <fw@deneb.enyo.de> on Tue, 15 Jul 2003
> | Does unwind-protect catch C-g?
>
> Catch as in "mask the interrupt"? I believe not.
> Even if it does, the worst that can happen with stock pop3.el is that
> you'll have a bunch of stuff in the crashbox and copies of those messages
> on the server.
Are you sure? I read 'pop3-movemail' differently, IMHO "QUIT" is
always sent to the server (look at the placement of the call to
'pop3-quit').
> Recent versions of qpopper can be configured to automatically issue DELE
> commands after each successful RETR, to foil (ab)use of "leave mail on
> server". But even so, messages are not purged unless the client explicitly
> issues a QUIT command and closes the session gracefully. It may be that
> you have a hacked POP server that expunges messages immediately after a
> successful RETR.
It's an qpopper 4.0.5, unpatched, unconfigured, running on FreeBSD.
next prev parent reply other threads:[~2003-07-16 0:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 18:46 Florian Weimer
2003-07-14 22:50 ` Marcelo Toledo
2003-07-14 22:55 ` Xavier Maillard
2003-07-15 10:25 ` Florian Weimer
2003-07-15 13:15 ` Mike Woolley
2003-07-15 14:58 ` Stainless Steel Rat
2003-07-15 20:48 ` Florian Weimer
2003-07-15 21:07 ` Stainless Steel Rat
2003-07-15 21:45 ` Florian Weimer
2003-07-15 23:56 ` Stainless Steel Rat
2003-07-16 0:08 ` Florian Weimer [this message]
2003-07-16 3:38 ` Stainless Steel Rat
2003-07-16 2:29 ` Marcelo Toledo
2003-07-15 8:03 ` Kai Großjohann
2003-07-15 21:47 ` Florian Weimer
2003-07-15 23:47 ` Florian Weimer
2003-07-16 23:59 ` Matthias Andree
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=87oezvl4ez.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=ding@gnus.org \
/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).