From: Steinar Bang <sb@metis.no>
Subject: VM pop, XEmacs, and Gnus (Was: POP3 - ...)
Date: 09 May 1997 19:40:19 +0200 [thread overview]
Message-ID: <whwwp8zgqk.fsf_-_@heidrun.troll.no> (raw)
In-Reply-To: wmperry@aventail.com's message of 06 May 1997 07:22:40 -0700
>>>>> wmperry@aventail.com (William M. Perry):
> Since I have plenty of memory on all my machines, I just load VM and
> use its pop retrieval stuff, like so:
> (setq vm-pop-max-message-size 21000
> nnmail-movemail-program 'my-movemail)
> (defun my-movemail (inbox crashbox)
> (require 'vm)
> (vm-pop-move-mail "aventail.com:110:pass:wmperry:*" crashbox)
> (vm-pop-move-mail "oz.net:110:pass:wmperry:*" crashbox))
Hm... is this all that's required? I tried compiling this on both GNU
emacs, and XEmacs, and both places, I've gotten the message:
** the function vm-pop-move-mail is not known to be defined.
both places, when byte compiling the .gnus.el file.
The VM directory, is in load-path. I've also tried using
(require 'vm-pop)
with the same response when byte compiling.
The reason I'm doing this, is that I haven't been able to run movemail
with POP, on XEmacs, and since I run demonical mail fetch, I can't use
pop3.el, because it asks for the password each time it fetches the
mail (or can I...? How does this apop stuff work? Does it negotiate a
session key? I think not, if I remember correctly, from the POP3 RFC.
Will I have to maintain a list of clear text "secrets" on the POP3
server, to use APOP?
(But for the time being, I'm back to Gnus in GNU Emacs 19.34, which
works fine, with movemail/POP, and demonical mail fetch. I just want
better support for richer mail content (inline images, and the like))
- Steinar
next prev parent reply other threads:[~1997-05-09 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-05-06 10:09 POP3 - long mails David Hedbor
1997-05-06 14:22 ` William M. Perry
1997-05-09 17:40 ` Steinar Bang [this message]
1997-05-06 16:33 ` Stainless Steel Rat
1997-05-06 19:05 ` David Hedbor
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=whwwp8zgqk.fsf_-_@heidrun.troll.no \
--to=sb@metis.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).