From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: jwiegley@gmail.com, eggert@cs.ucla.edu, 28597@debbugs.gnu.org,
nljlistbox2@gmail.com
Subject: bug#28597: 26.0.60; [Security] Configure should use --without-pop by default
Date: Fri, 29 Sep 2017 20:42:25 +0300 [thread overview]
Message-ID: <83a81d7666.fsf@gnu.org> (raw)
In-Reply-To: <87r2upd2h5.fsf@gmail.com> (message from Robert Pluim on Fri, 29 Sep 2017 16:05:42 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: John Wiegley <jwiegley@gmail.com>, nljlistbox2@gmail.com, eggert@cs.ucla.edu, 28597@debbugs.gnu.org
> Date: Fri, 29 Sep 2017 16:05:42 +0200
>
> I thought we were discussing making --without-pop be the default even
> if GNU Mailutils are not available, and it's what I'm
> advocating. Paul's patch only did that if they were found.
If that's what people want, fine with me on Posix platforms, but not
on MS-Windows (where Mailutils are not available, and probably never
will be).
> If that means that some people need to install GNU Mailutils, which
> support secure(r) protocols, then I'm all in favour.
But the effect of encouraging the installation of Mailutils will only
be achieved if the configure script displays something about that.
AFIU, the proposal was to make --without-pop the default and not
display any message, in which case people just get movemail without
POP3, and we might be silently breaking someone's setup. Do we want
that?
next prev parent reply other threads:[~2017-09-29 17:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 15:11 bug#28597: 26.0.60; [Security] Configure should use --without-pop by default N. Jackson
2017-09-25 15:21 ` John Wiegley
2017-09-26 9:13 ` Robert Pluim
2017-09-26 15:39 ` Glenn Morris
2017-09-26 17:22 ` Paul Eggert
2017-09-26 18:51 ` John Wiegley
2017-09-29 13:14 ` Eli Zaretskii
2017-09-29 14:05 ` Robert Pluim
2017-09-29 17:42 ` Eli Zaretskii [this message]
2017-09-29 20:04 ` Robert Pluim
2017-10-02 16:29 ` Robert Pluim
2017-10-02 18:23 ` Paul Eggert
2017-10-03 8:09 ` Robert Pluim
2017-10-03 14:34 ` Eli Zaretskii
2017-10-03 15:03 ` Robert Pluim
2017-10-03 15:42 ` Eli Zaretskii
2017-10-03 22:47 ` Paul Eggert
2017-10-04 7:14 ` Robert Pluim
2017-10-16 2:34 ` Noam Postavsky
2017-09-29 16:07 ` N. Jackson
2017-09-29 17:53 ` Eli Zaretskii
2017-09-29 18:14 ` N. Jackson
2017-09-29 19:11 ` Eli Zaretskii
2017-10-02 17:22 ` N. Jackson
2017-10-02 17:32 ` Eli Zaretskii
2017-10-02 18:00 ` Paul Eggert
2017-10-02 18:47 ` Eli Zaretskii
2017-10-02 23:20 ` Paul Eggert
2017-10-03 2:29 ` Eli Zaretskii
2017-10-03 14:29 ` N. Jackson
2017-10-03 14:55 ` Robert Pluim
2017-10-03 15:43 ` Eli Zaretskii
2017-10-02 18:00 ` Paul Eggert
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=83a81d7666.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28597@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=jwiegley@gmail.com \
--cc=nljlistbox2@gmail.com \
--cc=rpluim@gmail.com \
/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).