Re: Message security; protected header fields

2024-04-20 Thread Sirius via Mutt-dev
have not tried to get working, but there is some GUI offering of GnuPG for Windows, so I assume it is possible. > |I would like to hold off on this until the draft becomes an RFC, if \ > |it does. Agreed - though as Mutt can produce at least the Subject line this way when signing messages, we

Correct parsing of obsolete header syntax

2023-12-02 Thread Crystal Kolipe via Mutt-dev
Hi, When mutt parses a header line that includes a space in the header name field, it treats this line and all following lines as body text. This has the unwanted effect of moving genuine headers into the body of the message. Although the ASCII space character is not usually permitted

Correct parsing of obsolete header syntax

2023-12-02 Thread Crystal Kolipe via Mutt-dev
Hi, When mutt parses a header line that includes a space in the header name field, it treats this line and all following lines as body text. This has the unwanted effect of moving genuine headers into the body of the message. Although the ASCII space character is not usually permitted

Re: mutt on OpenBSD

2023-04-27 Thread ckeader via Mutt-dev
> I recently hit a similar issue on Gentoo when I tried building Mutt > using GnuTLS (forgot to note down the versions, but I think it was Mutt > 2.2.3 and GnuTLS 3.7.8 according to Portage logs). I backed out when I > saw the "accept cert" prompt, though, since I wasn't

mutt on OpenBSD

2023-04-25 Thread ckeader via Mutt-dev
This is more of a heads-up as the problem isn't in mutt per se. A while back, mutt stopped working correctly for me on OpenBSD, and of course, I completely failed to take notice at which point and with which release exactly ... What is the problem? When you connect to a server for the first time

[PATCH v3] Add socket send/receive timeout options

2022-12-01 Thread Matthew Sotoudeh via Mutt-dev
On an unreliable connection (e.g., laptop put to sleep and changing wifi networks) I've had mutt fairly regularly become stuck in SSL_read and have to be killed. Per some of the comments on https://stackoverflow.com/questions/46517875/ssl-read-blocks-indefinitely adding a timeout to the socket

Re: [PATCH v2] Add a receive_timeout option for sockets

2022-11-29 Thread Matthew Sotoudeh via Mutt-dev
On Tue, Nov 29, 2022 at 11:35:11AM -0800, Kevin J. McCarthy wrote: > On Tue, Nov 29, 2022 at 02:19:26PM +0100, Oswald Buddenhagen wrote: > > On Mon, Nov 28, 2022 at 11:24:13PM -0800, Matthew Sotoudeh via Mutt-dev > > wrote: > > > + ** Causes Mutt to timeout any so

Re: [PATCH v2] Add a receive_timeout option for sockets

2022-11-29 Thread Matthew Sotoudeh via Mutt-dev
Thanks for pointing that out ! To second Kevin's comments below, I personally didn't find a SNDTIMEO necessary. Also worth noting that, at least in my case, large writes (sending email, etc.) happen while I'm sitting down, so a much more stable network connection vs., e.g., background downloading

[PATCH v2] Add a receive_timeout option for sockets

2022-11-28 Thread Matthew Sotoudeh via Mutt-dev
On an unreliable connection (e.g., laptop put to sleep and changing wifi networks) I've had mutt fairly regularly become stuck in SSL_read and have to be killed. Per some of the comments on https://stackoverflow.com/questions/46517875/ssl-read-blocks-indefinitely adding a timeout to the socket

[PATCH] Updated: add a receive_timeout option for sockets

