From: Ken Raeburn <raeburn@cygnus.com>
Cc: ding@ifi.uio.no
Subject: Re: How to make pop3-movemail work?
Date: 08 Jan 1997 12:23:59 -0800 [thread overview]
Message-ID: <tx1pvzf531c.fsf@cygnus.com> (raw)
In-Reply-To: Rich Pieri's message of 08 Jan 1997 12:41:45 -0500
Rich Pieri <rich.pieri@prescienttech.com> writes:
> When I wrote pop3-movemail, it was intended to replace the call-process
> that invokes nnmail-movemail-program... and nnmail-movemail-program
> could go away because it is not needed anymore.
It'll still be needed for those of us using Kerberos-authenticated POP
service. Unfortunately, I don't think it's possible to use the
Kerberos code in a subprocess that doesn't have access to the network
file descriptor being used to talk to the POP server. (I looked into
this after seeing the pop3 code included.)
Ken
next prev parent reply other threads:[~1997-01-08 20:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-08 1:03 John Twilley
1997-01-08 16:07 ` Rich Pieri
1997-01-08 16:47 ` John Twilley
1997-01-08 17:41 ` Rich Pieri
1997-01-08 20:23 ` Ken Raeburn [this message]
1997-01-08 21:03 ` Rich Pieri
1997-01-08 21:38 ` William M. Perry
1997-01-08 22:30 ` Mark Eichin
1997-01-08 23:13 ` Rich Pieri
1997-01-09 1:17 ` Paul Franklin
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=tx1pvzf531c.fsf@cygnus.com \
--to=raeburn@cygnus.com \
--cc=ding@ifi.uio.no \
/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).