Bug#960160: Acknowledgement (mutt: stack overflow DoS fixed in 1.14)
Relevant upstream commit is 758d406ede97ad627ab804ab049e77396d18746c https://gitlab.com/muttmua/mutt.git
Bug#960160: mutt: stack overflow DoS fixed in 1.14
Package: mutt Version: 1.10.1-2.1 Severity: important Tags: upstream, security mutt 1.14 fixes a stack overflow when parsing a specially-crafted message.
Bug#671847: #3879: mutt: encoded-words are not decoded in mailto:
#3879: mutt: encoded-words are not decoded in mailto:
+--
Reporter: antonio@… | Owner: mutt-dev
Type: defect | Status: closed
Priority: major | Milestone:
Component: charset|Version: 1.7.0
Resolution: fixed | Keywords:
+--
Changes (by Kevin McCarthy <kevin@…>):
* status: reopened => closed
* resolution: => fixed
Comment:
In [changeset:"e0c0a2820b8b50c1e622181d4a6bbe7c1850a8ed"
6803:e0c0a2820b8b]:
{{{
#!CommitTicketReference repository=""
revision="e0c0a2820b8b50c1e622181d4a6bbe7c1850a8ed"
RFC2047-decode mailto url headers after RFC2822 parsing. (closes #3879)
Commit 55819a7e6169 performed the RFC2047 decode before the parsing.
This works okay for headers such as subject, but for others such as
address fields could lead to parsing errors.
Change to perform a decode on envelope headers after all the calls to
mutt_parse_rfc822_line(), using the same list of fields as
mutt_read_rfc822_header().
Change the do_2047 parameter of mutt_read_rfc822_line() to true, so
that user headers are decoded if needed.
}}}
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3879#comment:7>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Bug#671847: #3879: mutt: encoded-words are not decoded in mailto:
#3879: mutt: encoded-words are not decoded in mailto: +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: reopened Priority: major | Milestone: Component: charset|Version: 1.7.0 Resolution: | Keywords: +-- Changes (by kevin8t8): * Attachment "ticket-3879-v2.patch" added. -- Ticket URL: <https://dev.mutt.org/trac/ticket/3879> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#671847: #3879: mutt: encoded-words are not decoded in mailto:
#3879: mutt: encoded-words are not decoded in mailto: +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: reopened Priority: major | Milestone: Component: charset|Version: 1.7.0 Resolution: | Keywords: +-- Comment (by kevin8t8): I'm attaching a patch that takes the same approach as mutt_read_rfc822_header(). It changes the do_2047 parameter of mutt_parse_rfc822_line() to true (for user headers). Then it calls rfc2047_decode on all the other standard encoded header fields below (after the tokenizing and rfc822 parsing). I considered trying to keep track of which headers are in the mailto url, but given that the rfc2047_decode functions abort quickly if the header NULL, it seemed more likely to cause bugs than benefit. The copy/paste of fields from mutt_parse_rfc822_header() is also in somewhat poor taste, but I didn't think it was important enough to create a shared function for this. Feedback is most welcome! -- Ticket URL: <https://dev.mutt.org/trac/ticket/3879#comment:6> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#671847: #3879: mutt: encoded-words are not decoded in mailto:
#3879: mutt: encoded-words are not decoded in mailto: +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: reopened Priority: major | Milestone: Component: charset|Version: 1.7.0 Resolution: | Keywords: +-- Comment (by kevin8t8): Thanks Thomas. I figured there was a good reason mutt_read_rfc822_header() was doing it in that order, but couldn't figure out what it was! :-) I'll redo this today. -- Ticket URL: <https://dev.mutt.org/trac/ticket/3879#comment:5> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#671847: #3879: mutt: encoded-words are not decoded in mailto:
#3879: mutt: encoded-words are not decoded in mailto:
+--
Reporter: antonio@… | Owner: mutt-dev
Type: defect | Status: reopened
Priority: major | Milestone:
Component: charset|Version: 1.7.0
Resolution: | Keywords:
+--
Changes (by roessler@…):
* cc: kevin@…, antonio@… (added)
* status: closed => reopened
* resolution: fixed =>
Comment:
{{{
You should do the RFC 2822 parse first, then the decode -- 2047 is
specifically written so it parses as one token.
Thomas Roessler (@roessler)
On Tue, Sep 27, 2016 at 6:17 PM, Mutt <fl...@mutt.org> wrote:
}}}
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3879#comment:4>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Bug#671847: #3879: mutt: encoded-words are not decoded in mailto:
#3879: mutt: encoded-words are not decoded in mailto:
+--
Reporter: antonio@… | Owner: mutt-dev
Type: defect | Status: closed
Priority: major | Milestone:
Component: charset|Version: 1.7.0
Resolution: fixed | Keywords:
+--
Changes (by Kevin McCarthy <kevin@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"55819a7e61695bffea31646464183fcb2d54899d"
6802:55819a7e6169]:
{{{
#!CommitTicketReference repository=""
revision="55819a7e61695bffea31646464183fcb2d54899d"
RFC2047-decode mailto header values. (closes #3879)
RFC 6068 specifies that the header values (with the exception of body)
may contain RFC 2047-encoded values.
}}}
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3879#comment:2>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Bug#671847: #3879: mutt: encoded-words are not decoded in mailto:
#3879: mutt: encoded-words are not decoded in mailto: +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: charset|Version: 1.7.0 Resolution: | Keywords: +-- Changes (by kevin8t8): * Attachment "ticket-3879.patch" added. -- Ticket URL: <https://dev.mutt.org/trac/ticket/3879> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#671847: #3879: mutt: encoded-words are not decoded in mailto:
#3879: mutt: encoded-words are not decoded in mailto: +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: charset|Version: 1.7.0 Resolution: | Keywords: +-- Comment (by kevin8t8): I'm attaching a proposed patch. This just adds a rfc2047 decode call for the header values (with the exception of body). I think this should solve the problem for the basic "subject" case. One concern I have is for other address fields, e.g. Cc, whether doing the decode before the mutt_parse_rfc822_line() call is acceptable. I'll have to think about that a bit more before I commit it. -- Ticket URL: <https://dev.mutt.org/trac/ticket/3879#comment:1> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#671847: #3879: mutt: encoded-words are not decoded in mailto:
#3879: mutt: encoded-words are not decoded in mailto: ---+-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: charset|Version: 1.7.0 Keywords: | ---+-- From http://bugs.debian.org/671847 (Confirmed in 1.7.0) When fed the following example from RFC 6068: $ mutt 'mailto:u...@example.org?subject=%3D%3Fiso-8859-1%3FQ%3Fcaf%3DE9%3F%3D' The subject line is not properly decoded to "café" as per RFC 2047, and remains "=?iso-8859-1?Q?caf=E9?=". -- Ticket URL: <https://dev.mutt.org/trac/ticket/3879> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#837372: #3872: when using gpgme, the signature information is brightyellow making it difficult to read
#3872: when using gpgme, the signature information is brightyellow making it
difficult to read
+--
Reporter: antonio@… | Owner: mutt-dev
Type: defect | Status: closed
Priority: minor | Milestone:
Component: crypto |Version: 1.7.0
Resolution: fixed | Keywords:
+--
Changes (by Antonio Radici <antonio@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"405cbc43c3acc6cec944110f4a8d8b0b1977d4f8"
6793:405cbc43c3ac]:
{{{
#!CommitTicketReference repository=""
revision="405cbc43c3acc6cec944110f4a8d8b0b1977d4f8"
Use body color for gpgme output. (closes #3872)
When switching from pgp_* commands to crypt_use_gpgme=yes, Peter
Colberg noticed that the output was colored 'brightyellow'.
The issue is that crypt-gpgme.c uses state_attach_puts in various
places where it should use state_puts to maintain compatibility with
the previous behavior in pgp.c.
}}}
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3872#comment:3>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Bug#837372: #3872: when using gpgme, the signature information is brightyellow making it difficult to read
#3872: when using gpgme, the signature information is brightyellow making it difficult to read +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: new Priority: minor | Milestone: Component: crypto |Version: 1.7.0 Resolution: | Keywords: +-- Comment (by kevin8t8): Thanks Antonio. The analysis looks correct to me. We only want to tag the "[--..." output with the attachment marker. I'll take a closer look at the patch tomorrow. -- Ticket URL: <https://dev.mutt.org/trac/ticket/3872#comment:2> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#837372: #3872: when using gpgme, the signature information is brightyellow making it difficult to read
#3872: when using gpgme, the signature information is brightyellow making it difficult to read +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: new Priority: minor | Milestone: Component: crypto |Version: 1.7.0 Resolution: | Keywords: +-- Comment (by antonio@…): I've investigated and I'm providing you with the same patch that I'll add to the debian package. It seems that the output of pgp.c is written with state_puts(), while the output of crypt-gpgme.c has state_attach_puts(). It might make sense to use state_attach_puts() for the lines with [--] but we still want to preserve the same behavior of pgp.c for the content. Another option is to provide a feature to have a different color for crypto output (it might be called crypto and we could provide state_crypto_puts()); I might provide a patch for this particular feature next weekend (I'll file a separate bug for that). -- Ticket URL: <https://dev.mutt.org/trac/ticket/3872#comment:1> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#837372: #3872: when using gpgme, the signature information is brightyellow making it difficult to read
#3872: when using gpgme, the signature information is brightyellow making it difficult to read +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: new Priority: minor | Milestone: Component: crypto |Version: 1.7.0 Resolution: | Keywords: +-- Changes (by antonio@…): * Attachment "837372-do-not-color-gpgme-output.patch" added. -- Ticket URL: <https://dev.mutt.org/trac/ticket/3872> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#837372: #3872: when using gpgme, the signature information is brightyellow making it difficult to read
#3872: when using gpgme, the signature information is brightyellow making it difficult to read ---+-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: new Priority: minor | Milestone: Component: crypto |Version: 1.7.0 Keywords: | ---+-- How to reproduce: (1) set crypt_use_gpgme=yes (2) open mutt and check a signed email, the verification output is brightyellow While: (1) set crypt_use_gpgme=no (2) open mutt and check a signed email, the verification output is the same color as the text. We would like to get the second behavior for gpgme too, because otherwise the text is too difficult to read -- Ticket URL: <https://dev.mutt.org/trac/ticket/3872> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#624111: #3868: mutt should error if the imported mailbox is invalid
#3868: mutt should error if the imported mailbox is invalid +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: mutt |Version: 1.7.0 Resolution: | Keywords: +-- Comment (by antonio@…): More context about this problem is in the Debian bug -- Ticket URL: <https://dev.mutt.org/trac/ticket/3868#comment:1> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#624111: #3868: mutt should error if the imported mailbox is invalid
#3868: mutt should error if the imported mailbox is invalid ---+-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: mutt |Version: 1.7.0 Keywords: | ---+-- Forwarding from http://bugs.debian.org/624111 Mutt fails to display the messages in the decompressed archives from Freedesktop.org. 1. messages not displayed, just a few with bo...@does.not.exist.com $ wget http://lists.freedesktop.org/archives/intel- gfx/2011-April.txt.gz --2011-04-25 17:54:48-- http://lists.freedesktop.org/archives /intel-gfx/2011-April.txt.gz Auflösen des Hostnamen lists.freedesktop.org... 131.252.210.177 Verbindungsaufbau zu lists.freedesktop.org|131.252.210.177|:80... verbunden. HTTP-Anforderung gesendet, warte auf Antwort... 200 OK Länge: 465348 (454K) [application/x-gzip] In »2011-April.txt.gz« speichern. 100%[==>] 465.348 53,4K/s in 7,5s 2011-04-25 17:54:56 (60,8 KB/s) - »2011-April.txt.gz« gespeichert [465348/465348] $ gunzip 2011-April.txt.gz $ mutt -f 2011-April.txt # just shows the following 1 Apr 12 bo...@does.not. (63100) No subject $ # trying to display the above message shows the raw mbox file Date: Tue, 12 Apr 2011 21:12:25 - From: bo...@does.not.exist.com Subject: No subject […] 2. messages not displayed at all $ wget http://lists.freedesktop.org/archives/dri- devel/2010-March.txt.gz $ gunzip 2010-March.txt.gz $ mutt -f 2010-March.txt # no messages are displayed I can import both decompressed archives using Evolution just fine. -- Ticket URL: <https://dev.mutt.org/trac/ticket/3868> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#741213: #3867: pgpring displays an incorrect length for DSA and Elgamal keys
#3867: pgpring displays an incorrect length for DSA and Elgamal keys
+--
Reporter: antonio@… | Owner: mutt-dev
Type: defect | Status: closed
Priority: major | Milestone:
Component: crypto |Version: 1.7.0
Resolution: fixed | Keywords:
+--
Changes (by Guilhem Moulin <guilhem@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"b082bcd5d5e225a29df0a3406d3863a9f5573137"
6780:b082bcd5d5e2]:
{{{
#!CommitTicketReference repository=""
revision="b082bcd5d5e225a29df0a3406d3863a9f5573137"
Fix pgpring reporting of DSA and Elgamal key lengths. (closes #3867)
Patch provided by Guilhem Moulin from an original idea of Fabrizio
Tarizzo.
The key length is always the length of the first MPI for RSA, DSA, and
Elgamal.
}}}
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3867#comment:1>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Bug#741213: #3867: pgpring displays an incorrect length for DSA and Elgamal keys
#3867: pgpring displays an incorrect length for DSA and Elgamal keys ---+-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: crypto |Version: 1.7.0 Keywords: | ---+-- does not look at the right field as key lengh for DSA and Elgamal keys, which results to an incorrect output. The attached patch fixes the proble, this was reported in the Debian bug http://bugs.debian.org/741213 -- Ticket URL: <https://dev.mutt.org/trac/ticket/3867> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#741213: #3867: pgpring displays an incorrect length for DSA and Elgamal keys
#3867: pgpring displays an incorrect length for DSA and Elgamal keys +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: crypto |Version: 1.7.0 Resolution: | Keywords: +-- Changes (by antonio@…): * Attachment "741213-dsa-elgamal-keys-length.patch" added. -- Ticket URL: <https://dev.mutt.org/trac/ticket/3867> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#529250: #3232: deleting attachement changes sort order of message when using 'date-received'
#3232: deleting attachement changes sort order of message when using 'date- received' +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: closed Priority: minor | Milestone: Component: display|Version: 1.5.20 Resolution: fixed | Keywords: +-- Changes (by antonio@…): * status: new => closed * resolution: => fixed Comment: fixed on 1.7.0-1 -- Ticket URL: <https://dev.mutt.org/trac/ticket/3232#comment:3> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#530671: #3242: mutt: does not want to open dot subdirs via imap anymore
#3242: mutt: does not want to open dot subdirs via imap anymore +--- Reporter: antonio@… | Owner: lucki2791 Type: task | Status: accepted Priority: major | Milestone: 2.0 Component: browser|Version: 1.5.21 Resolution: | Keywords: +--- Comment (by antonio@…): Are we going to fix this? It would be great if we do! -- Ticket URL: <https://dev.mutt.org/trac/ticket/3242#comment:8> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#545814: #3807: query_format should handle unicode string
#3807: query_format should handle unicode string -+-- Reporter: antonio@…| Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: display |Version: Keywords: | -+-- Hi, it will be great if query_format could handle unicode string, at the moment it is not the case and strings like: Дмитрий Эдуардович get truncated based on the precision specified in query_format, so if I specify %2n, I will only get the first character rather than the first two (because there are 2 bytes in Д) snprintf already handles this case if %ls is specified rathern than %s, I've had a look at query_format_str but I've been unable to patch it properly (I think that the caller might also do other things with the output). -- Ticket URL: <http://dev.mutt.org/trac/ticket/3807> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#530584: #3236: mutt: should use /var/tmp for mail drafts by default
#3236: mutt: should use /var/tmp for mail drafts by default --+-- Reporter: antonio@…| Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt |Version: Resolution: | Keywords: --+-- Changes (by chrysn): * cc: chrysn@… (added) -- Ticket URL: <http://dev.mutt.org/trac/ticket/3236#comment:16> Mutt <http://www.mutt.org/> The Mutt mail user agent
Bug#572702: #3495: q and x in help menu should only appear once
#3495: q and x in help menu should only appear once
+--
Reporter: antonio@… | Owner: mutt-dev
Type: defect | Status: closed
Priority: trivial| Milestone:
Component: mutt |Version: 1.5.21
Resolution: wontfix| Keywords:
+--
Changes (by myon):
* status: new = closed
* resolution: = wontfix
Old description:
Forwarding from http://bugs.debian.org/572702
{{{
In the ? help screen, one sees
q quit save changes to mailbox and quit
x exit exit this menu
q exit exit this menu
Well, the x should be changed to match
/usr/share/doc/mutt/manual.txt.gz:
xabort changes and exit
And I would perhaps just use a special line somewhere:
to exit this menu, press q or x.
Else the user might notice one q but not the other...
}}}
New description:
Forwarding from http://bugs.debian.org/572702
{{{
In the ? help screen, one sees
q quit save changes to mailbox and quit
x exit exit this menu
q exit exit this menu
Well, the x should be changed to match
/usr/share/doc/mutt/manual.txt.gz:
xabort changes and exit
And I would perhaps just use a special line somewhere:
to exit this menu, press q or x.
Else the user might notice one q but not the other...
}}}
--
--
Ticket URL: http://dev.mutt.org/trac/ticket/3495#comment:2
Mutt http://www.mutt.org/
The Mutt mail user agent
Bug#530671: #3242: mutt: does not want to open dot subdirs via imap anymore
#3242: mutt: does not want to open dot subdirs via imap anymore +--- Reporter: antonio@… | Owner: lucki2791 Type: task | Status: accepted Priority: major | Milestone: 2.0 Component: browser|Version: 1.5.21 Resolution: | Keywords: +--- Changes (by grawity): * cc: grawity@… (added) -- Ticket URL: http://dev.mutt.org/trac/ticket/3242#comment:7 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#624058: #3515: Remove deprecated _set_priority GnuTLS functions (patch available)
#3515: Remove deprecated _set_priority GnuTLS functions (patch available) +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: closed Priority: minor | Milestone: Component: crypto |Version: 1.5.21 Resolution: fixed | Keywords: patch +-- Changes (by ametzler): * status: reopened = closed * resolution: = fixed Comment: kevin8t8 wrote: ''The usage of gnutls_protocol_set_priority() is contained in an #else/#endif block, which should only be compiled if the function gnutls_priority_set_direct() is not found by configure.'' You are absolutely right. I am very sorry for the noise. cu Andreas -- Ticket URL: http://dev.mutt.org/trac/ticket/3515#comment:6 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#624058: #3515: Remove deprecated _set_priority GnuTLS functions (patch available)
#3515: Remove deprecated _set_priority GnuTLS functions (patch available) +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: reopened Priority: minor | Milestone: Component: crypto |Version: 1.5.21 Resolution: | Keywords: patch +-- Changes (by ametzler): * status: closed = reopened * resolution: fixed = Comment: Current HG is broken, it uses gnutls_protocol_set_priority() and therefore fails to build with GnuTLS 3.4. -- Ticket URL: http://dev.mutt.org/trac/ticket/3515#comment:4 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#624058: #3515: Remove deprecated _set_priority GnuTLS functions (patch available)
#3515: Remove deprecated _set_priority GnuTLS functions (patch available)
+--
Reporter: antonio@… | Owner: mutt-dev
Type: defect | Status: reopened
Priority: minor | Milestone:
Component: crypto |Version: 1.5.21
Resolution: | Keywords: patch
+--
Comment (by kevin8t8):
The usage of gnutls_protocol_set_priority() is contained in an
#else/#endif block, which should only be compiled if the function
gnutls_priority_set_direct() is not found by configure.
Can you re-run configure and confirm what this section of the output looks
like for you:
{{{
checking for gnutls_check_version in -lgnutls... yes
checking whether GNUTLS_VERIFY_DISABLE_TIME_CHECKS is declared... yes
checking for gnutls_priority_set_direct... yes
checking for gnutls_certificate_credentials_t... yes
checking for gnutls_certificate_status_t... yes
checking for gnutls_datum_t... yes
checking for gnutls_digest_algorithm_t... yes
checking for gnutls_session_t... yes
checking for gnutls_transport_ptr_t... yes
checking for gnutls_x509_crt_t... yes
}}}
--
Ticket URL: http://dev.mutt.org/trac/ticket/3515#comment:5
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606742: #3488: mail-key function is broken when crypt_use_gpgme is set
#3488: mail-key function is broken when crypt_use_gpgme is set
+--
Reporter: antonio@… | Owner: kevin8t8
Type: defect | Status: closed
Priority: trivial| Milestone:
Component: mutt |Version: 1.5.21
Resolution: fixed | Keywords:
+--
Changes (by Kevin McCarthy kevin@…):
* status: assigned = closed
* resolution: = fixed
Comment:
In [ec93761e3e129e7ff7d81c892a69c5b2a89a832d]:
{{{
#!CommitTicketReference repository=
revision=ec93761e3e129e7ff7d81c892a69c5b2a89a832d
Implement mail-key, Esc-K, for gpgme. (closes #3488)
This patch implements the make-key-attachment function for gpgme,
modeled after the pgp version.
It also adds an optional tempf parameter to data_object_to_tempfile() so
the function can be reused for make-key-attachment.
}}}
--
Ticket URL: http://dev.mutt.org/trac/ticket/3488#comment:4
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606742: #3488: mail-key function is broken when crypt_use_gpgme is set
#3488: mail-key function is broken when crypt_use_gpgme is set +-- Reporter: antonio@… | Owner: kevin8t8 Type: defect | Status: assigned Priority: trivial| Milestone: Component: mutt |Version: 1.5.21 Resolution: | Keywords: +-- Comment (by kevin8t8): Attaching a patch that implements the missing function. -- Ticket URL: http://dev.mutt.org/trac/ticket/3488#comment:3 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606742: #3488: mail-key function is broken when crypt_use_gpgme is set
#3488: mail-key function is broken when crypt_use_gpgme is set +-- Reporter: antonio@… | Owner: kevin8t8 Type: defect | Status: assigned Priority: trivial| Milestone: Component: mutt |Version: 1.5.21 Resolution: | Keywords: +-- Changes (by kevin8t8): * owner: mutt-dev = kevin8t8 * status: new = assigned -- Ticket URL: http://dev.mutt.org/trac/ticket/3488#comment:2 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606742: #3488: mail-key function is broken when crypt_use_gpgme is set
#3488: mail-key function is broken when crypt_use_gpgme is set +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: new Priority: trivial| Milestone: Component: mutt |Version: 1.5.21 Resolution: | Keywords: +-- Changes (by na57teku): * cc: bugs-mutt@… (added) -- Ticket URL: http://dev.mutt.org/trac/ticket/3488#comment:1 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#481500: #3247: mutt: should provide options for cipher selections
#3247: mutt: should provide options for cipher selections --+-- Reporter: antonio@…| Owner: mutt-dev Type: enhancement | Status: closed Priority: minor| Milestone: Component: crypto |Version: Resolution: duplicate| Keywords: --+-- Changes (by rinni): * status: new = closed * resolution: = duplicate Comment: This should be addressed in ticket #3167 so I mark this report as duplicate. -- Ticket URL: http://dev.mutt.org/trac/ticket/3247#comment:1 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729310: #3669: save-hook ignores %b expando after change-folder with tab complete
#3669: save-hook ignores %b expando after change-folder with tab complete -+-- Reporter: dirkg | Owner: mutt-dev Type: defect | Status: new Priority: minor | Milestone: Component: mutt|Version: 1.5.22 Resolution: | Keywords: -+-- Comment (by dirkg): Only now I see it is a FAQ already. (Q: Why doesn't $index_format %b show some Maildir? A: Because %b extracts the string after the last slash of the mailbox). And as complete adds a '/' at the end of the path, %b isn't working. While I can deal with the advice not to add '/' at the end of a Maildir as a workaround for manual input, I think tab completion should just work regarding the %b expando. But what's the best approach here? Just remove any trailing / prior from path when b gets evaluated in hdrline.c? Or something more generic like imap_fix_path? The latter could also fix e.g. trailing / appearing in $status_format. -- Ticket URL: http://dev.mutt.org/trac/ticket/3669#comment:1 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729310: #3669: save-hook ignores %b expando after change-folder with tab complete
#3669: save-hook ignores %b expando after change-folder with tab complete
+--
Reporter: dirkg | Owner: mutt-dev
Type: defect | Status: new
Priority: minor | Milestone:
Component: mutt|Version: 1.5.22
Keywords: |
+--
Forwarding from http://bugs.debian.org/729310
{{{
the %b expando isn't evaluated as part of a save-hook mailbox if the
current mailbox was reached by change-folder and the name of the
folder was tab completed. If the name of the folder was not tab
completed but written out, the expando will work as advertised.
e.g. try to save message from folder =foobar to =bar/foobar
a) save-hook . '=bar/%b'
b) change folder to =footab complete - =foobar
c) s for save-message will default to =bar/
c) change folder to =foobar without tab completion
d) s for save-message will default to =bar/foobar
}}}
--
Ticket URL: http://dev.mutt.org/trac/ticket/3669
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602145: #3487: Display problems for mbox-files 2GiB
#3487: Display problems for mbox-files 2GiB
+
Reporter: antonio@… | Owner: me
Type: defect | Status: closed
Priority: trivial| Milestone:
Component: mutt |Version: 1.5.21
Resolution: fixed | Keywords: patch
+
Changes (by Michael Elkins me@…):
* status: assigned = closed
* resolution: = fixed
Comment:
In [99d913f46eb9d694b6d361cf4d0061d66f2a21b4]:
{{{
#!CommitTicketReference repository=
revision=99d913f46eb9d694b6d361cf4d0061d66f2a21b4
use LOFF_T as the type for variables used in fseeko()
closes #3487
}}}
--
Ticket URL: http://dev.mutt.org/trac/ticket/3487#comment:7
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#291798: #3245: mutt: aliases for mailboxes
#3245: mutt: aliases for mailboxes --+-- Reporter: antonio@…| Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt |Version: Resolution: | Keywords: patch --+-- Comment (by vext01): I would also welcome mailbox aliases. -- Ticket URL: http://dev.mutt.org/trac/ticket/3245#comment:4 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602145: #3487: Display problems for mbox-files 2GiB
#3487: Display problems for mbox-files 2GiB
+--
Reporter: antonio@… | Owner: me
Type: defect | Status: assigned
Priority: trivial| Milestone:
Component: mutt |Version: 1.5.21
Resolution: | Keywords: patch
+--
Changes (by me):
* owner: mutt-dev = me
* status: new = assigned
Old description:
Forwarding from http://bugs.debian.org/602145
{{{
I archive some old Mail in mbox files. Recently one of those has become
larger than 2GiB. Mutt still appears to be able to read the headers
correctly, but instead of the body it displays some random chunk of the
mbox file for mails starting after the 2GiB boundary in the mbox. The
exact conditions appears to be that the body must start before 2GiB for
everything to work fine, even if the body then crosses the 2GiB barrier.
Here is a collection of what works and what doesn't for mails after the
2GiB barrier:
Works:
- Headers are displayed correctly.
- Piping the entire mail to some shell-command.
- Viewing the structure of a MIME-message in the attachmend browser.
- From the attachment browser: Viewing (and piping) some parts of
MIME-messages, such as a GPG signature.
Doesn't work:
- Displaying the body.
- Verifying GPG-Encrypted messages.
- From the attachment browser: Viewing (and piping) some parts of
MIME-messages, such as GPG-signed text.
- From the attachment browser: Viewing (and piping) some parts of
messages such as the body-text of non-multipart mails. I even get a
different part of the mbox file for the first 5 to 10 tries, until it
settles to only show me empty text.
The attached perl script will generate a mbox file slightly larger than
2GiB on stdout to illustrate the problem. Note that it had to be a
script because I had to give each mail in the mbox a unique Message-ID,
otherwise mutt assumes they are all in one thread and takes ages to sort
the mails for display. In an mbox generated by the unmodified skript the
last two mails show the broken behaviour.
I suggest to either fix the broken behaviour. If that proves to be too
difficult, I suggest to refuse opening mbox files larger than 2GiB (at
least on 32 bit architectures). This smells like some integer overflow
and those tend to have security implications.
}}}
New description:
Forwarding from http://bugs.debian.org/602145
{{{
I archive some old Mail in mbox files. Recently one of those has become
larger than 2GiB. Mutt still appears to be able to read the headers
correctly, but instead of the body it displays some random chunk of the
mbox file for mails starting after the 2GiB boundary in the mbox. The
exact conditions appears to be that the body must start before 2GiB for
everything to work fine, even if the body then crosses the 2GiB barrier.
Here is a collection of what works and what doesn't for mails after the
2GiB barrier:
Works:
- Headers are displayed correctly.
- Piping the entire mail to some shell-command.
- Viewing the structure of a MIME-message in the attachmend browser.
- From the attachment browser: Viewing (and piping) some parts of
MIME-messages, such as a GPG signature.
Doesn't work:
- Displaying the body.
- Verifying GPG-Encrypted messages.
- From the attachment browser: Viewing (and piping) some parts of
MIME-messages, such as GPG-signed text.
- From the attachment browser: Viewing (and piping) some parts of
messages such as the body-text of non-multipart mails. I even get a
different part of the mbox file for the first 5 to 10 tries, until it
settles to only show me empty text.
The attached perl script will generate a mbox file slightly larger than
2GiB on stdout to illustrate the problem. Note that it had to be a script
because I had to give each mail in the mbox a unique Message-ID, otherwise
mutt assumes they are all in one thread and takes ages to sort the mails
for display. In an mbox generated by the unmodified skript the last two
mails show the broken behaviour.
I suggest to either fix the broken behaviour. If that proves to be too
difficult, I suggest to refuse opening mbox files larger than 2GiB (at
least on 32 bit architectures). This smells like some integer overflow
and those tend to have security implications.
}}}
--
Comment:
There is a macro LOFF_T for this purpose. Older systems may not have
off_t, so we use LOFF_T and the configure script substitutes the best
possible type available on the system. See the attached patch.
--
Ticket URL: http://dev.mutt.org/trac/ticket/3487#comment:6
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602145: #3487: Display problems for mbox-files 2GiB
#3487: Display problems for mbox-files 2GiB +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: new Priority: trivial| Milestone: Component: mutt |Version: 1.5.21 Resolution: | Keywords: patch +-- Comment (by ansgar): Any chance to get this tiny patch reviewed and applied? Ansgar -- Ticket URL: http://dev.mutt.org/trac/ticket/3487#comment:5 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602145: #3487: Display problems for mbox-files 2GiB
#3487: Display problems for mbox-files 2GiB +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: new Priority: trivial| Milestone: Component: mutt |Version: 1.5.21 Resolution: | Keywords: patch +-- Comment (by ansgar): Is there still something to do to get this patch applied? There hasn't been any feedback. The patch is tiny (just changes one type) and should be easy to review ;) While the patch is against 1.5.21 the problematic code is still present in the current Hg HEAD in the mutt_body_handler function (though the line numbers have changed a bit). Ansgar -- Ticket URL: http://dev.mutt.org/trac/ticket/3487#comment:4 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592874: #3489: user-defined settings are overriden by /etc/Muttrc
#3489: user-defined settings are overriden by /etc/Muttrc -+-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: closed Priority: trivial | Milestone: Component: mutt|Version: 1.5.21 Resolution: worksforme | Keywords: -+-- Changes (by kevin8t8): * status: new = closed * resolution: = worksforme Comment: Closing this ticket out. Looks like the same conclusion was already discussed in the Debian bug too. -- Ticket URL: http://dev.mutt.org/trac/ticket/3489#comment:2 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592874: #3489: user-defined settings are overriden by /etc/Muttrc
#3489: user-defined settings are overriden by /etc/Muttrc
+--
Reporter: antonio@… | Owner: mutt-dev
Type: defect | Status: new
Priority: trivial| Milestone:
Component: mutt |Version: 1.5.21
Resolution: | Keywords:
+--
Comment (by kevin8t8):
(Sorry I know this bug is two years old. I don't have a frame of
reference for any discussion that may have taken place before opening this
bug. Please enlighten me if my response is not helpful.)
Each invocation of ''hdr_order'' appends more headers to mutt's header
order list. If a header is already in the list, then it is ignored in
subsequent ''hdr_order'' commands.
The recommended solution is to put ''unhdr_order *'' before your
''hdr_order'' command. This will empty the list so you can start fresh in
your .muttrc:
{{{
unhdr_order *
hdr_order from date to cc subject
}}}
Alternatively, if you don't mind your specified headers coming after other
system muttrc defined ones, you can use
{{{
unhdr_order from date to cc subject
hdr_order from date to cc subject
}}}
which will remove and then append those headers to the end of the order
list (at least preserving the order of them.)
--
Ticket URL: http://dev.mutt.org/trac/ticket/3489#comment:1
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602145: #3487: Display problems for mbox-files 2GiB
#3487: Display problems for mbox-files 2GiB +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: new Priority: trivial| Milestone: Component: mutt |Version: 1.5.21 Resolution: | Keywords: +-- Changes (by ansgar): * cc: ansgar@… (added) Comment: Jö and I wrote the attached patch after playing a bit with gdb. The tmpoffset variable is used to temporarily store a off_t value: tmpoffset = b-offset; ... b-offset = tmpoffset; This doesn't work if sizeof(off_t) != sizeof(long) as on i386 with 64-bit off_t. Ansgar -- Ticket URL: http://dev.mutt.org/trac/ticket/3487#comment:2 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602145: #3487: Display problems for mbox-files 2GiB
#3487: Display problems for mbox-files 2GiB +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: new Priority: trivial| Milestone: Component: mutt |Version: 1.5.21 Resolution: | Keywords: patch +-- Changes (by Joe): * keywords: = patch -- Ticket URL: http://dev.mutt.org/trac/ticket/3487#comment:3 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#172960: #1208: pgp_getkeys_command uses email address in %r
#1208: pgp_getkeys_command uses email address in %r --+- Reporter: Conrad Heiney conrad@… | Owner: me Type: defect | Status: closed Priority: minor| Milestone: Component: crypto | Version: 1.5.19 Resolution: fixed|Keywords: --+- Changes (by Michael Elkins me@…): * status: accepted = closed * resolution: = fixed Comment: (In [5e745e37fe6e]) update documentation for $pgp_getkeys_command to note that %r is replaced with the email address, not the public key ID closes #1208 -- Ticket URL: http://dev.mutt.org/trac/ticket/1208#comment:10 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#172960: #1208: pgp_getkeys_command uses email address in %r
#1208: pgp_getkeys_command uses email address in %r
-+--
Reporter: Conrad Heiney conrad@… | Owner: me
Type: defect | Status: accepted
Priority: minor| Milestone:
Component: crypto | Version: 1.5.19
Keywords: |
-+--
Changes (by me):
* owner: mutt-dev = me
* status: new = accepted
Old description:
{{{
Package: mutt
Version: 1.3.99i
Severity: normal
-- Please type your report below this line
When attempting to use pgp_getkeys_command in my muttrc, gpg routinely
fails to retrieve keys from keyserver with the error that $email_address
is not a valid key ID. Upon reading the muttrc man page, it appears that
%r should be the key ID, but for some reason mutt is passing the email
address rather than a key to the gpg --recv-keys command.
It appears based on the documentation that mutt should be passing the
actual Key ID in %r rather than the email address so that this will work
as described. Please forgive me if I am insane or wrong.
-- Build environment information
(Note: This is the build environment installed on the system
muttbug is run on. Information may or may not match the environment
used to build mutt.)
- gcc version information
gcc
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
gcc version 2.95.4 20011002 (Debian prerelease)
- CFLAGS
-Wall -pedantic -O2 -pipe
-- Mutt Version Information
Mutt 1.3.99i (2002-05-02)
Copyright (C) 1996-2001 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.
System: Linux 2.4.19-pre8-ac5 (i686) [using ncurses 5.2]
Compile options:
-DOMAIN
-DEBUG
+HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE
+USE_FCNTL -USE_FLOCK
-USE_POP -USE_IMAP -USE_GSS -USE_SSL -USE_SASL
+HAVE_REGCOMP -USE_GNU_REGEX
+HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET
+HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM
+HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT
+ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET
+HAVE_LANGINFO_YESEXPR
+HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID -HAVE_GETADDRINFO
ISPELL=/usr/bin/ispell
SENDMAIL=/var/qmail/bin/sendmail
MAILPATH=./Maildir/
PKGDATADIR=/usr/local/share/mutt
SYSCONFDIR=/usr/local/etc
EXECSHELL=/bin/sh
-MIXMASTER
To contact the developers, please mail to mutt-...@mutt.org.
To report a bug, please use the flea(1) utility.
--- Begin /home/conrad/.muttrc
set realname = Conrad Heiney
set from = con...@fringehead.org
set beep = no
set delete = yes
set tmpdir = /tmp
set ispell = /usr/bin/ispell
set spoolfile = $HOME/Maildir/
set sort = from
set visual = vim
set markers = no
set signature = $HOME/.signature|
set fast_reply = yes
set include = yes
set move = no
set mbox = $HOME/Maildir/
set mbox_type = Maildir
set confirmappend = no
set confirmcreate = no
set default_hook = ~f %s !~P | (~P ~C %s)
set fcc_attach = no
set force_name = yes
set save_address = no
set save_name = yes
set envelope_from = yes
set rfc2047_parameters = yes
set mailcap_path = /etc/mailcap
set implicit_autoview = yes
set pgp_decode_command=/usr/local/bin/pgpewrap gpg %?p?--passphrase-fd
0? --no-verbose --batch --output - %f
set pgp_verify_command=/usr/local/bin/pgpewrap gpg --no-verbose --batch
--output - --verify %s %f
set pgp_decrypt_command=/usr/local/bin/pgpewrap gpg --passphrase-fd 0
--no-verbose --batch --output - %f
set pgp_sign_command=/usr/local/bin/pgpewrap gpg --no-verbose --batch
--output - --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a?
%f
set pgp_clearsign_command=/usr/local/bin/pgpewrap gpg --no-verbose
--batch --output - --passphrase-fd 0 --armor --textmode --clearsign
%?a?-u %a? %f
set pgp_encrypt_only_command=/usr/local/bin/pgpewrap gpg --batch --quiet
--no-verbose --output - --encrypt --textmode --armor --always-trust
--encrypt-to 445FFDD4 -- -r %r -- %f
set pgp_encrypt_sign_command=/usr/local/bin/pgpewrap gpg --passphrase-fd
0 --batch --quiet --no-verbose --textmode --output - --encrypt --sign
%?a?-u %a? --armor --always-trust --encrypt-to 445FFDD4 -- -r %r -- %f
set pgp_import_command=/usr/local/bin/pgpewrap gpg --no-verbose --import
-v %f
set pgp_export_command=/usr/local/bin/pgpewrap gpg --no-verbose --export
--armor %r
set pgp_verify_key_command=/usr/local/bin/pgpewrap gpg --no-verbose
--batch --fingerprint --check-sigs %r
set pgp_list_pubring_command=/usr/local/bin/pgpewrap gpg --no-verbose
--batch --with-colons --list-keys %r
set pgp_list_secring_command=/usr/local
Bug#439308: #3259: should be able to delete certain attachments in crypted mail
#3259: should be able to delete certain attachments in crypted mail --+- Reporter: antonio@… | Owner: mutt-dev Type: enhancement | Status: new Priority: minor | Milestone: Component: mutt | Version: Keywords:| --+- Changes (by vinc17): * cc: vincent@… (added) -- Ticket URL: http://dev.mutt.org/trac/ticket/3259#comment:2 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#439308: #3259: should be able to delete certain attachments in crypted mail
#3259: should be able to delete certain attachments in crypted mail --+- Reporter: antonio@… | Owner: mutt-dev Type: enhancement | Status: new Priority: minor | Milestone: Component: mutt | Version: Keywords:| --+- Changes (by hlein): * cc: hlein@… (added) Comment: Bump. Sometimes I'll get emails with large (MBs) of attachments. Once I verify the PGP signature and save the attachments to disk, I don't need them in my inbox any more. However, I do want to keep the record that/when they emailed, and any text they included in the body. I understand that deleting attachments from a signed email would break the signature. Ideally mutt would re-sign the message to myself with my own key. Similarly if the email were encrypted, Mutt can't just slice some bits out of it; it wouldn't decrypt any more. So instead, Mutt would have to call gpg to re-encrypt the content that was preserved. -- Ticket URL: http://dev.mutt.org/trac/ticket/3259#comment:1 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530584: [Mutt] #3236: mutt: should use /var/tmp for mail drafts by default
#3236: mutt: should use /var/tmp for mail drafts by default --+- Reporter: antonio@… | Owner: mutt-dev Type: enhancement | Status: new Priority: minor | Milestone: Component: mutt | Version: Keywords:| --+- Changes (by hhorak): * cc: hhorak@… (added) -- Ticket URL: http://dev.mutt.org/trac/ticket/3236#comment:15 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540540: [Mutt] #3323: Sending postponed messages doesn't save a copy in $record
#3323: Sending postponed messages doesn't save a copy in $record ---+ Reporter: antonio@… | Owner: mutt-dev Type: defect| Status: new Priority: minor | Milestone: Component: mutt | Version: 1.5.20 Resolution:|Keywords: ---+ Changes (by Kip): * cc: kip@… (added) Comment: I completely agree with what others have said. Data loss is data loss. Even if upstream reasons that there are conditions under which $record ought to be ignored on outbound mail, that should be made clear in the documentation since, as others and myself have experienced, we're losing data unexpectedly. -- Ticket URL: http://dev.mutt.org/trac/ticket/3323#comment:6 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530671: [Mutt] #3242: mutt: does not want to open dot subdirs via imap anymore
#3242: mutt: does not want to open dot subdirs via imap anymore --+- Reporter: antonio@… | Owner: lucki2791 Type: task | Status: accepted Priority: major | Milestone: 2.0 Component: browser | Version: 1.5.21 Keywords:| --+- Changes (by lucki2791): * cc: lucki2791@… (added) * component: IMAP = browser * version: 1.5.19 = 1.5.21 * milestone: 1.6 = 2.0 * owner: brendan = lucki2791 * type: defect = task -- Ticket URL: http://dev.mutt.org/trac/ticket/3242#comment:6 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599136: [Mutt] #3491: hangs when IP address changes
#3491: hangs when IP address changes --+- Reporter: antonio@… | Owner: mutt-dev Type: defect| Status: new Priority: trivial | Milestone: Component: mutt | Version: 1.5.21 Keywords:| --+- Comment(by petr_p): I don't think mutt (or any generic application) should watch local IP addresses. This is job for kernel to close stream connections after loosing local address. Though mutt should be able to interrupt network operation on user request. If server becomes unresponsive, or connection is to slow, it's useful to be able to abort e.g. fetching e-mail body. I think simple SIGINT handler could set a flag and EINTRed syscall loop could break on the flag. Also there could be possibility to adjust network time-out (SO_RCVTIMEO, SO_SNDTIMEO) if default system-wide value is not suitable (like connect_timeout exists for establishing a connection). -- Ticket URL: http://dev.mutt.org/trac/ticket/3491#comment:2 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599136: [Mutt] #3491: hangs when IP address changes
#3491: hangs when IP address changes --+- Reporter: antonio@… | Owner: mutt-dev Type: defect| Status: new Priority: trivial | Milestone: Component: mutt | Version: 1.5.21 Keywords:| --+- Comment(by antonio@…): Hi guys, this is still an issue and it is causing problems to everyone who needs to switch their connection without closing and reopening mutt in the process. Any change that you could have a look at this? -- Ticket URL: http://dev.mutt.org/trac/ticket/3491#comment:1 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#603291: [Mutt] #3513: mutt: unable to attach a folder
#3513: mutt: unable to attach a folder --+- Reporter: antonio@… | Owner: mutt-dev Type: enhancement | Status: new Priority: trivial | Milestone: Component: mutt | Version: 1.5.21 Keywords:| --+- Comment(by kolcon): That would be indeed useful! -- Ticket URL: http://dev.mutt.org/trac/ticket/3513#comment:1 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#603291: [Mutt] #3513: mutt: unable to attach a folder
#3513: mutt: unable to attach a folder
--+-
Reporter: antonio@… | Owner: mutt-dev
Type: enhancement | Status: new
Priority: trivial | Milestone:
Component: mutt | Version: 1.5.21
Keywords:|
--+-
Comment(by cameron):
{{{
On 27Apr2011 22:44, Mutt fl...@mutt.org wrote:
| I'd like to attach folders with everything contained. [...]
| I know I could create an archive, eg. using tar or zip, but would
prefer
| to not do this, since the other side then complains about the work to
| unpack those.
I'd do that from within the editor. For example, using vi:
!!find dir/ -type f -print | sed 's/^/Attach: /'
to insert Attach: header lines for all files in dir.
Mutt will attach when you exit the editor.
Currently I have a convenient vi macro bound to ctrl-A to prompt and file
complete a single file path and emit an Attach: line; I could beef it up a
little...
Cheers,
}}}
--
Ticket URL: http://dev.mutt.org/trac/ticket/3513#comment:
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540540: [Mutt] #3323: Sending postponed messages doesn't save a copy in $record
#3323: Sending postponed messages doesn't save a copy in $record ---+ Reporter: antonio@… | Owner: mutt-dev Type: defect| Status: new Priority: minor | Milestone: Component: mutt | Version: 1.5.20 Resolution:|Keywords: ---+ Changes (by russor): * cc: mutt@… (added) Comment: My corporate Exchange 2007 server is silently removing the X-Mutt-Fcc header when mutt stores drafts, so it would be great for me to have a way to force recording, since despite mutt's best efforts, my imap server is conspiring against me. I've verified with -d5 that the message that's appended by mutt has the head, and the message retrieved when the mail is continued does not, thanks Exchange, but I don't control the server. -- Ticket URL: http://dev.mutt.org/trac/ticket/3323#comment:5 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600962: [Mutt] #3490: IMAP: ignores \Recent flag but rolls its own replacement
#3490: IMAP: ignores \Recent flag but rolls its own replacement --+- Reporter: antonio@… | Owner: brendan Type: defect| Status: new Priority: trivial | Milestone: Component: IMAP | Version: 1.5.21 Keywords:| --+- Comment(by brendan): We used \Recent for a long time, but it is unfortunately a very unreliable flag. It can't be changed explicitly, and is easily lost by implicit actions performed by things like biff clients, or closing mailboxes with \Recent messages. After many bug reports that were due to \Recent's poor semantics, we gave up on it. There may be ways to improve old message handling, but simply using \Recent is a step backwards. Possibly it could be a configuration variable for people in environments where \Recent behaves acceptably. I don't think there's any violation of the RFC here. The problem is in part due to the RFC's poor specification of \Recent semantics. By the way, old messages do not overlap with read messages. -- Ticket URL: http://dev.mutt.org/trac/ticket/3490#comment: Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#611412: [Mutt] #3514: bogus regexp for BTS subscription
#3514: bogus regexp for BTS subscription ---+ Reporter: antonio@… | Owner: mutt-dev Type: defect| Status: closed Priority: trivial | Milestone: Component: mutt | Version: 1.5.21 Resolution: fixed |Keywords: patch ---+ Changes (by me): * status: new = closed * resolution: = fixed -- Ticket URL: http://dev.mutt.org/trac/ticket/3514#comment:1 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539232: [Mutt] #3332: Failures to send result in duplicate messages in record folder
#3332: Failures to send result in duplicate messages in record folder --+- Reporter: antonio@… | Owner: mutt-dev Type: defect| Status: new Priority: trivial | Milestone: Component: mutt | Version: 1.5.21 Keywords:| --+- Changes (by ilf): * cc: ilf@… (added) * version: 1.5.20 = 1.5.21 Comment: This is highly annoying. If you want to keep the current way of things and not provide an option, then at least the already recorded message should be deleted again when sending failed. -- Ticket URL: http://dev.mutt.org/trac/ticket/3332#comment:3 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521732: [Mutt] #2056: Attempt re-connect when idle mailbox connection closes
#2056: Attempt re-connect when idle mailbox connection closes +--- Reporter: gale@… | Owner: brendan Type: enhancement | Status: new Priority: major | Milestone: 2.0 Component: IMAP| Version: Keywords: | +--- Changes (by petr): * cc: petr.mvd@… (added) -- Ticket URL: http://dev.mutt.org/trac/ticket/2056#comment:8 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#624058: [Mutt] #3515: Remove deprecated _set_priority GnuTLS functions (patch available)
#3515: Remove deprecated _set_priority GnuTLS functions (patch available)
--+-
Reporter: antonio@… | Owner: mutt-dev
Type: defect| Status: new
Priority: minor | Milestone:
Component: crypto| Version: 1.5.21
Keywords: patch |
--+-
Reporting from http://bugs.debian.org/624058
{{{
This package is using some functions which are marked deprecated in
newer versions of GnuTLS (=2.12.x). (They are not yet removed, though.)
These functions will be removed in future releases. GnuTLS 2.12.x is
already available in experimental.
Excerpt from buildlog:
../mutt_ssl_gnutls.c:313:3: warning: 'gnutls_protocol_set_priority' is
deprecated (declared at /usr/include/gnutls/compat.h:344)
../mutt_ssl_gnutls.c:313:3: warning: 'gnutls_protocol_set_priority' is
deprecated (declared at /usr/include/gnutls/compat.h:344)
The gnutls_*_set_priority family of functions has been marked deprecated
in 2.12.x. These functions have been superceded by
gnutls_priority_set_direct(). The replacement function was added in gnutls
stable release 2.2.0 (released 2007-12-14).
}}}
The attached patch fixes the problem
--
Ticket URL: http://dev.mutt.org/trac/ticket/3515
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#624085: [Mutt] #3516: Remove deprecated gnutls_certificate_verify_peers (patch available)
#3516: Remove deprecated gnutls_certificate_verify_peers (patch available)
--+-
Reporter: antonio@… | Owner: mutt-dev
Type: defect| Status: new
Priority: minor | Milestone:
Component: crypto| Version: 1.5.21
Keywords: patch |
--+-
Reporting from http://bugs.debian.org/624085
{{{
This package is using gnutls_certificate_verify_peers(), a function marked
deprecated in newer stable versions of GnuTLS (=2.12.x) and removed in
the GnuTLS development version 2.99.1. GnuTLS 2.12.x is already available
in experimental.
Excerpt from buildlog:
../mutt_ssl_gnutls.c:944:3: warning: 'gnutls_certificate_verify_peers' is
deprecated (declared at /usr/include/gnutls/compat.h:330)
../mutt_ssl_gnutls.c:944:3: warning: 'gnutls_certificate_verify_peers' is
deprecated (declared at /usr/include/gnutls/compat.h:330)
Please switch from gnutls_certificate_verify_peers to its successor
gnutls_certificate_verify_peers2 (first included in gnutls stable
release 1.2.0).
}}}
The attached patch fixes the problem
--
Ticket URL: http://dev.mutt.org/trac/ticket/3516
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#611412: [Mutt] #3514: bogus regexp for BTS subscription
#3514: bogus regexp for BTS subscription
--+-
Reporter: antonio@… | Owner: mutt-dev
Type: defect| Status: new
Priority: trivial | Milestone:
Component: mutt | Version: 1.5.21
Keywords: patch |
--+-
Forwarding from http://bugs.debian.org/611412
{{{
The manual reports a bad regexp for Debian bugs in BTS:
subscribe [0-9]*.*@bugs.debian.org
But this regex matches, amongst others, sub...@bugs.debian.org and
cont...@bugs.debian.org.
The new proposed regexp is:
subscribe [0-9]+.*@bugs.debian.org
The attached patch fixes the problem
}}}
--
Ticket URL: http://dev.mutt.org/trac/ticket/3514
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540540: [Mutt] #3323: Sending postponed messages doesn't save a copy in $record
#3323: Sending postponed messages doesn't save a copy in $record ---+ Reporter: antonio@… | Owner: mutt-dev Type: defect| Status: new Priority: minor | Milestone: Component: mutt | Version: 1.5.20 Resolution:|Keywords: ---+ Changes (by josh): * status: closed = new * resolution: invalid = Comment: Any further thoughts on this bug? (Reopening based on the previous comment; hope that's OK.) One followup to my previous comment: it also seems natural that when using IMAP, one mail client can write a draft to the Drafts folder and another mail client can continue that mail. The behavior described here would mean that mutt would not put the mail in the Sent folder unless mutt started the mail. That seems like a rather huge and unexpected exception to the normal expectations of keeping mail in IMAP. -- Ticket URL: http://dev.mutt.org/trac/ticket/3323#comment:4 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#603291: [Mutt] #3513: mutt: unable to attach a folder
#3513: mutt: unable to attach a folder
--+-
Reporter: antonio@… | Owner: mutt-dev
Type: enhancement | Status: new
Priority: trivial | Milestone:
Component: mutt | Version: 1.5.21
Keywords:|
--+-
Forwarding from http://bugs.debian.org/603291
{{{
I'd like to attach folders with everything contained. This would spare me
the tedious process of attaching one file after the other while
navigating the tree, and also spare the problem of possible name
collision.
I know I could create an archive, eg. using tar or zip, but would prefer
to not do this, since the other side then complains about the work to
unpack those.
}}}
--
Ticket URL: http://dev.mutt.org/trac/ticket/3513
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#206364: [Mutt] #1611: mutt erroneously omits information in parenthesis after addresses in Cc headers
#1611: mutt erroneously omits information in parenthesis after addresses in Cc headers -+-- Reporter: Marco d'Itri md@… | Owner: mutt-dev Type: defect | Status: closed Priority: minor | Milestone: Component: mutt| Version: 1.5.20 Resolution: invalid |Keywords: -+-- Comment(by KiBi): Hi, I'm wondering whether you would welcome a patch which would make it a runtime configuration option? This way, users could turn it on at their discretion (instead of having to keep a locally-built mutt). !KiBi. -- Ticket URL: http://dev.mutt.org/trac/ticket/1611#comment:11 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572702: [Mutt] #3495: q and x in help menu should only appear once
#3495: q and x in help menu should only appear once
--+-
Reporter: anto...@… | Owner: mutt-dev
Type: defect| Status: new
Priority: trivial | Milestone:
Component: mutt | Version: 1.5.21
Keywords:|
--+-
Forwarding from http://bugs.debian.org/572702
{{{
In the ? help screen, one sees
q quit save changes to mailbox and quit
x exit exit this menu
q exit exit this menu
Well, the x should be changed to match
/usr/share/doc/mutt/manual.txt.gz:
xabort changes and exit
And I would perhaps just use a special line somewhere:
to exit this menu, press q or x.
Else the user might notice one q but not the other...
}}}
--
Ticket URL: http://dev.mutt.org/trac/ticket/3495
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572702: [Mutt] #3495: q and x in help menu should only appear once
#3495: q and x in help menu should only appear once --+- Reporter: anto...@… | Owner: mutt-dev Type: defect| Status: new Priority: trivial | Milestone: Component: mutt | Version: 1.5.21 Keywords:| --+- Comment(by vinc17): I don't think this is a bug. The second one is under the generic bindings. -- Ticket URL: http://dev.mutt.org/trac/ticket/3495#comment:1 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568832: [Mutt] #3486: Attach: pseudo-header cannot handle filenames with newline
#3486: Attach: pseudo-header cannot handle filenames with newline
--+-
Reporter: anto...@… | Owner: mutt-dev
Type: defect| Status: new
Priority: trivial | Milestone:
Component: mutt | Version: 1.5.21
Keywords:|
--+-
Forwarding from http://bugs.debian.org/568832
{{{
The Attach: pseudo-header can now attach filenames with spaces in
them, through \-escaping. That's good, and works for spaces and tabs
(^I, \t). But it does not work for newlines (^J, \n).
}}}
I'm filling it as a defect because maybe it should also handle newlines as
well, if you feel that this is an enhancement please feel free to
reclassify!
Cheers
Antonio
--
Ticket URL: http://dev.mutt.org/trac/ticket/3486
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602145: [Mutt] #3487: Display problems for mbox-files 2GiB
#3487: Display problems for mbox-files 2GiB
--+-
Reporter: anto...@… | Owner: mutt-dev
Type: defect| Status: new
Priority: trivial | Milestone:
Component: mutt | Version: 1.5.21
Keywords:|
--+-
Forwarding from http://bugs.debian.org/602145
{{{
I archive some old Mail in mbox files. Recently one of those has become
larger than 2GiB. Mutt still appears to be able to read the headers
correctly, but instead of the body it displays some random chunk of the
mbox file for mails starting after the 2GiB boundary in the mbox. The
exact conditions appears to be that the body must start before 2GiB for
everything to work fine, even if the body then crosses the 2GiB barrier.
Here is a collection of what works and what doesn't for mails after the
2GiB barrier:
Works:
- Headers are displayed correctly.
- Piping the entire mail to some shell-command.
- Viewing the structure of a MIME-message in the attachmend browser.
- From the attachment browser: Viewing (and piping) some parts of
MIME-messages, such as a GPG signature.
Doesn't work:
- Displaying the body.
- Verifying GPG-Encrypted messages.
- From the attachment browser: Viewing (and piping) some parts of
MIME-messages, such as GPG-signed text.
- From the attachment browser: Viewing (and piping) some parts of
messages such as the body-text of non-multipart mails. I even get a
different part of the mbox file for the first 5 to 10 tries, until it
settles to only show me empty text.
The attached perl script will generate a mbox file slightly larger than
2GiB on stdout to illustrate the problem. Note that it had to be a script
because I had to give each mail in the mbox a unique Message-ID, otherwise
mutt assumes they are all in one thread and takes ages to sort the mails
for display. In an mbox generated by the unmodified skript the last two
mails show the broken behaviour.
I suggest to either fix the broken behaviour. If that proves to be too
difficult, I suggest to refuse opening mbox files larger than 2GiB (at
least on 32 bit architectures). This smells like some integer overflow
and those tend to have security implications.
}}}
--
Ticket URL: http://dev.mutt.org/trac/ticket/3487
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606742: [Mutt] #3488: mail-key function is broken when crypt_use_gpgme is set
#3488: mail-key function is broken when crypt_use_gpgme is set
--+-
Reporter: anto...@… | Owner: mutt-dev
Type: defect| Status: new
Priority: trivial | Milestone:
Component: mutt | Version: 1.5.21
Keywords:|
--+-
Forwarding from http://bugs.debian.org/606742
{{{
Hello,
Mailing a PGP public key with Esc-k is broken when using the gpgme
crypto backend.
Steps to reproduce:
1)
% echo set crypt_use_gpgme=yes /tmp/broken
% mutt -F /tmp/broken
alternatively, launch mutt with a gpg-agent if you don't have one
already running:
% gpg-agent --daemon mutt -F /tmp/broken
2) Type Esc-k to mail a public key. You are asked for recipient
and subject, but not for a keyid. Nothing more happens.
Laurent.
}}}
--
Ticket URL: http://dev.mutt.org/trac/ticket/3488
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592874: [Mutt] #3489: user-defined settings are overriden by /etc/Muttrc
#3489: user-defined settings are overriden by /etc/Muttrc
--+-
Reporter: anto...@… | Owner: mutt-dev
Type: defect| Status: new
Priority: trivial | Milestone:
Component: mutt | Version: 1.5.21
Keywords:|
--+-
Forwarding from http://bugs.debian.org/592874
{{{
Since I upgraded from lenny to squeeze I found that my 'hdr_order'
configuration has stopped working.
How to reproduce it:
$ mutt -F /dev/null -e hdr_order from date to cc subject -f /tmp/msg
With this, the 'Date' header should appear between 'From' and 'To'.
However, it appears in the first position. The reason for this is that
it's being overriden by /etc/Muttrc.
Removing the 'hdr_order' line from /etc/Muttrc makes it work as
expected, but users shouldn't need to do that.
strace suggests that the config files are being read in the correct
order (/etc first, $HOME last). This has also been reported in the
mutt-users mailing list, but apparently with no solution so far:
http://www.mail-archive.com/mutt-users@mutt.org/msg39558.html
}}}
--
Ticket URL: http://dev.mutt.org/trac/ticket/3489
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600962: [Mutt] #3490: IMAP: ignores \Recent flag but rolls its own replacement
#3490: IMAP: ignores \Recent flag but rolls its own replacement
--+-
Reporter: anto...@… | Owner: brendan
Type: defect| Status: new
Priority: trivial | Milestone:
Component: IMAP | Version: 1.5.21
Keywords:|
--+-
Forwarding from http://bugs.mutt.org/600962
{{{
When accessing IMAP folders, mutt ignores the \Recent message flag, but
uses a custom keyword Old instead.
Email messages on IMAP servers are old when the corresponding mailbox
has been opened by a MUA previously, that is (in theory) iff they have
the \Recent flag not set.
Mutt however considers a message old only iff it is read (have the
\Seen flag set), or have the mutt-specific keyword Old set.
This violates RFC 3501, and breaks inter-operability with other MUAs.
For example, say I open a mailbox with a MUA other than mutt, and find 3
messages new in the mailbox but don't read them. When I later open the
mailbox again with mutt, the 3 messages are labelled new in mutt,
which is wrong.
And it is particularly annoying if the IMAP server doesn't allow
creating custom keywords (it is an optional IMAP feature, after all); in
this case, the set of old messages in mutt always equals the set of
read messages.
}}}
--
Ticket URL: http://dev.mutt.org/trac/ticket/3490
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599136: [Mutt] #3491: hangs when IP address changes
#3491: hangs when IP address changes
--+-
Reporter: anto...@… | Owner: mutt-dev
Type: defect| Status: new
Priority: trivial | Milestone:
Component: mutt | Version: 1.5.21
Keywords:|
--+-
Forwarding from http://bugs.mutt.org/599136
{{{
I use mutt with an IMAP server (imap.crustytoothpaste.net, running
Dovecot). My IMAP connection is always encrypted. I'm running mutt on
my laptop, so often I forget to quit mutt before I put the lid down.
When I resume my laptop, I am often at another location with a different
IP address. When I hit . to refresh the buffer list or pretty much
anything else, mutt becomes unresponsive and I cannot do anything, even
quit, for some amount of time (probably until the network times out).
Even Ctrl-C doesn't work. I'm forced to wait or use Ctrl-\.
I'd really appreciate it if mutt could be more responsive in this case.
I would prefer if it would detect that the network address had changed
or even that the connection it once had does not exist anymore. I would
even be satisfied if I could just quit and restart mutt (even if I had
to interrupt it with Ctrl-C to make it responsive again).
}}}
--
Ticket URL: http://dev.mutt.org/trac/ticket/3491
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589430: [Mutt] #3492: mutt uses ncurses even in non-interactive mode
#3492: mutt uses ncurses even in non-interactive mode
--+-
Reporter: anto...@… | Owner: mutt-dev
Type: defect| Status: new
Priority: trivial | Milestone:
Component: mutt | Version: 1.5.21
Keywords:|
--+-
Forwarding from http://bugs.debian.org/589430
{{{
Hello,
mutt uses ncurses even if there is no such need, i.e.:
- with '-p' option,
- with '-Z' option if there is no new mail,
- in compose mode when editor is started right away.
After mutt exits user is left with cleaned screen and default color
palette on some terminals[1], which is pretty annoying.
[1] http://bugs.debian.org/589429
}}}
--
Ticket URL: http://dev.mutt.org/trac/ticket/3492
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602145: [Mutt] #3487: Display problems for mbox-files 2GiB
#3487: Display problems for mbox-files 2GiB --+- Reporter: anto...@… | Owner: mutt-dev Type: defect| Status: new Priority: trivial | Milestone: Component: mutt | Version: 1.5.21 Keywords:| --+- Changes (by Joe): * cc: jor...@… (added) -- Ticket URL: http://dev.mutt.org/trac/ticket/3487#comment:1 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#578087: [Mutt] #3483: segfault on a weird maildir
#3483: segfault on a weird maildir --+- Reporter: anto...@… | Owner: mutt-dev Type: defect| Status: new Priority: minor | Milestone: Component: mutt | Version: 1.5.20 Keywords:| --+- Hi, mutt segfaults on a weird maildir (attached), the attached patch should fix the problem, it seems that the return value of strchr is not checked in an else block (it is checked on the previous if block though). I've put 1.5.20 on the Version field but this is reproducible on 1.5.21 as well -- Ticket URL: http://dev.mutt.org/trac/ticket/3483 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#578087: [Mutt] #3483: segfault on a weird maildir
#3483: segfault on a weird maildir --+- Reporter: anto...@… | Owner: mutt-dev Type: defect| Status: new Priority: minor | Milestone: Component: mutt | Version: 1.5.21 Keywords:| --+- Changes (by brendan): * version: 1.5.20 = 1.5.21 -- Ticket URL: http://dev.mutt.org/trac/ticket/3483#comment:1 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#578087: [Mutt] #3483: segfault on a weird maildir
#3483: segfault on a weird maildir ---+ Reporter: anto...@… | Owner: brendan Type: defect| Status: closed Priority: minor | Milestone: Component: mutt | Version: 1.5.21 Resolution: fixed |Keywords: ---+ Changes (by Brendan Cully bren...@…): * status: accepted = closed * resolution: = fixed Comment: (In [f01b306ebe0e]) Handle missing : in write_one_header debug statement. Closes #3483 -- Ticket URL: http://dev.mutt.org/trac/ticket/3483#comment:3 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#578087: [Mutt] #3483: segfault on a weird maildir
#3483: segfault on a weird maildir --+- Reporter: anto...@… | Owner: brendan Type: defect| Status: accepted Priority: minor | Milestone: Component: mutt | Version: 1.5.21 Keywords:| --+- Changes (by brendan): * owner: mutt-dev = brendan * status: new = accepted Comment: Thanks, I'm applying an equivalent but shorter fix. -- Ticket URL: http://dev.mutt.org/trac/ticket/3483#comment: Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#311493: [Mutt] #2073: mutt should have a CA certs directory option
#2073: mutt should have a CA certs directory option --+- Reporter: d...@…| Owner: mutt-dev Type: enhancement | Status: new Priority: minor | Milestone: Component: mutt | Version: Keywords:| --+- Changes (by rsc): * cc: mutt@… (added) -- Ticket URL: http://dev.mutt.org/trac/ticket/2073#comment:1 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#177504: [Mutt] #1441: can't view-attachments of a message/rfc822 attachment view-attached in compose
#1441: can't view-attachments of a message/rfc822 attachment view-attached in compose +--- Reporter: Marco d'Itri m...@… | Owner: me Type: enhancement | Status: accepted Priority: minor | Milestone: Component: display | Version: Keywords: #2085 | +--- Changes (by barsnick): * cc: barsn...@… (added) -- Ticket URL: http://dev.mutt.org/trac/ticket/1441#comment:4 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#565236: [Mutt] #3427: mutt-1.5.20: reply-hook . set realname=foo is executed too late
#3427: mutt-1.5.20: reply-hook . set realname=foo is executed too late
+---
Reporter: fr...@…| Owner: mutt-dev
Type: defect | Status: infoneeded_new
Priority: major | Milestone:
Component: mutt | Version:
Resolution: fixed |Keywords:
+---
Comment(by Francois Lallart):
{{{
patch works for me. thank you.
}}}
--
Ticket URL: http://dev.mutt.org/trac/ticket/3427#comment:
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#565236: [Mutt] #3427: mutt-1.5.20: reply-hook . set realname=foo is executed too late
#3427: mutt-1.5.20: reply-hook . set realname=foo is executed too late +--- Reporter: fr...@…| Owner: mutt-dev Type: defect | Status: closed Priority: major | Milestone: Component: mutt | Version: Resolution: fixed |Keywords: +--- Changes (by Michael Elkins m...@…): * status: infoneeded_new = closed Comment: (In [8051fc8b631c]) clear the real name when $reverse_realname is unset and a match is hit so that $realname can be set in a reply- or send-hook closes #3427 -- Ticket URL: http://dev.mutt.org/trac/ticket/3427#comment:4 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#177504: [Mutt] #1441: can't view-attachments of a message/rfc822 attachment view-attached in compose
#1441: can't view-attachments of a message/rfc822 attachment view-attached in compose +--- Reporter: Marco d'Itri m...@… | Owner: me Type: enhancement | Status: accepted Priority: minor | Milestone: Component: display | Version: Keywords: #2085 | +--- Changes (by me): * owner: mutt-dev = me * status: new = accepted * type: defect = enhancement -- Ticket URL: http://dev.mutt.org/trac/ticket/1441#comment:3 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#206364: [Mutt] #1611: mutt erroneously omits information in parenthesis after addresses in Cc headers
#1611: mutt erroneously omits information in parenthesis after addresses in Cc
headers
-+--
Reporter: Marco d'Itri m...@… | Owner: mutt-dev
Type: defect | Status: closed
Priority: minor | Milestone:
Component: mutt| Version: 1.5.20
Resolution: invalid |Keywords:
-+--
Changes (by me):
* status: new = closed
* resolution: = invalid
Old description:
{{{
Package: mutt
Version: 1.5.4-1
Severity: normal
[NOTE: this bug report has been submitted to the debian BTS as
Bug#206364.
Please Cc all your replies to 206...@bugs.debian.org .]
From: Josip Rodin j...@srce.hr
Subject: mutt erroneously omits information in parenthesis after
addresses in Cc headers
Date: Wed, 20 Aug 2003 13:06:30 +0200
Hi,
This set of headers:
From: ow...@bugs.debian.org (Debian Bug Tracking System)
To: Marc Haber mh+debian-b...@zugschlus.de
Cc: Bdale Garbee bd...@gag.com (sudo #89743),
Anthony Towns a...@debian.org (ifupdown #88945 #88946 #88947
#88948,...),
Robert Luberda rob...@debian.org (solid-pop3d #77710 #77711),
Torsten Landschoff tors...@debian.org (tcpdump #75788),
Daniel Jacobowitz d...@debian.org (bitchx #58192),
Luigi Gangitano lu...@debian.org (squid #103130 #81667),
Antonin Kral a.k...@sh.cvut.cz (fmirror #70989 #75965 #78359),
LaMont Jones lam...@debian.org (util-linux #63073),
Mark Baker mba...@iee.org (exim #59545 #95325),
APT Development Team de...@lists.debian.org (apt #57795 #59723),
Robert Woodcock r...@debian.org (mtr #58610),
Josip Rodin joy-packa...@debian.org (gman #82376, lintian #111948),
Jason Thomas ja...@debian.org (grub #93537),
Sean 'Shaleh' Perry sha...@debian.org (anacron #63543),
Matthew Vernon matt...@debian.org (ssh #84008 #84010),
Steve Kemp s...@debian.org (checksecurity #59809)
Gets displayed in my mutt like this:
From: Debian Bug Tracking System ow...@bugs.debian.org
To: Marc Haber mh+debian-b...@zugschlus.de
Cc: Bdale Garbee bd...@gag.com, Anthony Towns a...@debian.org,
Robert Luberda rob...@debian.org,
Torsten Landschoff tors...@debian.org,
Daniel Jacobowitz d...@debian.org,
Luigi Gangitano lu...@debian.org,
Antonin Kral a.k...@sh.cvut.cz, LaMont Jones
lam...@debian.org,
Mark Baker mba...@iee.org,
APT Development Team de...@lists.debian.org,
Robert Woodcock r...@debian.org,
Josip Rodin joy-packa...@debian.org,
Jason Thomas ja...@debian.org,
Sean 'Shaleh' Perry sha...@debian.org,
Matthew Vernon matt...@debian.org, Steve Kemp s...@debian.org
Valuable information in parenthesis is lost. Please don't do that. TIA.
--
2. That which causes joy or happiness.
How-To-Repeat:
Fix:
}}}
New description:
{{{
Package: mutt
Version: 1.5.4-1
Severity: normal
[NOTE: this bug report has been submitted to the debian BTS as Bug#206364.
Please Cc all your replies to 206...@bugs.debian.org .]
From: Josip Rodin j...@srce.hr
Subject: mutt erroneously omits information in parenthesis after addresses
in Cc headers
Date: Wed, 20 Aug 2003 13:06:30 +0200
Hi,
This set of headers:
From: ow...@bugs.debian.org (Debian Bug Tracking System)
To: Marc Haber mh+debian-b...@zugschlus.de
Cc: Bdale Garbee bd...@gag.com (sudo #89743),
Anthony Towns a...@debian.org (ifupdown #88945 #88946 #88947
#88948,...),
Robert Luberda rob...@debian.org (solid-pop3d #77710 #77711),
Torsten Landschoff tors...@debian.org (tcpdump #75788),
Daniel Jacobowitz d...@debian.org (bitchx #58192),
Luigi Gangitano lu...@debian.org (squid #103130 #81667),
Antonin Kral a.k...@sh.cvut.cz (fmirror #70989 #75965 #78359),
LaMont Jones lam...@debian.org (util-linux #63073),
Mark Baker mba...@iee.org (exim #59545 #95325),
APT Development Team de...@lists.debian.org (apt #57795 #59723),
Robert Woodcock r...@debian.org (mtr #58610),
Josip Rodin joy-packa...@debian.org (gman #82376, lintian #111948),
Jason Thomas ja...@debian.org (grub #93537),
Sean 'Shaleh' Perry sha...@debian.org (anacron #63543),
Matthew Vernon matt...@debian.org (ssh #84008 #84010),
Steve Kemp s...@debian.org (checksecurity #59809)
Gets displayed in my mutt like this:
From: Debian Bug Tracking System ow...@bugs.debian.org
To: Marc Haber mh+debian-b...@zugschlus.de
Cc: Bdale Garbee bd...@gag.com, Anthony Towns a...@debian.org,
Robert Luberda rob...@debian.org,
Torsten Landschoff tors...@debian.org,
Daniel Jacobowitz d...@debian.org,
Luigi Gangitano lu...@debian.org,
Antonin Kral a.k...@sh.cvut.cz, LaMont Jones
lam...@debian.org
Bug#521732: [Mutt] #2056: Attempt re-connect when idle mailbox connection closes
#2056: Attempt re-connect when idle mailbox connection closes +--- Reporter: g...@… | Owner: brendan Type: enhancement | Status: new Priority: major | Milestone: 2.0 Component: IMAP| Version: Keywords: | +--- Comment(by me): Ran into this problem recently. My workaround was to set $imap_keepalive to some lower bound that keeps the connection open. -- Ticket URL: http://dev.mutt.org/trac/ticket/2056#comment:7 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#206364: [Mutt] #1611: mutt erroneously omits information in parenthesis after addresses in Cc headers
#1611: mutt erroneously omits information in parenthesis after addresses in Cc
headers
-+--
Reporter: Marco d'Itri m...@… | Owner: mutt-dev
Type: defect | Status: closed
Priority: minor | Milestone:
Component: mutt| Version: 1.5.20
Resolution: invalid |Keywords:
-+--
Comment(by Gregor Zattler):
{{{
Hi mutt developers and package maintainer,,
* Mutt fl...@mutt.org [05. Aug. 2010]:
[... for actual bug report see thread ..]
Then this option should be enabled by default, at least for Debian?
Ciao, Gregor
}}}
--
Ticket URL: http://dev.mutt.org/trac/ticket/1611#comment:
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#344766: [Mutt] #2171: previous-thread doesn't jumps to first message if parent not available
#2171: previous-thread doesn't jumps to first message if parent not available
+---
Reporter: mike.dornber...@… | Owner: mutt-dev
Type: defect | Status: new
Priority: trivial | Milestone:
Component: mutt| Version: 1.5.19
Keywords: |
+---
Old description:
{{{
This is from Debian Bug#344766; in a nutshell, if a thread is missing the
root message, doing next-thread from the previous thread goes to the
first message, but doing previous-thread from the next one does not. Here
is the original report:
---
Hi,
when in threaded mode, mutt doesn't jump to the first available message
when
executing previous-thread (default binding: ^P) when the parent of two
replies is not available, which is at least unexpected. In my case it
goes
to the second subthread. I wanted to read all what I have of this thread
and
expected ^P to jump to the first message, so I can read all the messages
by
pressing right.
You can test this with the file prev_thread-test.mbox that is compressed
in
the attached file mutt_test_prev_thread.tar.bz2 [1]. Maybe an automated
test can
be done with the muttrc I wrote. After executing
$ mutt -f prev_thread-test.1.mbox -F muttrc
the created file content should be the same as content.expected.
Actually it gives the same as in content.not_expected.
Greeting,
Mike Dornberger
---
[1]
http://people.debian.org/~adeodato/tmp/2006-01-29/mutt_test_prev_thread.tar.bz2
How-To-Repeat:
Fix:
Unknown
}}}
New description:
{{{
This is from Debian Bug#344766; in a nutshell, if a thread is missing the
root message, doing next-thread from the previous thread goes to the first
message, but doing previous-thread from the next one does not. Here is the
original report:
---
Hi,
when in threaded mode, mutt doesn't jump to the first available message
when
executing previous-thread (default binding: ^P) when the parent of two
replies is not available, which is at least unexpected. In my case it goes
to the second subthread. I wanted to read all what I have of this thread
and
expected ^P to jump to the first message, so I can read all the messages
by
pressing right.
You can test this with the file prev_thread-test.mbox that is compressed
in
the attached file mutt_test_prev_thread.tar.bz2 [1]. Maybe an automated
test can
be done with the muttrc I wrote. After executing
$ mutt -f prev_thread-test.1.mbox -F muttrc
the created file content should be the same as content.expected.
Actually it gives the same as in content.not_expected.
Greeting,
Mike Dornberger
---
[1]
http://people.debian.org/~adeodato/tmp/2006-01-29/mutt_test_prev_thread.tar.bz2
How-To-Repeat:
Fix:
Unknown
}}}
--
Comment(by me):
The cause here is at thread.c:988 in find_virtual():
while (reverse cur-next)
cur = cur-next;
This occurs when moving to the previous (sub)thread and either it is
missing (only known via references: or in-reply-to:) or the current view
is limited; in either case the message is invisible.
I can only speculate that the intent here was when you had a deeply nested
thread tree that it might be confusing if the cursor jumped past the
immediately preceding subthread, since the messages are not indented as
far as they normally would be if the parent was actually visible.
--
Ticket URL: http://dev.mutt.org/trac/ticket/2171#comment:3
Mutt http://www.mutt.org/
The Mutt mail user agent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#565236: [Mutt] #3427: mutt-1.5.20: reply-hook . set realname=foo is executed too late
#3427: mutt-1.5.20: reply-hook . set realname=foo is executed too late +--- Reporter: fr...@…| Owner: mutt-dev Type: defect | Status: infoneeded_new Priority: major | Milestone: Component: mutt | Version: Resolution: fixed |Keywords: +--- Changes (by me): * cc: 565...@… (added) * status: new = infoneeded_new Comment: The code doing the alternates match was erroneously setting the real name when $reverse_realname was unset instead of letting the $realname be set in reply- and send-hooks. The patch attached to this bug report fixes that problem. -- Ticket URL: http://dev.mutt.org/trac/ticket/3427#comment:2 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521405: [Mutt] #3230: decode-copy/save clobbers all headers when $weed=yes
#3230: decode-copy/save clobbers all headers when $weed=yes --+- Reporter: anto...@… | Owner: mutt-dev Type: defect| Status: new Priority: minor | Milestone: Component: mutt | Version: 1.5.19 Keywords:| --+- Comment(by madduck): Yes, it seems that decode-save/-copy once did the right thing, but it sure does not work with 1.5.x anymore. -- Ticket URL: http://dev.mutt.org/trac/ticket/3230#comment:2 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#393926: [Mutt] #3246: Please make the internal viewer open diffs and/or text/*
#3246: Please make the internal viewer open diffs and/or text/* ---+ Reporter: anto...@… | Owner: mutt-dev Type: enhancement | Status: new Priority: trivial | Milestone: Component: display | Version: 1.5.19 Resolution:|Keywords: ---+ Comment(by ghelleks): I believe projekt21's regression also effects the ability to handle text/calendar in a useful way. .mailcap is only honored via autoview with this patch, which means that my clever calendar attachment processing happens automatically when I open the message. If I disable autoview, the text/calendar attachment is only handled by the internal editor. The preferred behavior is to be able to not use autoview, and instead launch a .mailcap handler script via view-attach instead of the internal viewer. -- Ticket URL: http://dev.mutt.org/trac/ticket/3246#comment:3 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549278: [Mutt] #3373: color header only matches first line of multi-line headers
#3373: color header only matches first line of multi-line headers ---+ Reporter: anto...@… | Owner: mutt-dev Type: defect| Status: closed Priority: trivial | Milestone: Component: display | Version: 1.5.20 Resolution: fixed |Keywords: ---+ Changes (by Michael Elkins m...@…): * status: new = closed * resolution: = fixed Comment: (In [b592852968f9]) allow regexps to match on continuation header lines in 'color header' commands. closes #3373 -- Ticket URL: http://dev.mutt.org/trac/ticket/3373#comment:1 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#553238: [Mutt] #3372: incorrect german translation for No undeleted messages.
#3372: incorrect german translation for No undeleted messages. ---+ Reporter: anto...@… | Owner: mutt-dev Type: defect| Status: closed Priority: trivial | Milestone: Component: mutt | Version: 1.5.20 Resolution: fixed |Keywords: patch ---+ Changes (by Antonio Radici anto...@…): * status: new = closed * resolution: = fixed Comment: (In [25459cbb132a]) Fix German translation of No undeleted messages. (closes #3372) -- Ticket URL: http://dev.mutt.org/trac/ticket/3372#comment:1 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#128945: [Mutt] #973: encrypt mail with more keys than recipient list (think mailinglist)
#973: encrypt mail with more keys than recipient list (think mailinglist) +--- Reporter: Marco d'Itri m...@… | Owner: mutt-dev Type: enhancement | Status: new Priority: trivial | Milestone: Component: crypto | Version: Keywords: #1610 + #1897 | +--- Comment(by Martin Sander): If you are looking for a workaround rather than a fix, here is how you can pull this off: For every user on your mailinglist that you want to encrypt to, add his key to a group in ~/.gnupg/gpg.conf: group 0x=14A32316 group 0x=29B3135D ... where the name of the group _has_ to be a hex-key, where usually it would be the address of the mailing list - mutt does not accept anything else. You can make one up, just make sure it does not collide with a key in your keyring. Now for every group that you have defined this way, add a crypt-hook to your .muttrc: crypt-hook my-mail...@list.com 0x Two caveats: Mutt will ask you if you want to use the key 0x for encryption, instead of just encrypting. Also the nice feature that mutt asks if you really want to encrypting with an untrusted public key does obviously not work, as mutt does not know which keys gpg will use.. -- Ticket URL: http://dev.mutt.org/trac/ticket/973#comment:7 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542344: [Mutt] #3331: mutt mangles display of time in From line
#3331: mutt mangles display of time in From line --+- Reporter: anto...@… | Owner: mutt-dev Type: defect| Status: new Priority: trivial | Milestone: Component: display | Version: 1.5.20 Keywords: patch | --+- Changes (by anto...@…): * status: infoneeded_new = new Comment: The patch is just code from what is currently present in hg that can be backported to 1.5.20 in Debian to fix this bug. To clarify: the bug is reproducible with 1.5.20 and NOT reproducible with the hg tip (because, I suppose, it contains that code). Resolving the bug because this is not an issue anymore. -- Ticket URL: http://dev.mutt.org/trac/ticket/3331#comment:3 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542344: [Mutt] #3331: mutt mangles display of time in From line
#3331: mutt mangles display of time in From line ---+ Reporter: anto...@… | Owner: mutt-dev Type: defect| Status: closed Priority: trivial | Milestone: Component: display | Version: 1.5.20 Resolution: fixed |Keywords: patch ---+ Changes (by anto...@…): * status: new = closed * resolution: = fixed -- Ticket URL: http://dev.mutt.org/trac/ticket/3331#comment:4 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530584: [Mutt] #3236: mutt: should use /var/tmp for mail drafts by default
#3236: mutt: should use /var/tmp for mail drafts by default --+- Reporter: anto...@… | Owner: mutt-dev Type: enhancement | Status: new Priority: minor | Milestone: Component: mutt | Version: Keywords:| --+- Changes (by msh): * cc: m...@… (added) -- Ticket URL: http://dev.mutt.org/trac/ticket/3236#comment:14 Mutt http://www.mutt.org/ The Mutt mail user agent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
