Re: [Mutt] #2749: %l in status_format (total size of folder) fails

#2749: %l in status_format (total size of folder) fails for IMAP servers Changes (by brendan): * status: new => closed * resolution: => fixed Comment: Fixed in [4f598543d7a5] -- Ticket URL:

Re: [Mutt] #2356: segfaults related to browser?

#2356: segfaults related to browser? Changes (by brendan): * status: new => closed * resolution: => fixed Old description: > {{{ > mutt segfaults when i execute the given macros. > > [cut here] > ## ~/.mutt/default (sourced in muttrc) > # unset imap_user > # unset imap_pass > set folder=~

Re: [Mutt] #2277: mailboxes in "mailboxes" directives do not

#2277: mailboxes in "mailboxes" directives do not auto-fill in change folder dialog when they have new mail Changes (by brendan): * keywords: => buffy * owner: mutt-dev => brendan * milestone: => 1.6 Old description: > {{{ > I am using mutt to access an IMAP server (Cyrus IMAPd 2.2.12)

Re: [Mutt] #2185: In manual.xml,

#2185: In manual.xml, "screen" contents should not exceed 79 columns Changes (by brendan): * component: mutt => doc * milestone: => 1.6 Old description: > {{{ > In manual.xml, one has for instance: > > display the next page (or next message if at the > end of a message) >

Re: [Mutt] #2749: %l in status_format (total size of folder) fails

#2749: %l in status_format (total size of folder) fails for IMAP servers Changes (by brendan): * owner: mutt-dev => brendan * milestone: => 1.6 Old description: > {{{ > The total size of folder %l always shows 0KB for every IMAP-server, > while it works OK for local mbox folders. > Untest

Re: [Mutt] #2684: crash on s/mime verification

#2684: crash on s/mime verification Changes (by brendan): * owner: mutt-dev => brendan * status: new => assigned * component: mutt => crypto * milestone: => 1.6 Old description: > {{{ > I tried to verify an S/MIME signed test mail with GPG encrypted body. But > I noticed two problem

Re: [Mutt] #2551: imap_sync_mailbox: EXPUNGE failed when synching

#2551: imap_sync_mailbox: EXPUNGE failed when synching mailbox Changes (by brendan): * status: assigned => closed * resolution: => wontfix Old description: > {{{ > when synching my inbox (after marking messages for deletion) I get the > following error: > > imap_sync_mailbox: EXPUNGE fail

Re: [Mutt] #2054: wish $signature %expandos

#2054: wish $signature %expandos Old description: > {{{ > i was writing a gen_signature shell script which takes param 1 as the > recipient name. However, it seems that the > set signature="script|" > command could only take one command value. Parameters are not supported. > That is inconvenient

Re: [Mutt] #2561: IMAP mail count in Mailboxes view not registering

#2561: IMAP mail count in Mailboxes view not registering true count when using multiple accounts. Changes (by brendan): * owner: mutt-dev => brendan * milestone: => 1.6 Old description: > {{{ > When starting mutt with the -y flag, the mail count displayed in > folder_format does not incre

Re: [Mutt] #2500: Segmentation fault when use tag-pattern or limit

#2500: Segmentation fault when use tag-pattern or limit Changes (by brendan): * status: new => closed * resolution: => wontfix Old description: > {{{ > I subscribe some mail lists. The incoming emails are classified by > procmail into several mail boxes. With these boxes, whenever I use >

Re: [Mutt] #2493: SEGV when replying to message with no From: header

#2493: SEGV when replying to message with no From: header Changes (by brendan): * status: assigned => closed * resolution: => worksforme Old description: > {{{ > I received an email message that has no From: header. It does have > Resent-From: and Sender:. If I press "r" to reply when t

Re: [Mutt] #2061: wish: mail composition crash recovery

#2061: wish: mail composition crash recovery Old description: > {{{ > if your tty gets a HUP while composing a mail (say, your inet conn breaks > or x crashes or whatever), it is tedious to continue composing the mail. > of course it works at all only if your editor has built-in crash > recovery,

Re: [Mutt] #2175: IMAP header cache segfault

