From: Richard Pieri <ratinox@unilab.dfci.harvard.edu>
Subject: Re: POP3 support
Date: 31 Jul 1996 17:12:20 -0400 [thread overview]
Message-ID: <x77mrk9lfv.fsf@unilab.dfci.harvard.edu> (raw)
In-Reply-To: Ken Raeburn's message of 31 Jul 1996 16:06:09 -0400
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "KR" == Ken Raeburn <raeburn@cygnus.com> writes:
KR> Just as long as I can still run movemail to talk to my pop server. I
KR> assume you didn't implement Kerberos authentication (including DES
KR> encryption) in elisp? :-)
Don't tempt me :).
Actually, implementing 'extensions' is simple because, unlike vm-pop,
pop3 does implement the full set of basic POP3 commands (except LIST
which is generally useless).
There are two reasons why I did not implement APOP. One, my POP server,
the Qualcomm qpopper, does not understand it so I cannot test it. Two,
I have not dug up a precompiled MD5 filter program for Win32, which is
where I have been doing most of my development work. This is currently
on the to-do list.
As for Kerberos... not a chance of that happening here, so if you want
to implement it, go for it.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv
iQCVAwUBMf/MNZ6VRH7BJMxHAQH1OQP+IxtYoIXYbBlxou5iUWxscXZFwjKMiPY2
9auFlZxmLBDelmAOx31c49DZ+leJr6AsPDmdnFYztyemGkUkX4pAnTMIrlbZxl1F
9pM+jlYoEphvK645/XdX97H8g/dc8BHLuBBhNSJpR2k8dl3XCsH0DvSyJGui86jJ
Uywozjvy69Y=
=8Xtw
-----END PGP SIGNATURE-----
--
Richard Pieri/Information Services \ Always give generously - a small bird or
<ratinox@unilab.dfci.harvard.edu> \ rodent left on the bed tells them, "I
http://www.dfci.harvard.edu/ \ care". -A cat's guide to life
next prev parent reply other threads:[~1996-07-31 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-31 16:08 Richard Pieri
1996-07-31 20:06 ` Ken Raeburn
1996-07-31 21:12 ` Richard Pieri [this message]
1996-07-31 23:05 ` William Perry
1996-08-01 13:49 ` Richard 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=x77mrk9lfv.fsf@unilab.dfci.harvard.edu \
--to=ratinox@unilab.dfci.harvard.edu \
/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).