From: Andrew Hilborne <andrew.hilborne@gxn.net>
Cc: "(ding)" <ding@gnus.org>
Subject: Re: missing POP3 mail
Date: 17 Dec 1999 10:49:49 +0000 [thread overview]
Message-ID: <uawvqdalki.fsf@sapphire.noc.gxn.net> (raw)
In-Reply-To: Stainless Steel Rat's message of "Wed, 15 Dec 1999 10:41:16 -0500"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> * Andrew Hilborne <andrew.hilborne@gxn.net> on Wed, 15 Dec 1999
> | Quite possibly. But I worked with this particular _instance_ of qpopper for
> | years, used by thousands of dial-up and other users, and we suffered no such
> | problems. This is in contrast to pop3d which we used before that, which was
> | horrible.
>
> Well, like I said, if qpopper has the drop locked as you described, there
> is nothing pop3.el or any POP client can do to it.
This is not the issue. The issue is my suspicion that pop3.el has failed in its
duties (the overriding one being *never* to lose mail) in the face of this
behaviour on the part of qpopper, and possibly unexpected behaviour on my own
part.
Anyway, I can't prove any of this at this time, and clearly noone else knows
anything definitive about such a problem. So I'm going to shut up, until I have
time to try to reproduce it.
--
Andrew Hilborne
next prev parent reply other threads:[~1999-12-17 10:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-14 16:49 Andrew Hilborne
1999-12-14 17:03 ` Stainless Steel Rat
1999-12-14 17:44 ` Andrew Hilborne
1999-12-14 20:32 ` Stainless Steel Rat
1999-12-15 11:46 ` Andrew Hilborne
1999-12-15 15:41 ` Stainless Steel Rat
1999-12-17 10:49 ` Andrew Hilborne [this message]
1999-12-21 20:47 ` Kai Großjohann
1999-12-21 21:16 ` Stainless Steel Rat
1999-12-21 21:36 ` Kai Großjohann
1999-12-21 22:13 ` Stainless Steel Rat
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=uawvqdalki.fsf@sapphire.noc.gxn.net \
--to=andrew.hilborne@gxn.net \
--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).