#2175: IMAP header cache segfault Changes (by brendan): * milestone: => 1.6 Old description: > {{{ > I'm using mutt with an IMAP server and have enabled the IMAP header > cache. At times mutt segfaults when opening an already cached folder > with a few thousand mails. The variable header_c

Re: [Mutt] #2183: Messages marked as old even though mark_old set

#2183: Messages marked as old even though mark_old set to no Changes (by brendan): * status: new => closed * resolution: => wontfix Old description: > {{{ > I get my mail using fetchmail, which passes it to exim to deliver locally > (via procmail). > After recently upgrading to mutt 1.5.9

Re: [Mutt] #2428: S/MIME opaque signed mails unverified or undisplayed

#2428: S/MIME opaque signed mails unverified or undisplayed Changes (by brendan): * component: mutt => crypto Old description: > {{{ > > Hello ALL and others, > > When displaying S/MIME opaque signed mails, of type > application/x-pkcs7-mime; smime-type=signed-data, Mutt 1.5.13 with > de

Re: [Mutt] #2172: crashes (double free) when closing externally

#2172: crashes (double free) when closing externally modified mailbox Changes (by brendan): * status: new => closed * resolution: => worksforme Old description: > {{{ > (This comes from Debian Bug#346073.) > > When quitting after a mailbox has been emptied by an external program, > Mutt s

Re: [Mutt] #1672: mutt: Keys for PGP don't work (only for

#1672: mutt: Keys for PGP don't work (only for zh_TW.Big5 locale?) Changes (by brendan): * component: mutt => crypto Old description: > {{{ > Package: mutt > Version: 1.5.4+20030913-1 > Severity: normal > > [NOTE: this bug report has been submitted to the debian BTS as > Bug#187093. > Please

Re: [Mutt] #1455: unable to exit PGP key selection menu if key is

#1455: unable to exit PGP key selection menu if key is not found or expired on send Changes (by brendan): * component: mutt => crypto Old description: > {{{ > Package: mutt > Version: 1.4i > Severity: normal > > -- Please type your report below this line > > On sending a pgp encrypted messag

Re: [Mutt] #1535: attachments of type "application/xxx" cannot be

#1535: attachments of type "application/xxx" cannot be viewed Changes (by brendan): * component: mutt => MIME Old description: > {{{ > Package: mutt > Version: 1.5.3i > Severity: normal > > -- Please type your report below this line > When mutt sees an attachments of type "application/whatev

Re: [Mutt] #937: Mutt closes POP connection and hangs

#937: Mutt closes POP connection and hangs Changes (by brendan): * component: mutt => POP -- Ticket URL:

Re: [Mutt] #1665: Mutt crashes when selecting a key to encrypt with

#1665: Mutt crashes when selecting a key to encrypt with pgp 6.5.8 Changes (by brendan): * status: assigned => closed * resolution: => worksforme Old description: > {{{ > Package: mutt > Version: 1.5.4i > Severity: normal > > -- Please type your report below this line > > Hello, > >I

Re: [Mutt] #1565: Failure to pass correct subkey when encrypting (GPG)

#1565: Failure to pass correct subkey when encrypting (GPG) Changes (by brendan): * component: mutt => crypto Old description: > {{{ > Package: mutt > Version: mutt-1.4-4 > Severity: normal > > -- Please type your report below this line > When encrypting to a GPG key with multiple sub(encryp

Re: [Mutt] #1519: when replying to pgp-encrypted mail,

#1519: when replying to pgp-encrypted mail, message ist *not* included in reply Changes (by brendan): * status: new => closed * resolution: => wontfix * component: mutt => crypto Old description: > {{{ > Package: mutt > Version: 1.5.4-1 > Severity: normal > > -- Please type your report

Re: [Mutt] #2087: "%>" in pager_format overshoots by 10 repetitions

#2087: "%>" in pager_format overshoots by 10 repetitions Changes (by brendan): * owner: mutt-dev => brendan * status: new => assigned * component: mutt => display * milestone: => 1.6 Old description: > {{{ > Hi, this is Debian Bug#259145. The original report was: > > Hello, > > A co

