From: Jack Vinson <jvinson@chevax.ecs.umass.edu>
Subject: Re: pop3-movemail works with NTemacs 20.3.1
Date: 20 Apr 1999 15:52:52 -0500 [thread overview]
Message-ID: <wku2ubypy3.fsf@chevax.ecs.umass.edu> (raw)
In-Reply-To: Stainless Steel Rat's message of "Tue, 20 Apr 1999 14:35:06 -0400"
>>>>> "Rat" == Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> * Jack Vinson <jvinson@chevax.ecs.umass.edu> on Tue, 20 Apr 1999
> I don't know what has happened, but pop3-movemail now works with NTemacs.
Rat> It should never have broken, what as it was written originally for Emacs
Rat> running under Windows 95, specifically because movemail did not work.
After ruminating on this some more, I suspect I gave up on pop3-movemail
because of the other problems with mail-source around version 0.74. Of
course, I had problems with regular movemail as well.
All's well that ends well.
Jack
prev parent reply other threads:[~1999-04-20 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-20 15:04 Jack Vinson
1999-04-20 18:35 ` Stainless Steel Rat
1999-04-20 20:52 ` Jack Vinson [this message]
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=wku2ubypy3.fsf@chevax.ecs.umass.edu \
--to=jvinson@chevax.ecs.umass.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).