2022-11-28 Thread Matthew Sotoudeh via Mutt-dev
quot;, DT_NUM, R_NONE, {.p=}, {.l=0} }, + /* + ** .pp + ** Causes Mutt to timeout any socket read operation (e.g. SSL_read) after + ** this many seconds. A zero (default) or negative value causes Mutt to wait + ** indefinitely for the read to complete. + */ { "record", DT_

[PATCH] Add a receive_timeout option for sockets

2022-11-26 Thread Matthew Sotoudeh via Mutt-dev
On an unreliable connection (e.g., laptop put to sleep and changing wifi networks) I've had mutt fairly regularly become stuck in SSL_read and have to be killed. Per some of the comments on https://stackoverflow.com/questions/46517875/ssl-read-blocks-indefinitely adding a timeout to the socket

Re: [PATCH] bugfix for handling incomplete IMAP header cache

2021-08-21 Thread Pieter-Tjerk de Boer via Mutt-dev
On Sat, Aug 21, 2021 at 07:15:12AM -0700, Kevin J. McCarthy wrote: > On Sat, Aug 21, 2021 at 11:35:19AM +0200, Pieter-Tjerk de Boer via Mutt-dev wr > > This bug isn't just cosmetic; it can lead to unintended deletion of > > large amounts of mails. > > I'm very sorry t

[PATCH] bugfix for handling incomplete IMAP header cache

2021-08-21 Thread Pieter-Tjerk de Boer via Mutt-dev
d deletion of large amounts of mails. Let me give a step-by-step example of what went wrong and how that could lead to losing mail: 0. Use mutt with IMAP, header caching enabled, but not CONDSTORE nor QRESYNC. 1. Open an IMAP mailbox with e.g. 5 mails in it, with e.g. UIDs 11...15. 2. Mark the 3rd

[PATCH] Generate version string during make not configure

2019-04-10 Thread aaron+mutt
.am @@ -22,7 +22,7 @@ if BUILD_HCACHE HCVERSION = hcversion.h endif -BUILT_SOURCES = keymap_defs.h patchlist.c reldate.h conststrings.c $(HCVERSION) +BUILT_SOURCES = keymap_defs.h patchlist.c reldate.h conststrings.c version.h $(HCVERSION) bin_PROGRAMS = mutt $(DOTLOCK_TARGET) $(PGPAUX_TAR

[PATCH] Add format attribute for buffer_printf functions

2019-04-10 Thread aaron+mutt
Let compilers know that `mutt_buffer_printf()` and `mutt_buffer_add_printf()` expect the second argument to be a `printf`-style format string with the arguments for the format starting at the third argument. This allows warnings to be shown if these are incorrect. --- buffer.h | 2 ++ 1 file

Re: [Mutt] #3518: IDNA2008 support by libidn2 usage in mutt

2018-02-26 Thread Mutt
#3518: IDNA2008 support by libidn2 usage in mutt --+-- Reporter: rsc | Owner: mutt-dev Type: enhancement | Status: new Priority: major| Milestone: 2.0 Component: mutt |Version: Resolution

Re: [Mutt] #3990: segfault in hdr_format_str

2018-02-25 Thread Mutt
#3990: segfault in hdr_format_str --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: closed Priority: major| Milestone: Component: mutt |Version: Resolution: fixed

Re: [Mutt] #3990: segfault in hdr_format_str

2018-02-25 Thread Mutt
#3990: segfault in hdr_format_str --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: closed Priority: major| Milestone: Component: mutt |Version: Resolution: fixed

Re: [Mutt] #3990: segfault in hdr_format_str

2018-02-21 Thread Mutt
#3990: segfault in hdr_format_str --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: closed Priority: major| Milestone: Component: mutt |Version: Resolution: fixed

Re: [Mutt] #3989: segfault in mutt_local_tz

2018-02-21 Thread Mutt
#3989: segfault in mutt_local_tz --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: closed Priority: major| Milestone: Component: mutt |Version: Resolution: fixed

Re: [Mutt] #3990: segfault in hdr_format_str

2018-02-20 Thread Mutt
#3990: segfault in hdr_format_str --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: Resolution: | Keywords

Re: [Mutt] #3518: IDNA2008 support by libidn2 usage in mutt

2018-02-20 Thread Mutt
#3518: IDNA2008 support by libidn2 usage in mutt --+-- Reporter: rsc | Owner: mutt-dev Type: enhancement | Status: new Priority: major| Milestone: 2.0 Component: mutt |Version: Resolution

Re: [Mutt] #3990: segfault in hdr_format_str

2018-02-14 Thread Mutt
#3990: segfault in hdr_format_str --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: Resolution: | Keywords

Re: [Mutt] #3988: signed integer overflow in mbox_parse_mailbox

2018-02-14 Thread Mutt
#3988: signed integer overflow in mbox_parse_mailbox --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: closed Priority: major| Milestone: Component: mutt |Version: Resolution

Re: [Mutt] #3988: signed integer overflow in mbox_parse_mailbox

2018-02-14 Thread Mutt
#3988: signed integer overflow in mbox_parse_mailbox --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: Resolution

Re: [Mutt] #3988: signed integer overflow in mbox_parse_mailbox

2018-02-13 Thread Mutt
#3988: signed integer overflow in mbox_parse_mailbox --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: Resolution

Re: [Mutt] #3988: signed integer overflow in mbox_parse_mailbox

2018-02-13 Thread Mutt
#3988: signed integer overflow in mbox_parse_mailbox --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: Resolution

Re: [Mutt] #3988: signed integer overflow in mbox_parse_mailbox

2018-02-13 Thread Mutt
#3988: signed integer overflow in mbox_parse_mailbox --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: Resolution

Re: [Mutt] #3988: signed integer overflow in mbox_parse_mailbox

2018-02-13 Thread Mutt
#3988: signed integer overflow in mbox_parse_mailbox --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: Resolution

Re: [Mutt] #3990: segfault in hdr_format_str

2018-02-11 Thread Mutt
#3990: segfault in hdr_format_str --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: Resolution: | Keywords

Re: [Mutt] #3990: segfault in hdr_format_str

2018-02-11 Thread Mutt
#3990: segfault in hdr_format_str --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: Resolution: | Keywords

Re: [Mutt] #3989: segfault in mutt_local_tz

2018-02-11 Thread Mutt
#3989: segfault in mutt_local_tz --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: Resolution: | Keywords

Re: [Mutt] #3988: signed integer overflow in mbox_parse_mailbox

2018-02-11 Thread Mutt
#3988: signed integer overflow in mbox_parse_mailbox --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: Resolution

Re: [Mutt] #3990: segfault in hdr_format_str

2018-02-10 Thread Mutt
#3990: segfault in hdr_format_str --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: Resolution: | Keywords

[Mutt] #3990: segfault in hdr_format_str

2018-02-10 Thread Mutt
#3990: segfault in hdr_format_str -+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: Keywords

Re: [Mutt] #3989: segfault in mutt_local_tz

2018-02-10 Thread Mutt
#3989: segfault in mutt_local_tz --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: Resolution: | Keywords

[Mutt] #3989: segfault in mutt_local_tz

2018-02-10 Thread Mutt
#3989: segfault in mutt_local_tz -+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: Keywords

Re: [Mutt] #3988: signed integer overflow in mbox_parse_mailbox

2018-02-10 Thread Mutt
#3988: signed integer overflow in mbox_parse_mailbox --+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: Resolution

[Mutt] #3988: signed integer overflow in mbox_parse_mailbox

2018-02-10 Thread Mutt
#3988: signed integer overflow in mbox_parse_mailbox -+-- Reporter: josephbisch | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: Keywords

Re: [Mutt] #3195: mutt-1.5.19: The crash of mutt's pager on messages with quoted text.

2018-01-30 Thread Mutt
#3195: mutt-1.5.19: The crash of mutt's pager on messages with quoted text. --+-- Reporter: rdna@… | Owner: mutt-dev Type: defect | Status: closed Priority: major| Milestone: Component: mutt |Version: Resolution

Re: [Mutt] #2900: mutt-1.5.15: Crashes on a mail message in a very wide xterm

2018-01-30 Thread Mutt
#2900: mutt-1.5.15: Crashes on a mail message in a very wide xterm -+-- Reporter: olav@… | Owner: mutt-dev Type: defect | Status: closed Priority: major | Milestone: Component: mutt|Version: Resolution: fixed

Re: [Mutt] #1471: omission of reference to "include" in manual

2018-01-30 Thread Mutt
#1471: omission of reference to "include" in manual ---+-- Reporter: rupert@… | Owner: mutt-dev Type: defect| Status: closed Priority: trivial | Milestone: Component: mutt |Version: 1.3.28i Resoluti

Re: [Mutt] #1046: Request that the "uncolor" command work with "body"/"header" objects in addition to "index"

2018-01-30 Thread Mutt
#1046: Request that the "uncolor" command work with "body"/"header" objects in addition to "index" --+-- Reporter: arno@… | Owner: mutt-dev Type: enhancement | Status: closed Priority

Re: [Mutt] #3987: Bug in Yahoo Mail where body contains an empty text attachment if sent through mutt

2018-01-25 Thread Mutt
#3987: Bug in Yahoo Mail where body contains an empty text attachment if sent through mutt --+-- Reporter: Peter92 | Owner: mutt-dev Type: defect | Status: new Priority: minor| Milestone: Component: mutt |Version

Re: [Mutt] #3986: send-hook for Cc and Bcc executed too late

2018-01-25 Thread Mutt
#3986: send-hook for Cc and Bcc executed too late ---+-- Reporter: alahouze | Owner: mutt-dev Type: defect| Status: closed Priority: major | Milestone: Component: mutt |Version: Resolution: invalid

Re: [Mutt] #3987: Bug in Yahoo Mail where body contains an empty text attachment if sent through mutt

2018-01-25 Thread Mutt
#3987: Bug in Yahoo Mail where body contains an empty text attachment if sent through mutt --+-- Reporter: Peter92 | Owner: mutt-dev Type: defect | Status: new Priority: minor| Milestone: Component: mutt |Version

[Mutt] #3987: Bug in Yahoo Mail where body contains an empty text attachment if sent through mutt

2018-01-25 Thread Mutt
#3987: Bug in Yahoo Mail where body contains an empty text attachment if sent through mutt -+-- Reporter: Peter92 | Owner: mutt-dev Type: defect | Status: new Priority: minor| Milestone: Component: mutt |Version: 1.5.24

Re: [Mutt] #3986: send-hook for Cc and Bcc executed too late

2018-01-23 Thread Mutt
#3986: send-hook for Cc and Bcc executed too late ---+-- Reporter: alahouze | Owner: mutt-dev Type: defect| Status: closed Priority: major | Milestone: Component: mutt |Version: Resolution: invalid

Re: [Mutt] #3986: send-hook for Cc and Bcc executed too late

2018-01-23 Thread Mutt
#3986: send-hook for Cc and Bcc executed too late ---+-- Reporter: alahouze | Owner: mutt-dev Type: defect| Status: new Priority: major | Milestone: Component: mutt |Version: Resolution

[Mutt] #3986: send-hook for Cc and Bcc executed too late

2018-01-23 Thread Mutt
#3986: send-hook for Cc and Bcc executed too late --+-- Reporter: alahouze | Owner: mutt-dev Type: defect| Status: new Priority: major | Milestone: Component: mutt |Version

Re: [Mutt] #3985: viewing HTML attachments frequently fails with "File not found"

2018-01-18 Thread Mutt
#3985: viewing HTML attachments frequently fails with "File not found" ---+-- Reporter: adrianvm | Owner: mutt-dev Type: defect| Status: closed Priority: major | Milestone: Component: mutt |Version:

Re: [Mutt] #3985: viewing HTML attachments frequently fails with "File not found"

2018-01-18 Thread Mutt
#3985: viewing HTML attachments frequently fails with "File not found" ---+-- Reporter: adrianvm | Owner: mutt-dev Type: defect| Status: closed Priority: major | Milestone: Component: mutt |Version:

[Mutt] #3985: viewing HTML attachments frequently fails with "File not found"

2018-01-17 Thread Mutt
#3985: viewing HTML attachments frequently fails with "File not found" --+-- Reporter: adrianvm | Owner: mutt-dev Type: defect| Status: new Priority: major | Milestone: Component: mutt |Version:

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2018-01-12 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2018-01-11 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: closed Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2018-01-10 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2018-01-10 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2018-01-10 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2018-01-09 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2018-01-09 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2018-01-09 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2018-01-08 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2018-01-08 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2018-01-08 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3984: Very large IMAP folders result in "could not copy message"

2018-01-06 Thread Mutt
#3984: Very large IMAP folders result in "could not copy message" -+-- Reporter: darac | Owner: mutt-dev Type: defect | Status: closed Priority: major | Milestone: Component: IMAP|Version: Resoluti

Re: [Mutt] #3984: Very large IMAP folders result in "could not copy message"

2018-01-05 Thread Mutt
#3984: Very large IMAP folders result in "could not copy message" -+-- Reporter: darac | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: IMAP|Version:

Re: [Mutt] #3984: Very large IMAP folders result in "could not copy message"

2018-01-05 Thread Mutt
#3984: Very large IMAP folders result in "could not copy message" -+-- Reporter: darac | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: IMAP|Version:

[Mutt] #3984: Very large IMAP folders result in "could not copy message"

2018-01-05 Thread Mutt
#3984: Very large IMAP folders result in "could not copy message" +-- Reporter: darac | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: IMAP|Version: Keywor

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2018-01-04 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2018-01-04 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2017-12-31 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3755: imap: accumulates the same certificate over and over in ~/.mutt/certificates but doesn't recognize at startup

2017-12-29 Thread Mutt
#3755: imap: accumulates the same certificate over and over in ~/.mutt/certificates but doesn't recognize at startup -+- Reporter: ecloud | Owner: brendan Type: defect | Status: closed Priority: major | Milestone: Component

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2017-12-29 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2017-12-29 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2017-12-29 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2017-12-28 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3755: imap: accumulates the same certificate over and over in ~/.mutt/certificates but doesn't recognize at startup

2017-12-28 Thread Mutt
#3755: imap: accumulates the same certificate over and over in ~/.mutt/certificates but doesn't recognize at startup -+- Reporter: ecloud | Owner: brendan Type: defect | Status: new Priority: major | Milestone: Component: IMAP

Re: [Mutt] #3476: copyright years are not up-to-date

2017-12-27 Thread Mutt
#3476: copyright years are not up-to-date -+-- Reporter: vinc17 | Owner: mutt-dev Type: defect | Status: closed Priority: major | Milestone: Component: mutt|Version: Resolution: fixed | Keywords

Re: [Mutt] #3962: Backspace Key doesn't work in pager and Tmux

2017-12-27 Thread Mutt
#3962: Backspace Key doesn't work in pager and Tmux -+--- Reporter: ManDay | Owner: mutt-dev Type: defect | Status: closed Priority: major | Milestone: Component: user interface |Version

Re: [Mutt] #3980: Can we integrate support for /etc/mailname?

2017-12-21 Thread Mutt
#3980: Can we integrate support for /etc/mailname? +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: closed Priority: trivial| Milestone: Component: mutt |Version: 1.9.1 Resolution: wontfix

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2017-12-19 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2017-12-18 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

Re: [Mutt] #3982: recipient's S/MIME certificate disappear after sending encrypted email

2017-12-18 Thread Mutt
#3982: recipient's S/MIME certificate disappear after sending encrypted email --+-- Reporter: michele | Owner: mutt-dev Type: defect | Status: closed Priority: major| Milestone: Component: mutt |Version: 1.9.1

Re: [Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2017-12-17 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) --+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt

[Mutt] #3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt)

2017-12-17 Thread Mutt
#3983: Change smime_self_encrypt default to yes (same for pgp_self_encrypt) -+-- Reporter: michele | Owner: mutt-dev Type: enhancement | Status: new Priority: minor| Milestone: Component: mutt |Version

Re: [Mutt] #3982: recipient's S/MIME certificate disappear after sending encrypted email

2017-12-16 Thread Mutt
#3982: recipient's S/MIME certificate disappear after sending encrypted email --+-- Reporter: michele | Owner: mutt-dev Type: defect | Status: closed Priority: major| Milestone: Component: mutt |Version: 1.9.1

Re: [Mutt] #3982: recipient's S/MIME certificate disappear after sending encrypted email

2017-12-16 Thread Mutt
#3982: recipient's S/MIME certificate disappear after sending encrypted email --+-- Reporter: michele | Owner: mutt-dev Type: defect | Status: closed Priority: major| Milestone: Component: mutt |Version: 1.9.1

Re: [Mutt] #3982: recipient's S/MIME certificate disappear after sending encrypted email

2017-12-15 Thread Mutt
#3982: recipient's S/MIME certificate disappear after sending encrypted email --+-- Reporter: michele | Owner: mutt-dev Type: defect | Status: closed Priority: major| Milestone: Component: mutt |Version: 1.9.1

Re: [Mutt] #3982: recipient's S/MIME certificate disappear after sending encrypted email

2017-12-15 Thread Mutt
#3982: recipient's S/MIME certificate disappear after sending encrypted email --+-- Reporter: michele | Owner: mutt-dev Type: defect | Status: closed Priority: major| Milestone: Component: mutt |Version: 1.9.1

Re: [Mutt] #3982: recipient's S/MIME certificate disappear after sending encrypted email

2017-12-15 Thread Mutt
#3982: recipient's S/MIME certificate disappear after sending encrypted email --+-- Reporter: michele | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: 1.9.1

[Mutt] #3982: recipient's S/MIME certificate disappear after sending encrypted email

2017-12-15 Thread Mutt
#3982: recipient's S/MIME certificate disappear after sending encrypted email -+-- Reporter: michele | Owner: mutt-dev Type: defect | Status: new Priority: major| Milestone: Component: mutt |Version: 1.9.1 Keywords

Re: [Mutt] #3981: auto loging issue

2017-12-11 Thread Mutt
#3981: auto loging issue -+-- Reporter: harsh | Owner: mutt-dev Type: defect | Status: closed Priority: major | Milestone: Component: mutt|Version: Resolution: fixed | Keywords

Re: [Mutt] #3981: auto loging issue

2017-12-11 Thread Mutt
#3981: auto loging issue -+-- Reporter: harsh | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: mutt|Version: Resolution: | Keywords

Re: [Mutt] #3981: auto loging issue

2017-12-10 Thread Mutt
#3981: auto loging issue -+-- Reporter: harsh | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: mutt|Version: Resolution: | Keywords

Re: [Mutt] #973: encrypt mail with more keys than recipient list (think mailinglist)

2017-12-10 Thread Mutt
#973: encrypt mail with more keys than recipient list (think mailinglist) --+--- Reporter: Marco d'Itri <md@…> | Owner: mutt-dev Type: enhancement | Status: closed Priority: trivial | Mil

Re: [Mutt] #3687: Threads expand when other IMAP clients access IMAP folder

2017-12-10 Thread Mutt
#3687: Threads expand when other IMAP clients access IMAP folder -+-- Reporter: G11_a | Owner: mutt-dev Type: defect | Status: closed Priority: minor | Milestone: Component: user interface

Re: [Mutt] #3975: Not plain/text /usr/share/doc/mutt/manual.txt.gz

2017-12-10 Thread Mutt
#3975: Not plain/text /usr/share/doc/mutt/manual.txt.gz --+-- Reporter: jaalto | Owner: mutt-dev Type: defect | Status: closed Priority: trivial | Milestone: Component: mutt |Version: Resolution: wontfix

Re: [Mutt] #3980: Can we integrate support for /etc/mailname?

2017-12-10 Thread Mutt
#3980: Can we integrate support for /etc/mailname? +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: closed Priority: trivial| Milestone: Component: mutt |Version: 1.9.1 Resolution: wontfix

[Mutt] #3981: auto loging issue

2017-12-05 Thread Mutt
#3981: auto loging issue +-- Reporter: harsh | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: mutt|Version: Keywords: | +-- need

Re: [Mutt] #3980: Can we integrate support for /etc/mailname?

2017-12-04 Thread Mutt
#3980: Can we integrate support for /etc/mailname? +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: new Priority: trivial| Milestone: Component: mutt |Version: 1.9.1 Resolution

  1   2   3   4   5   6   7   8   9   10   >