Re: [Mutt] #2082: S/MIME signature verification fails on encrypted

#2082: S/MIME signature verification fails on encrypted and signed messages Changes (by brendan): * component: mutt => crypto Old description: > {{{ > Everytime I try to open a encrypted and signed message I get the > following error: > > [-- OpenSSL output follows (current time: Fr 16 Sep 2

Re: [Mutt] #1726: flea failed when reading a core

#1726: flea failed when reading a core Changes (by brendan): * status: reopened => closed * resolution: => wontfix Old description: > {{{ > Package: mutt > Version: 1.5.5i > Severity: important > > > -- Please type your report below this line > > > > Severity? [01234] 2 > > If mutt has cr

Re: [Mutt] #1670: Context-colored indicator bar does not work with

#1670: Context-colored indicator bar does not work with S-Lang Changes (by brendan): * component: mutt => display Old description: > {{{ > Package: mutt > Version: 1.5.4i > Severity: normal > > -- Please type your report below this line > > When "mono indicator reverse" is set, which is the

Re: [Mutt] #1672: mutt: Keys for PGP don't work (only for

#1672: mutt: Keys for PGP don't work (only for zh_TW.Big5 locale?) Changes (by brendan): * cc: Ambrose, Li, <[EMAIL PROTECTED]> (added) * status: new => closed * resolution: => fixed Comment: I've applied the patch in part -- many hunks did not apply. An updated translation would be ap

Re: [Mutt] #937: Mutt closes POP connection and hangs

#937: Mutt closes POP connection and hangs Old description: > {{{ > Package: mutt > Version: 1.3.24i > Severity: important > > -- Please type your report below this line > > Hi, > > After sending an e-mail, after the ISP connection had dropped and the > modem was redialing, when I entered 'i' to

Re: [Mutt] #862: format=flowed handler isn't utf-8 aware

#862: format=flowed handler isn't utf-8 aware Changes (by brendan): * reporter: [EMAIL PROTECTED] (Thomas Roessler) => [EMAIL PROTECTED] (Thomas Roessler) -- Ticket URL:

Re: [Mutt] #862: format=flowed handler isn't utf-8 aware

#862: format=flowed handler isn't utf-8 aware Changes (by brendan): * component: mutt => display * milestone: => 1.6 Old description: > {{{ > Package: mutt > Version: 1.3.23.1i > Severity: normal > > -- Please type your report below this line > > Just for the record: The format=flowed han

Re: [Mutt] #2790: re-executing a "too long" 'color body ...' cmd

#2790: re-executing a "too long" 'color body ...' cmd causes segv crash after a while Changes (by brendan): * component: mutt => display -- Ticket URL:

Re: [Mutt] #507: message/partial MIME type not handled as expected

#507: message/partial MIME type not handled as expected Changes (by brendan): * component: mutt => MIME -- Ticket URL:

Re: [Mutt] #2846: Security vulnerability in APOP authentication

#2846: Security vulnerability in APOP authentication Changes (by brendan): * component: mutt => POP -- Ticket URL:

Re: [Mutt] #2448: S/MIME decrypting keyid selection

#2448: S/MIME decrypting keyid selection Changes (by brendan): * component: mutt => crypto Old description: > {{{ > > Hello, > > There are some problems with S/MIME decrypting key selection, when > one has multiple keys, and has unset $smime_decrypt_use_default_key: > > -1) Before each

Re: [Mutt] #1160: multiple MIME boundary

#1160: multiple MIME boundary Changes (by brendan): * component: mutt => MIME Old description: > {{{ > Package: mutt > Version: 1.2.5.1i > Severity: normal > > -- Please type your report below this line > > Multiple boundary delimiter prevents mutt from recognising > MIME fields. In the exam

Re: [Mutt] #1125: Incorrect display of non-MIME content-types

#1125: Incorrect display of non-MIME content-types Changes (by brendan): * status: new => closed * resolution: => wontfix * component: mutt => MIME Old description: > {{{ > Package: mutt > Version: 1.3.27-4 > Severity: normal > > -- Please type your report below this line > If a conten

