From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: eggert@cs.ucla.edu, 26102@debbugs.gnu.org, hengaini2055@qq.com
Subject: bug#26102: movemail can't connect mail server
Date: Fri, 17 Mar 2017 12:56:25 +0200 [thread overview]
Message-ID: <83efxwyxwm.fsf@gnu.org> (raw)
In-Reply-To: <m37f3o5gba.fsf@stories> (message from Lars Ingebrigtsen on Fri, 17 Mar 2017 11:49:13 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Fri, 17 Mar 2017 11:49:13 +0100
> Cc: eggert@cs.ucla.edu, hengaini2055@qq.com
>
> Paul Eggert <eggert@cs.ucla.edu> writes:
>
> > As the default Emacs configuration still has a significant security
> > hole, this patch changes 'configure' to warn about the problem if
> > present.
>
> Is there any reason rmail doesn't just use pop3.el instead of the
> movemail binary when speaking to pop3 servers?
I guess because no one wrote the code to support that. movemail
supports many different protocols, including /var/mail files etc., so
Rmail needs just rudimentary understanding of the inbox syntax spec to
invoke movemail correctly. To single out POP3 would need a bit more
code, but nothing too complicated, of course.
Patches welcome. (For backward compatibility, the old code that uses
movemail for POP3 should still be kept, I think, subject to some user
option.)
next prev parent reply other threads:[~2017-03-17 10:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 1:14 bug#26102: movemail can't connect mail server �ž��
2017-03-15 15:49 ` Eli Zaretskii
2017-03-15 17:30 ` Paul Eggert
2017-03-15 17:48 ` Eli Zaretskii
2017-03-15 18:15 ` Glenn Morris
2017-03-15 18:20 ` Eli Zaretskii
2017-03-15 20:03 ` Noam Postavsky
2017-03-16 3:31 ` Eli Zaretskii
2017-03-15 22:48 ` Paul Eggert
2017-03-16 15:31 ` Eli Zaretskii
2017-03-17 7:23 ` Paul Eggert
2017-03-17 8:58 ` Eli Zaretskii
2017-03-17 10:49 ` Lars Ingebrigtsen
2017-03-17 10:56 ` Eli Zaretskii [this message]
2017-03-16 0:15 ` Glenn Morris
2017-03-16 15:33 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83efxwyxwm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=26102@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=hengaini2055@qq.com \
--cc=larsi@gnus.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).