Gnus development mailing list
 help / color / mirror / Atom feed
From: Jack Vinson <jvinson@chevax.ecs.umass.edu>
Subject: pop3-movemail works with NTemacs 20.3.1
Date: 20 Apr 1999 10:04:47 -0500	[thread overview]
Message-ID: <wk1zhf8h9s.fsf@chevax.ecs.umass.edu> (raw)

I don't know what has happened, but pop3-movemail now works with NTemacs.
When we first switched to mail-sources and the default use of
pop3-movemail, I had problems with it not being able to grab mail off my
pop server.  I switched to using the movemail that was provided with
ntemacs (after not a little difficulty).

Today, I just tried pop3-movemail on a lark and it worked like a charm.  I
think I am going back to the elisp, since it gives me /some/ indication of
progress where movemail just sits there while it grabs all my mail.  After
a weekend of Lars brain dumps this takes quite a while.

-- 
Jack Vinson <jvinson@chevax.ecs.umass.edu>    http://www.cis.upenn.edu/~vinson/
Zippy: Is this "BIKINI BEACH"?



             reply	other threads:[~1999-04-20 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-20 15:04 Jack Vinson [this message]
1999-04-20 18:35 ` Stainless Steel Rat
1999-04-20 20:52   ` Jack Vinson

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=wk1zhf8h9s.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).