Re: [Mutt] #1100: gpg encryption to multiple recipients doesn't work

#1100: gpg encryption to multiple recipients doesn't work Changes (by brendan): * component: mutt => crypto Old description: > {{{ > Package: mutt > Version: 1.3.27-2 > Severity: normal > > [NOTE: this bug report has been submitted to the debian BTS as > Bug#137747. > Please Cc all your repl

Re: [Mutt] #1090: bcc:s given away through encryption

#1090: bcc:s given away through encryption Changes (by brendan): * component: mutt => crypto -- Ticket URL:

Re: [Mutt] #1607: bug 1417 not fixed in mutt 1.4.1: mutt leaves

#1607: bug 1417 not fixed in mutt 1.4.1: mutt leaves temp files after signing PGP- traditional Changes (by brendan): * status: new => closed * resolution: => fixed Old description: > {{{ > Package: mutt > Version: 1.4.1i > Severity: normal > > -- Please type your report below this line >

Re: [Mutt] #1567: segfault on reading a 1200 msg Maildir

#1567: segfault on reading a 1200 msg Maildir Changes (by brendan): * status: new => closed * resolution: => worksforme Old description: > {{{ > Package: mutt > Version: 1.5.4-1 > Severity: normal > > -- Please type your report below this line > > I have a Maildir with 1230 messages in it

Re: [Mutt] #1274: IMAP / limited view: new messages not always

#1274: IMAP / limited view: new messages not always detected Changes (by brendan): * status: reopened => closed * resolution: => worksforme Old description: > {{{ > Package: mutt > Version: 1.5.1-current-20020627i > Severity: normal > > -- Please type your report below this line > > With

Re: [Mutt] #1259: Bright* colors in index losing brightness in xterm.

#1259: Bright* colors in index losing brightness in xterm. Changes (by brendan): * component: mutt => display Old description: > {{{ > Package: mutt > Version: 1.4i > Severity: normal > > -- Please type your report below this line > > I have bright foreground colors in my index to highlight

Re: [Mutt] #1220: After telnet session dies, Mutt continues running,

#1220: After telnet session dies, Mutt continues running, gradually consuming all CPU resources. Changes (by brendan): * summary: mutt-: After telnet session dies, Mutt continues running, gradually consuming all CPU resources. => After telnet session dies, Mutt con

Re: [Mutt] #1090: bcc:s given away through encryption

#1090: bcc:s given away through encryption Old description: > {{{ > Package: mutt > Version: 1.3.25-1 > Severity: normal > > -- Please type your report below this line > > When encrypting (with gpg) and having several bccs, > it is encrypted to them all. So the to: and cc: recipients > can see th

Re: [Mutt] #507: message/partial MIME type not handled as expected

#507: message/partial MIME type not handled as expected Changes (by brendan): * milestone: => 1.6 Old description: > {{{ > Package: mutt > Version: 1.3.9i > Severity: normal > > -- Please type your report below this line > > If I receive multiple mail messages with MIME type message/partial,

Re: [Mutt] #681: rc of mutt_display_message differs between builtin

#681: rc of mutt_display_message differs between builtin and external pager Changes (by brendan): * component: mutt => display * milestone: => 1.6 Old description: > {{{ > Package: mutt > Version: 1.3.19i > Severity: normal > > -- Please type your report below this line > > for example, p

Re: [Mutt] #2707: On NFS creating files by mutt leaves empty

#2707: On NFS creating files by mutt leaves empty .muttXXX tmp-dirs behind Changes (by brendan): * priority: major => minor * milestone: => 1.6 Old description: > {{{ > Any file created is opened via "safe_open" in a .muttXXX subdir 1st > and then it wants to move/ rename to its real/ fin

Re: [Mutt] #2676: mutt + imap header results in a NULL pointer

#2676: mutt + imap header results in a NULL pointer dereference crash Changes (by brendan): * milestone: => 1.6 -- Ticket URL:

Re: [Mutt] #2545: Cannot open message with pgp key attachment

