From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
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: Tue, 03 Oct 2017 17:03:48 +0200 [thread overview]
Message-ID: <87d164l1d7.fsf@gmail.com> (raw)
In-Reply-To: <83poa41erm.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 03 Oct 2017 17:34:37 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Robert Pluim <rpluim@gmail.com>
>> Cc: Eli Zaretskii <eliz@gnu.org>, jwiegley@gmail.com, 28597@debbugs.gnu.org, nljlistbox2@gmail.com
>> Date: Tue, 03 Oct 2017 10:09:15 +0200
>>
>> I'm not wedded to the form, but I think configure should output
>> *something* to warn people about the change in behaviour. Or we go
>> full radical and disable building our own mailutils on non MS-Windows,
>> thus simplifying this mess greatly (we'd have to warn a bit more
>> loudly if GNU Mailutils aren't installed, though)
>
> Not building movemail if Mailutils are not installed is too harsh,
> because movemail supports methods other than POP3.
Does GNU Mailutils not support those same methods? I'm assuming it's
also maintained more than our movemail.
Robert
next prev parent reply other threads:[~2017-10-03 15:03 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
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 [this message]
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=87d164l1d7.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=28597@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=jwiegley@gmail.com \
--cc=nljlistbox2@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).