Package: mutt / 1.10.1-2

Metadata

Package Version Patches format
mutt 1.10.1-2 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
debian specific/Muttrc.patch | (download)

doc/Muttrc.head | 39 37 + 2 - 0 !
1 file changed, 37 insertions(+), 2 deletions(-)

 muttrc

 * 2009-01-15 myon: refreshed for mutt-1.5.19; drop our list of ignored headers
   in favor of upstream's new unignore list

Signed-off-by: Matteo F. Vescovi <mfvescovi@gmail.com>

debian specific/882690 use_fqdn_from_etc_mailname.patch | (download)

init.c | 58 50 + 8 - 0 !
1 file changed, 50 insertions(+), 8 deletions(-)

---
debian specific/use_usr_bin_editor.patch | (download)

init.c | 2 1 + 1 - 0 !
init.h | 2 1 + 1 - 0 !
2 files changed, 2 insertions(+), 2 deletions(-)

 use_usr_bin_editor

Even if EDITOR is not set, mutt will always use /usr/bin/editor
(which is set by update-alternatives), rather than falling back
to vi.

debian specific/correct_docdir_in_man_page.patch | (download)

doc/mutt.man | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 correct_docdir_in_man_page

Fix the link so it points to the correct docdir
and gzipped manual.

debian specific/document_debian_defaults.patch | (download)

init.h | 19 19 + 0 - 0 !
1 file changed, 19 insertions(+)

 document_debian_defaults

Some customization of the option which are straying
from the default only on Debian systems.

debian specific/467432 write_bcc.patch | (download)

headers.c | 2 1 + 1 - 0 !
init.h | 21 1 + 20 - 0 !
main.c | 2 1 + 1 - 0 !
protos.h | 2 1 + 1 - 0 !
send.c | 4 2 + 2 - 0 !
sendlib.c | 6 3 + 3 - 0 !
6 files changed, 9 insertions(+), 28 deletions(-)

 467432-write_bcc
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

The purpose of this patch is to alter the behavior of the write_bcc option
because exim4, the default SMTP in Debian, does not strip the Bcc headers; by
default write_bcc is set so this could cause a privacy leak.

The behavior that this patch introduces is: never write the Bcc header when the
message is sent, otherwise, if the message is sent to Fcc, then this optin
will be evaluated and the Bcc header will be written based on that.

Background discussion on this is in the following bugs:
http://bugs.debian.org/304718
http://bugs.debian.org/467432

This patch is a slightly modified version of the patch provided by
Stefan Völkel <stefan@bc-bd.org> in the second bug.

debian specific/566076 build_doc_adjustments.patch | (download)

doc/Makefile.am | 6 2 + 4 - 0 !
1 file changed, 2 insertions(+), 4 deletions(-)

 566076-build_doc_adjustments

Use w3m to build the txt manual.

debian specific/828751 pinentry gpg2 support.patch | (download)

contrib/gpg.rc | 26 18 + 8 - 0 !
1 file changed, 18 insertions(+), 8 deletions(-)

---
misc/gpg.rc paths.patch | (download)

contrib/gpg.rc | 8 2 + 6 - 0 !
1 file changed, 2 insertions(+), 6 deletions(-)

 gpg.rc-paths

Use the correct path of pgpewrap.

misc/smime.rc.patch | (download)

contrib/smime.rc | 19 10 + 9 - 0 !
1 file changed, 10 insertions(+), 9 deletions(-)

 smime.rc

Add CA's provided by ca-certificates to the ones
distributed by the default installation of Mutt.

Signed-off-by: Matteo F. Vescovi <mfv@debian.org>

upstream/528233 readonly open.patch | (download)

attach.c | 7 6 + 1 - 0 !
1 file changed, 6 insertions(+), 1 deletion(-)

 528233-readonly-open

Open attachments as read-only so the editor won't be able to modify it;
otherwise the user can believe that he/she can edit it and risk to lose
his/her work (see upstream bug http://bugs.mutt.org/3261)

Debian bugs: #528233, updated in #572203

upstream/905551 oauthbearer imap.patch | (download)

imap/Makefile.am | 7 4 + 3 - 0 !
imap/auth.c | 1 1 + 0 - 0 !
imap/auth.h | 1 1 + 0 - 0 !
imap/auth_oauth.c | 104 104 + 0 - 0 !
imap/command.c | 1 1 + 0 - 0 !
imap/imap_private.h | 1 1 + 0 - 0 !
6 files changed, 112 insertions(+), 3 deletions(-)

 initial support for oauthbearer for imap.

commit 798f749eeeb98ed04028521a2eb3e505c1a83574 upstream.

Gmail supports RFC 7628 for using OAUTH with IMAP, and they really don't
like you using password based auth.  You can still enable "less secure
apps" and then generate an application specific password, but I figured it
was time to support it.

Being mutt, I punted on some of the "hard" work to an external script, ie
getting/refreshing the OAUTH tokens.  This avoids the issue of how do you
have a client-id and client-secret for an open source project, and the fact
that OAUTH discovery is still nascent, so you'd likely need separate things
for each of the providers.

At least for Gmail, you can use the oauth2.py script from Google's
gmail-oauth2-tools:
https://github.com/google/gmail-oauth2-tools/blob/master/python/oauth2.py

You'd need to get your own oauth client credentials for Gmail here:
https://console.developers.google.com/apis/credentials

Then, you'd use oauth2.py with --generate_oauth2_token to get a refresh
token, and configure mutt with:

set imap_authenticators="oauthbearer"
set imap_user="<email_address>"
set imap_pass=`/path/to/oauth2.py --quiet --user=<email_address>
--client_id=<client_id> --client_secret=<client_secret>
--refresh_token=<refresh_token>`

For this patch, I didn't add any new configuration, but I'm open to
suggestions on that.

The patch also only support SASL-IR to reduce round-trips to the server,
but it's certainly possible to change that if we think there are
OAUTHBEARER IMAP servers that don't support SASL-IR.  It also requires the
connection to be encrypted as the access token is re-usable for an hour or
so.  Again, Gmail only allows encrypted IMAP connections, not sure if any
OAUTHBEARER services allow non-encrypted.

Turns out that auth failure leaves you in SASL mode, so I have a hack to
issue a noop command on error.  Not sure if that's just OAUTHBEARER
oddness, or whether I should be using lower level mutt imap functions.

upstream/905551 oauthbearer smtp.patch | (download)

init.h | 2 0 + 2 - 0 !
smtp.c | 101 88 + 13 - 0 !
2 files changed, 88 insertions(+), 15 deletions(-)

 support for using oauthbearer for smtp.

commit fcd333986c0d15dec67870b7b74fef0e00e8c28b upstream.

This also means a bunch of smtp auth stuff is now compiled in by
default (with --enable-smtp) without having sasl

upstream/905551 oauthbearer refresh.patch | (download)

account.c | 80 80 + 0 - 0 !
account.h | 1 1 + 0 - 0 !
globals.h | 3 3 + 0 - 0 !
imap/auth_oauth.c | 57 17 + 40 - 0 !
init.h | 24 24 + 0 - 0 !
pop_auth.c | 71 69 + 2 - 0 !
smtp.c | 43 8 + 35 - 0 !
7 files changed, 202 insertions(+), 77 deletions(-)

 improve oauthbearer support.

commit 98cc42365ac97b0dfeafadf5561043e06744fcf6 upstream.

Move token refresh commands to their own config variables. Consolidate
code for refreshing tokens and generating the SASL OAUTHBEARER
argument in account.c. Add support for OAUTHBEARER to pop.

Fix pop_auth_oauth() mutt_from_base64() call from 1.10.1 release.