#2545: Cannot open message with pgp key attachment Comment (by brendan): I can't reproduce this here with tip. Can you? -- Ticket URL:

Re: [Mutt] #2545: Cannot open message with pgp key attachment

#2545: Cannot open message with pgp key attachment Changes (by brendan): * component: mutt => crypto * milestone: => 1.6 Old description: > {{{ > Trying to open a message with a PGP key attachment yields > "Could not copy message". > I can open both message parts separately from the > Att

Re: [Mutt] #2199: [gpgme] Sending ^C while running pinentry

#2199: [gpgme] Sending ^C while running pinentry segfaults Mutt Changes (by brendan): * status: assigned => closed * resolution: => fixed Comment: Patch applied, thanks. -- Ticket URL:

Re: [Mutt] #2575: "bind index z noop" makes mutt ignore "bind

#2575: "bind index z noop" makes mutt ignore "bind generic z current-middle" Changes (by brendan): * priority: major => minor Old description: > {{{ > I want to bind some keys to generic functions, but default > bindings for menus ovverride generic bindings defined by me. > When I "bind inde

Re: [Mutt] #2056: Attempt re-connect when idle mailbox connection

#2056: Attempt re-connect when idle mailbox connection closes Changes (by brendan): * owner: mutt-dev => brendan -- Ticket URL:

Re: [Mutt] #2540: Mutt crashes after IMAP timeout

#2540: Mutt crashes after IMAP timeout Changes (by brendan): * status: assigned => closed * resolution: => fixed Comment: I'm closing this. The reconnect bug is #2056. -- Ticket URL:

Re: [Mutt] #2056: Attempt re-connect when idle mailbox connection

#2056: Attempt re-connect when idle mailbox connection closes Old description: > {{{ > As requested by Brendan Cully in PR#2049: > In some environments - possibly dependent on particular IMAP > server software, firewalls, routers, etc. - the connection > to an IMAP mailbox can close when it remai

Re: [Mutt] #2570: crash when other MUA accesses IMAP

#2570: crash when other MUA accesses IMAP Changes (by yeled): * status: new => closed * resolution: => worksforme Comment: cannot replicate this anymore. -- Ticket URL:

[Mutt] #2871: test to [EMAIL PROTECTED]

#2871: test to [EMAIL PROTECTED] {{{ test }}} -- Ticket URL:

Re: IMAP regression after rev 5024

On Sunday, 01 April 2007 at 14:53, Jukka Salmi wrote: > Hi, > > with Mutt built using today's sources (rev 5034) I see the following > behaviour (I use IMAP mailboxes exclusively): after being started Mutt > seems to correctly determine which mailboxes contain new messages, > i.e. `change-folder'

Re: mutt cache sensitivity

Hi, * Kyle Wheeler [07-04-01 00:31:56 -0600] wrote: On Friday, March 30 at 03:29 PM, quoth Rocco Rutte: So... you're telling me that pointers are no longer stored in the hcache? Mutt (with hcache) no longer relies on malloc returning predictable results? No. Pointers are still stored. We do

IMAP regression after rev 5024

Hi, with Mutt built using today's sources (rev 5034) I see the following behaviour (I use IMAP mailboxes exclusively): after being started Mutt seems to correctly determine which mailboxes contain new messages, i.e. `change-folder' presents a list of mailboxes containing new messages. But after I'

Re: [Mutt] #2540: Mutt crashes after IMAP timeout

#2540: Mutt crashes after IMAP timeout Comment (by gjasny): I've build the nightly snapshot with debug and imap support against libssl. It still doesn't reconnect but at least doesn't crash anymore: Reorder: x = 3; hdr_count = 8 Reorder: From matches From: Mutt <[EMAIL PROTECTED]> Reorder:

Re: [Mutt] #2540: Mutt crashes after IMAP timeout

#2540: Mutt crashes after IMAP timeout Comment (by gjasny): With the latest mutt package from experimental (1.5.14+cvs20070321-1) it doesn't crash anymore. But a reconnct would be nice. IMAP queue drained parse_parameters: `charset="utf-8"' parse_parameter: `charset' = `utf-8' Reorder list