From: Rich Pieri <rich.pieri@PrescientTech.com>
Subject: Re: How to make pop3-movemail work?
Date: 08 Jan 1997 12:41:45 -0500 [thread overview]
Message-ID: <x768186p46.fsf@gkar.asds.com> (raw)
In-Reply-To: John Twilley's message of Wed, 08 Jan 1997 11:47:18 -0500
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "JT" == John Twilley <jmt@nda.com> writes:
JT> But nothing calls pop3-movemail, and it's not quite the right format
JT> for nnmail-movemail-program (which can take a function with two
JT> arguments -- pop3-movemail takes only one)
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. I have not been keeping
up with Red's development, so I have not seen a "new" version of
nnmail.el in quite a while. I should probably see to that before Red
goes out the door, eh?
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv
iQCVAwUBMtPcWp6VRH7BJMxHAQHC2QQApitwqjnH48Zz9mzRRryHfUdhC2DwP6Yd
n7INthN5yhVHyU0KFJpkfTUyBB4m7CK1soNwmVexEbOWWQNWTekZ5reYMCrmzWb2
SvaDi4ggzBe3aXeo8oo7XeSxBNUtaDwEA2ZDJulQfz2ZGArytnmHuCFHcsFzNqXx
OAVtQbn5ffc=
=WfF3
-----END PGP SIGNATURE-----
--
Rich Pieri <rich.pieri@prescienttech.com> | If Happy Fun Ball begins to smoke,
Prescient Technologies, Inc. | get away immediately. Seek shelter
A Stone & Webster Company | and cover head.
I speak for myself, not PTI or SWEC |
next prev parent reply other threads:[~1997-01-08 17:41 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 [this message]
1997-01-08 20:23 ` Ken Raeburn
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=x768186p46.fsf@gkar.asds.com \
--to=rich.pieri@prescienttech.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).