From: Paul Franklin <paul@cs.washington.edu>
Cc: John Twilley <jmt@NDA.COM>
Subject: Re: Hmm.. pop in gnus?
Date: 26 Feb 1997 12:33:42 -0800 [thread overview]
Message-ID: <r9qsp2je28p.fsf@fester.cs.washington.edu> (raw)
In-Reply-To: Christopher Davis's message of 26 Feb 1997 10:01:39 -0500
>>>>> Christopher Davis writes:
> PF> == Paul Franklin <paul@cs.washington.edu>
> PF> APOP is non-trivial though since the APOP code disappeared from the
> PF> FSF distribution about Emacs 19.29, and even if you resurrect the
> PF> required code, it needs to be installed setuid root.
> I think you're confusing APOP (which uses a challenge-response
> authentication) with RPOP (which used the rsh/rlogin approach).
Oops. You're quite right.
Sorry for any confusion and false hopes I might have given folks.
--Paul
next prev parent reply other threads:[~1997-02-26 20:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-02-25 15:06 Ben Gertzfield
1997-02-25 16:13 ` Kai Grossjohann
1997-02-25 23:37 ` Paul Franklin
1997-02-26 15:01 ` Christopher Davis
1997-02-26 20:33 ` Paul Franklin [this message]
1997-02-26 11:33 ` Hrvoje Niksic
1997-02-28 19:21 ` Albrecht Kadlec
1997-02-25 16:31 ` Rich Pieri
1997-02-25 18:12 ` Ben Gertzfield
1997-02-25 18:29 ` Rich Pieri
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=r9qsp2je28p.fsf@fester.cs.washington.edu \
--to=paul@cs.washington.edu \
--cc=jmt@NDA.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).