From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: gray@gnu.org, carlosjosepita@gmail.com, bug-mailutils@gnu.org,
18278@debbugs.gnu.org
Subject: bug#18278: [PATCH] bug#18130: rmail.el: handle imaps, pops, and local source mailboxes (maildir, MH, etc.)
Date: Tue, 09 Sep 2014 16:19:40 +0300 [thread overview]
Message-ID: <83k35daq37.fsf@gnu.org> (raw)
In-Reply-To: <jwv4mwis1zh.fsf-monnier+emacsbugs@gnu.org>
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Date: Mon, 08 Sep 2014 09:00:22 -0400
> Cc: Carlos Pita <carlosjosepita@gmail.com>, bug-mailutils@gnu.org,
> 18278@debbugs.gnu.org
>
> [ Thanks Carlos for pinging us about it. ]
>
> > set of mailbox formats (both remote and local). This patch makes
> > rmail.el fully use the flexibility of GNU Mailutils. In particular,
> > it makes it possible to use imaps and pops encrypted protocols. The
> > patch is against the current Emacs trunk. The bug has been reported by
> > Carlos Pita to both GNU Emacs[2] and Mailutuls[3].
>
> Thank you Sergey,
>
> The patch looks OK for me, but as I'm not familiar with Rmail, I'd like
> to have the opinion of someone else.
I do use Rmail, but not movemail from Mailutils, and not for imap and
other modern protocols.
So the only issue that bothers me here is: would the new code still
work with the old movemail, and how does the code detect whether it
invokes old or new one?
If this change is 100% backwards compatible, I see no reasons not to
install it.
next prev parent reply other threads:[~2014-09-09 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 12:53 [PATCH] bug#18130: rmail.el: handle imaps, pops, and local source mailboxes (maildir, MH, etc.) Sergey Poznyakoff
2014-09-08 9:33 ` bug#18130: Fwd: " Carlos Pita
2014-09-08 13:00 ` bug#18278: " Stefan Monnier
2014-09-09 13:19 ` Eli Zaretskii [this message]
2014-09-09 15:46 ` Carlos Pita
2014-09-09 15:51 ` Eli Zaretskii
2017-04-09 1:44 ` Glenn Morris
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=83k35daq37.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18278@debbugs.gnu.org \
--cc=bug-mailutils@gnu.org \
--cc=carlosjosepita@gmail.com \
--cc=gray@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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.