From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: eggert@cs.ucla.edu, 26102@debbugs.gnu.org, hengaini2055@qq.com
Subject: bug#26102: movemail can't connect mail server
Date: Thu, 16 Mar 2017 05:31:53 +0200 [thread overview]
Message-ID: <831stx28ye.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV-9BCCqD8zo3X4axf7mM5O-ZbEDiHEW6=wSY8Qzm9zrzVQ@mail.gmail.com> (message from Noam Postavsky on Wed, 15 Mar 2017 16:03:18 -0400)
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Date: Wed, 15 Mar 2017 16:03:18 -0400
> Cc: Glenn Morris <rgm@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>, 26102@debbugs.gnu.org,
> hengaini2055@qq.com
>
> > We already find movemail from Mailutils, if installed, before we find
> > our own. And our movemail requires zero maintenance. In this
> > situation, removing our version means just removing features, no more,
> > no less. I'm against removing features for no good reason.
>
> Currently we release Emacs with a movemail implementation lacking the
> usual features. This may confuse users, like the OP.
> Is avoiding this confusion a good enough reason?
That confusion wouldn't be solved by removing our movemail, because 3
out of 4 problems in OP's command will also fail the version from
Mailutils, and the 4th is taken care of by Rmail, which converts the
pop:// "URL" to the "po:" form when it invokes movemail.
next prev parent reply other threads:[~2017-03-16 3:31 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 [this message]
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
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=831stx28ye.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=26102@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=hengaini2055@qq.com \
--cc=npostavs@users.sourceforge.net \
/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).