From: Daniel Simms <dsimms@alink.net>
Cc: ding@ifi.uio.no
Subject: Re: pop mailboxes
Date: 05 Feb 1997 00:35:43 -0800 [thread overview]
Message-ID: <x5zpxjtzts.fsf@ba.alink.net> (raw)
In-Reply-To: Rich Pieri's message of 04 Feb 1997 22:08:34 -0500
>>>>> "RP" == Rich Pieri <rich.pieri@PrescientTech.com> writes:
>>>> "DS" == Daniel Simms <dsimms@alink.net> writes:
DS>> (setq nnmail-movemail-program 'pop3-really-movemail)
DS>> (require 'pop3)
RP> This will not work. nnmail-movemail-program expects an external
RP> program, not a function.
Really?
>>>>> "I" == (gnus)Mail Backend Variables
I> `nnmail-movemail-program'
I> This program is executed to move mail from the user's inbox to her
I> home directory. The default is `movemail'.
I>
I> This can also be a function. In that case, the function will be
I> called with two parameters -- the name of the inbox, and the file
I> to be moved to.
>>>>> "N" == ~/emacs/packages/gnus-5.4.9/lisp/nnmail.el
[[...]]
N> ;; Function rewritten from rmail.el.
N> (defun nnmail-move-inbox (inbox)
[[...]]
N> ;; If getting from mail spool directory, use movemail to move
N> ;; rather than just renaming, so as to interlock with the
N> ;; mailer.
N> (unwind-protect
N> (save-excursion
N> (setq errors (generate-new-buffer " *nnmail loss*"))
N> (buffer-disable-undo errors)
N> (let ((default-directory "/"))
N> (if (nnheader-functionp nnmail-movemail-program)
N> (funcall nnmail-movemail-program inbox tofile)
N> (apply
N> 'call-process
N> (append
N> (list
N> (expand-file-name nnmail-movemail-program
N> exec-directory)
N> nil errors nil inbox tofile)
N> (when nnmail-internal-password
N> (list (prin1-to-string nnmail-internal-password)))))))
(Sorry, I'm already two versions out of date, but one was released
*while* I was writing this email.)
RP> At this time, nnmail also does not use pop3.el.
Well, I had kind of noticed that, but figured that it was just an
option. Setting nnmail-movemail-program is about the only thing you
really need to do to make gnus really use pop3.el.
RP> I had not gotten around to rewriting that section of nnmail
RP> before Red went into feature freeze.
I didn't noticed anything on the wish list (or mailing list) about
this. What did you have in mind? (This is more out of curiousity
than it is relevant to this particular thread.)
--
Daniel Simms "A common mistake that people make when trying to design
dsimms@alink.net something completely foolproof [is] to underestimate the
(408) 720-6161 ingenuity of complete fools" -Ford Prefect
next prev parent reply other threads:[~1997-02-05 8:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-02-03 23:32 Daniel Simms
1997-02-04 19:41 ` Lars Magne Ingebrigtsen
1997-02-04 23:00 ` Daniel Simms
1997-02-04 23:13 ` Lars Magne Ingebrigtsen
1997-02-04 23:55 ` Daniel Simms
1997-02-05 1:41 ` Lars Magne Ingebrigtsen
1997-02-05 5:03 ` Paul Franklin
1997-02-05 9:01 ` Daniel Simms
1997-02-05 3:08 ` Rich Pieri
1997-02-05 8:35 ` Daniel Simms [this message]
1997-02-05 16:13 ` Rich Pieri
1997-02-05 4:50 ` 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=x5zpxjtzts.fsf@ba.alink.net \
--to=dsimms@alink.net \
--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).