From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, Glenn Morris <rgm@gnu.org>
Cc: hengaini2055@qq.com, 26102@debbugs.gnu.org
Subject: bug#26102: movemail can't connect mail server
Date: Wed, 15 Mar 2017 15:48:50 -0700 [thread overview]
Message-ID: <cc1a01f6-33c9-7466-9d4c-8a4a317924e9@cs.ucla.edu> (raw)
In-Reply-To: <834lyu1jws.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]
On 03/15/2017 11:20 AM, Eli Zaretskii wrote:
> I'm against removing features for no good reason.
Sure, but there is a good reason here: Emacs movemail supports only
unencrypted POP3 connections, which has real security problems in
typical network environments today. Also, as can be seen earlier in this
thread, having two 'movemail' commands confuses users and can trip them up.
I take your point that there is a backwards-compatibility argument for
installing a movemail program that converts mailboxes from system format
to Emacs format, when GNU Mailutils is not available. However, we should
not distribute a movemail program that encourages users to read their
mail unencrypted over a network -- although that may have been OK in the
1980s when POP support was added to movemail, it's a grave disservice to
users in typical environments today.
Attached are two proposed patches to try to improve the current
situation. The first removes unencrypted POP3 support from Emacs
movemail, as it's a significant security blunder to insist on
unencrypted network connections these days. The second changes the Emacs
build procedure so that there is a configure-time option for whether to
install the substitute 'movemail' program instead of relying on GNU
Mailutils 'movemail'; the idea is to let distributors decide whether to
make GNU Mailutils be a prerequisite for reading email in Emacs.
[-- Attachment #2: 0001-Drop-POP-from-movemail.patch --]
[-- Type: application/x-patch, Size: 70902 bytes --]
[-- Attachment #3: 0002-Emacs-movemail-is-now-a-configure-time-option.patch --]
[-- Type: application/x-patch, Size: 12270 bytes --]
next prev parent reply other threads:[~2017-03-15 22:48 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cc1a01f6-33c9-7466-9d4c-8a4a317924e9@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=26102@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=hengaini2055@qq.com \
--cc=rgm@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.