ticket summary component version milestone type owner status created _changetime _description _reporter 3564 can't choose certain public keys for encryption even when specifying the keyID mutt 1.5.21 defect kevin8t8 assigned 2012-02-01T22:56:34-08:00 2013-04-10T19:57:12-07:00 I get stuck when trying to send an encrypted mail after entering 0xbc8002f3 as keyID... mutt keeps asking me for keyID. The key is in my keyring but it is not listed when entering nothing. You can fetch the key from the keyservers. Please help! Thank you! likkk 714 Lines starting From aren't escaped saving from Maildir to mbox mutt 1.2.5i defect mutt-dev new 2001-07-30T17:45:28-07:00 2007-12-30T09:47:58-08:00 "Send a mail to an address which is saved into a Maildir folder; in the mail, include a line which starts ""From"". Start mutt on that folder. Read the message, save to a normal mbox folder. Look at the folder with a text-viewer, see that the line hasn't been escaped with a "">"". Mutt survives, thanks to the Content-Length: header. Mailers which don't understand that header get upset (as does Mutt if the header is deleted). Since Mutt supports multiple mailbox formats, it needs to understand the body conversions necessary when moving between formats. I've just confirmed that "">From"" isn't changed into ""From"" when saving _to_ Maildir format, but this is arguably more problematic. Bug confirmed present in 1.3.19i." Phil Pennock 2448 S/MIME decrypting keyid selection crypto 1.5.13 defect mutt-dev new 2006-08-25T05:31:02-07:00 2007-04-01T19:38:15-07:00 "{{{ 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 display of a crypted message, Mutt iteratively prompts for the decrypting key to use: | Use ID 12345678.1 for email@example.com ? ([no]/yes): | Use ID 12345678.2 for email@example.com ? ([no]/yes): | Use ID 12345678.x for email@example.com ? ([no]/yes): | Use ID 12345678.0 for email@example.com ? ([no]/yes): | Enter keyID for email@example.com: ...and finally shows the smime menu listing all available private keys, even for other email addreses: | S/MIME certificates matching """". That's not very practical, given that: - User may not know which encrypting key was used. - User may not remember which 12345678.x selects the wanted key (display the certficate's label would help). - The firsts y/n prompts are disordered: The last prompted "".0"" was the first in ~/.smime/keys/.index - The labels are displayed only at the 6th step, the key listing. - Each selection of a different keyid wipes the passphrase. - There is no error on misselected keyid, just an empty body. - There is no error on mistyped passphrase, just an empty body. - The whole sequence restarts each time user does , , , or goes to view another crypted message. Possible solutions: -a) Is there really no full automatic way to guess which key encrypted the message? -b) Could we store as many passphrases as keyids? Or optionally a single passphrase for all keyids? The current halfway scheme doesn't seem to make much sense. -c) In such long iterative selection sequences, shouldn't there be a shortcut to go directly to the listing? Maybe something similar to ""?"" at prompt going to browser, or yet another $option. Further problems: -2) and dont't prompt for a key, nor passphrase, and won't decrypt. Result is original crypted mail. -3) and do prompt for a passphrase, but not for a keyid. If crypted message, last selected keyid, and passphrase are matching: Result is the expected decoded and decrypted message. Otherwise result is a message with silently lost empty body. Without any error nor warning. -4) Doing on an S/MIME opaque signed message (that is *not* crypted) uselessly starts the keyid selection sequence (but doesn't prompt for a passphrase). Bye! Alain. >How-To-Repeat: >Fix: }}}" Alain Bench 2827 deleting attachment on imap and sync removes message from index IMAP 1.5.20 defect mutt-dev new 2007-03-06T10:35:02-08:00 2009-06-23T05:06:10-07:00 "{{{ The following was submitted as Debian bug #152012: ----- Forwarded message from Louis-David Mitterrand ---= -- Date: Fri, 5 Jul 2002 14:58:35 +0200 From: Louis-David Mitterrand Reply-To: 152012@bugs.debian.org To: Debian Bug Tracking System Subject: mutt: deleting attachement on imap box and sync'ing removes mess= age from index Package: mutt Version: 1.4.0-1 Severity: normal Log into a courier-imap server with mutt, delete an attachement, press $ and watch the message disappear from the index. Quit and log in again to get the message back. ----- End forwarded message ----- ----- Forwarded message from Adeodato Sim=F3 ----- Date: Tue, 25 May 2004 23:28:00 +0200 From: Adeodato Sim=F3 To: 152012@bugs.debian.org, mutt-dev@mutt.org Subject: Re: mutt: deleting attachement on imap box and sync'ing removes = message from index Mail-Followup-To: 152012@bugs.debian.org, mutt-dev@mutt.org [This is debian's bug#152012.] * Louis-David Mitterrand [Fri, 05 Jul 2002 14:58:35 +0200]: > Log into a courier-imap server with mutt, delete an attachement, press = $ > and watch the message disappear from the index. Quit and log in again t= o > get the message back. other servers will print a warning: ""CLIENT BUG DETECTED: STATUS on selected mailbox: INBOX"". there was once a similar case in comp.mail.mutt [1] that happened when deleting messages. it was fixed in 1.3.20 and of course it doesn't happen anymore when deleting messages, but it does when deleting attachments. any comments wrt this? [1] http://groups.google.com/groups?hl=3Den&lr=3D&ie=3DUTF-8&threadm=3D= 3B6776D9.60201%40cs.rose-hulman.edu&rnum=3D1&prev=3D/groups%3Fq%3D%2522ST= ATUS%2Bon%2Bselected%2Bmailbox%2522%2Bgroup:comp.mail.mutt%26hl%3Den%26lr= %3D%26ie%3DUTF-8%26group%3Dcomp.mail.mutt%26selm%3D3B6776D9.60201%2540cs.= rose-hulman.edu%26rnum%3D1%26filter%3D0 ----- End forwarded message ----- ----- Forwarded message from Louis-David Mitterrand ---= -- Date: Tue, 6 Mar 2007 18:48:22 +0100 From: Louis-David Mitterrand Reply-To: Louis-David Mitterrand , 152012@bugs.debian.or= g To: Christoph Berg , 152012@bugs.debian.org Subject: Bug#152012: mutt: deleting attachement on imap box and sync'ing removes message from index On Tue, Mar 06, 2007 at 06:47:01PM +0100, Christoph Berg wrote: > tags 152012 + moreinfo > thanks >=20 > Re: Louis-David Mitterrand 2002-07-05 <20020705125835.GA1424@apartia.or= g> > > Log into a courier-imap server with mutt, delete an attachement, pres= s $ > > and watch the message disappear from the index. Quit and log in again= to > > get the message back. >=20 > it's been a long time since you reported this. I just tried with my > local dovecot-imapd and everything was fine. Can you still reproduce > this bug? Hello, Yes the bug is still there with latest unstable mutt and courier. ----- End forwarded message ----- Christoph --=20 cb@df7cb.de | http://www.df7cb.de/ >Fix: Unknown }}}" Christoph Berg 3630 mutt-1.5.20: Segfault during hcache_open_db4() mutt defect mutt-dev new 2013-01-26T19:59:57-08:00 2013-01-26T19:59:57-08:00 "{{{ Package: mutt Version: mutt-1.5.20-2.20091214hg736b6a.el6_1.1.x86_64 Severity: important -- Please type your report below this line Backtrace from gdb (compiled with -O0): Program received signal SIGSEGV, Segmentation fault. 0x00007ffff735c024 in __env_get_errcall () from /lib64/libdb-4.7.so Missing separate debuginfos, use: debuginfo-install db4-4.7.25-17.el6.x86_64 glibc-2.12-1.80.el6_3.6.x86_64 keyutils-libs-1.4-4.el6.x86_64 krb5-libs-1.9-33.el6_3.3.x86_64 libcom_err-1.41.12-12.el6.x86_64 libidn-1.18-2.el6.x86_64 libselinux-2.0.94-5.3.el6.x86_64 ncurses-libs-5.7-3.20090208.el6.x86_64 openssl-1.0.0-25.el6_3.1.x86_64 zlib-1.2.3-27.el6.x86_64 (gdb) bt #0 0x00007ffff735c024 in __env_get_errcall () from /lib64/libdb-4.7.so #1 0x00000000004a8479 in hcache_open_db4 (h=0x7d27c0, path=0x6e5dc0 ""./cache/headers/imaps:beckerjes@mail.nih.gov/INBOX.hcache"") at hcache.c:1048 #2 0x00000000004a8980 in mutt_hcache_open ( path=0x6e5dc0 ""./cache/headers/imaps:beckerjes@mail.nih.gov/INBOX.hcache"", folder=0x7fffffffc2e0 ""imaps:beckerjes@mail.nih.gov/INBOX"", namer=0x4b610d ) at hcache.c:1177 #3 0x00000000004b6275 in imap_hcache_open () #4 0x00000000004b138e in imap_mboxcache_get () #5 0x00000000004aed36 in imap_open_mailbox () #6 0x0000000000452d7b in mx_open_mailbox () #7 0x0000000000446690 in main () -- System Information System Version: Linux helix.nih.gov 2.6.32-279.19.1.el6.x86_64 #1 SMP Sat Nov 24 14:35:28 EST 2012 x86_64 x86_64 x86_64 GNU/Linux RPM Packager: Red Hat, Inc. RedHat Release: Red Hat Enterprise Linux Server release 6.3 (Santiago) -- Mutt Version Information Mutt 1.5.20 (2009-12-10) Copyright (C) 1996-2009 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.6.32-279.19.1.el6.x86_64 (x86_64) ncurses: ncurses 5.7.20090207 (compiled with 5.7) libidn: 1.18 (compiled with 1.18) hcache backend: tokyocabinet 1.4.33 Compile options: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID -USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +USE_SMTP -USE_SSL_OPENSSL +USE_SSL_GNUTLS +USE_SASL +USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE ISPELL=""/usr/bin/hunspell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. }}} " beckerjes@… 2893 fcc_attach=no should record filenames (like deleted attachments) mutt defect mutt-dev new 2007-05-23T01:26:35-07:00 2009-06-04T16:26:20-07:00 " {{{ Forwarding to trac so we don't forget it... ----- Forwarded message from Louis-David Mitterrand ----- Date: Thu, 3 May 2007 17:21:26 +0200 From: Louis-David Mitterrand To: mutt-dev@mutt.org Subject: fcc_attach=no improvement suggestion Hello, I am following the exciting new rythm of mutt's development and this leads me to humbly submit an improvement request. When fcc_attach=no outgoing attachements are not saved in the 'Sent' mailbox however it would be convenient to have a record of what was attached at the time it was sent: file path, size and last modification. This would nicely improve the audit'ability of one's sent mail without inflating it. Thanks for your consideration, ----- End forwarded message ----- }}}" myon 2933 erroneously QP-encoded for PE executable mutt 1.4 defect mutt-dev infoneeded_new 2007-07-18T19:56:06-07:00 2009-06-12T05:05:37-07:00 "I sent the sample file attached with Mutt -a, but after saving the attachment to a file, the md5 checksum to the file is changed. Both mutt-1.4.2.3-1.fc6 on fc6 and mutt-1.5.14-4.fc7 on fedora 7 have the same issue. Original md5 sum: 0e37c055d7b3184d3530db1e06b948d5 Newly saved md5sum: b649d4991851c2757734432ce3a0c773 WARNING! The attached is virus infected, please handle with care." hubertwslin 2944 "mutt-1.5.16cvs: ""bind map KEY noop"" KEY rebound to macro does not activate despite listing against unbound in key bindings display." mutt 1.5.16 defect mutt-dev new 2007-08-19T07:03:46-07:00 2007-08-19T08:33:10-07:00 " {{{ Package: mutt Version: 1.5.12-1ubuntu1.1 Severity: normal -- Please type your report below this line Mutt fails (in CVS as of 2007-08-19 as well as Ubuntu-6.10 packaged 1.5.12) to accept that a key has been rebound to a macro, despite this binding being shown in the help display. To illustrate: :bind index r noop :macro index r ""display-message ; reply"" when r is pressed in the index view, ""Key is not bound."" However, in the listing of keybindings (produced with a ?) I see [...] q quit save changes to mailbox and quit r macro display-message; reply s save-message save message/attachment to a file u undelete-message undelete the current entry [...] I think this may be related to ticket #1880, opened 3 years ago but still showing as unclosed, relating to the difference between binding to a null operation, and removing a binding entirely. My speculation is that owing to a binding to a noop, Mutt never falls through to check whether there is a macro binding for that key. The patch for 1.5.1 provided by David Cohen will no longer apply to Mutt. -- 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 Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr --enable-checking=release i486-linux-gnu Thread model: posix gcc version 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.16cvs (2007-07-25) Copyright (C) 1996-2007 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.6.17-10-386 (i686) ncurses: ncurses 5.5.20060422 (compiled with 5.5) libidn: 0.6.3 (compiled with 0.6.3) Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_INODESORT -USE_POP -USE_IMAP -USE_SMTP -USE_GSS -USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID -USE_HCACHE -ISPELL SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. --- Begin /usr/local/etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb ""~b "" ""search in message bodies"" macro index,pager,attach,compose \cb ""\ set my_pipe_decode=\$pipe_decode pipe_decode\ urlview\ set pipe_decode=\$my_pipe_decode; unset my_pipe_decode"" \ ""call urlview to extract URLs out of a message"" macro generic,pager "" less /usr/local/doc/mutt/manual.txt"" ""show Mutt documentation"" macro index,pager y ""?"" ""show incoming mailboxes list"" bind browser y exit attachments +A */.* attachments -A text/x-vcard application/pgp.* attachments -A application/x-pkcs7-.* attachments +I text/plain attachments -A message/external-body attachments -I message/external-body --- End /usr/local/etc/Muttrc }}}" Yorudan 3006 mutt-1.5.17: MIME boundaries should not be displayed on the only text/plain part display defect mutt-dev new 2007-12-23T15:21:26-08:00 2009-07-09T18:58:37-07:00 " {{{ Package: mutt Version: 1.5.17 Severity: normal -- Please type your report below this line Alpine, a successor of Pine MUA, by default sends 8-bit mail as MIME multipart/mixed with only one text/plain part. For example: ,---- | [...] | User-Agent: Alpine 0.99999 (DEB 796 2007-11-08) | MIME-Version: 1.0 | Content-Type: MULTIPART/MIXED; | BOUNDARY=""-1463811583-823278545-1198451178=:5415"" | | This message is in MIME format. The first part should be readable | text, | while the remaining parts are likely unreadable without MIME-aware | tools. | | ---1463811583-823278545-1198451178=:5415 | Content-Type: TEXT/PLAIN; format=flowed; charset=KOI8-R | Content-Transfer-Encoding: 8BIT | | ôÅÓÔ | ---1463811583-823278545-1198451178=:5415-- `---- Mutt displays this message correctly, but it prepends the display with a text/PLAIN boundary. This style: ,---- | [...] | User-Agent: Alpine 0.99999 (DEB 796 2007-11-08) | | [-- Attachment #1 --] | [-- Type: text/PLAIN, Encoding: 8bit, Size: 0.1K --] | | ôÅÓÔ `---- My suggestion is that Mutt really should not display this boundary if the message has an only text/plain part. -- System Information System Version: FreeBSD hub.flexpro.ru 6.3-RC1 FreeBSD 6.3-RC1 #0: Mon Dec 3 13:15:16 MSK 2007 root@hub.flexpro.ru:/usr/src/sys/i386/compile/HUB i386 -- 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 cc -I/usr/local/include Using built-in specs. Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 3.4.6 [FreeBSD] 20060305 - CFLAGS -O2 -fno-strict-aliasing -pipe -march=pentiumpro -- Mutt Version Information Mutt 1.5.17 (2007-11-01) Copyright (C) 1996-2007 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: FreeBSD 6.3-RC1 (i386) ncurses: ncurses 5.6.20061217 (compiled with 5.6) libiconv: 1.9 Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK -USE_INODESORT +USE_POP +USE_IMAP -USE_SMTP +USE_GSS +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +COMPRESSED +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID -USE_HCACHE ISPELL=""/usr/local/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. vvv.quote patch-1.5.0.ats.date_conditional.1 dgc.deepif.1 vvv.initials rr.compressed --- Begin /home/deskpot/.mutt/muttrc set from=""vasily@korytov.pp.ru"" set envelope_from set use_from alternates (noc|abuse|moscowusers)@flexpro.ru set folder=""{korytov.pp.ru}"" set imap_user=""$from"" mailboxes =INBOX =INBOX.Root =INBOX.Announces =INBOX.Comments =INBOX.Junk set spoolfile=""=INBOX"" set mbox=""=INBOX"" set postponed=""=INBOX.Drafts"" set record=""=INBOX.Sent"" set allow_8bit set use_8bitmime set send_charset=""us-ascii:koi8-r:utf-8"" charset-hook windows-1251 cp1251 charset-hook us-ascii utf-8 unset crypt_autosign unset crypt_autoencrypt unset crypt_replysign unset crypt_replyencrypt unset crypt_replysignencrypted set crypt_verify_sig=""yes"" unset pgp_show_unusable set editor=""emacs -nw"" set edit_headers set fast_reply set mime_forward set include=""yes"" set abort_nosubject=""no"" set abort_unmodified=""yes"" set postpone=""ask-yes"" set reply_to=""yes"" set attribution=""On %d, %n wrote:"" set pager_index_lines=4 unset arrow_cursor set sort=""threads"" set sort_aux=""date-received"" set reply_regexp=""^(re([\[0-9\]+])*:[ \t]*|re([\[0-9\]+])*:[ \t]re([\[0-9\]+])*:[ \t])"" set tilde unset markers set pager_context=0 set pager_stop set quote_regexp=""^([a-z]+[|>}#]|[ \t]+[a-z]+[|>}#]|[|>}#]|[ \t]+[|>}#])+"" set print=""ask-no"" set move=""ask-yes"" set delete=""yes"" set mail_check=30 set timeout=30 set beep set beep_new unset mark_old unset wait_key unset help unset confirmappend ignore * # this means ""ignore all lines by default"" unignore From: Subject: To: Cc: Bcc: Date: unignore Mail-Followup-To: Followup-To: Reply-To: unignore User-Agent: X-Mailer: unhdr_order * # forget the previous settings hdr_order From: Reply-To: Subject: To: Cc: Bcc: Date: bind pager ""\Cv"" next-page bind pager ""\033v"" previous-page bind pager previous-page bind pager ""\177"" previous-page color normal white black color attachment green black color bold blue white color error red white color hdrdefault cyan black color indicator white red color markers red black color message white blue color quoted green black color quoted1 yellow black color quoted2 green black color quoted3 yellow black color signature red black color status white blue color tilde cyan black color tree red black color underline yellow white color header yellow black \ ""^(((Delivery|Resent)-)?Date|X-Received): *"" color header yellow black \ ""^(Organization|Subject): *"" color header green black \ ""^(From|(X-)?Sender|Return-Path): *"" color header green black \ ""^(Reply|Mail-Followup|Return-Receipt|Errors)-To: *"" color header green black \ ""^Resent-(From|Sender|Reply-To): *"" color header green black \ ""^(((Delivered|X-Comment|Apparently)-)?To|(B)?Cc): *"" color header green black \ ""^Resent-(To|Cc|Bcc): *"" color header red black \ ""^(Message-ID|Resent-Message-ID|References|In-Reply-To): *"" color body magenta black \ ""((ftp|http)://|(www|ftp).|(news|URL):)[-a-zA-Z_0-9./~?=&:]+"" color body magenta black \ ""mailto:[-a-zA-Z_0-9][-a-zA-Z_0-9./:]+@[-a-zA-Z_0-9.]+"" color body magenta black \ ""[-a-z_0-9][-a-z_0-9./:]+@[-a-z_0-9.]+"" set alias_file=""~/.mutt/aliases"" source ~/.mutt/aliases set certificate_file=""~/.mutt/certificates"" source ~/.mutt/pgp --- End /home/deskpot/.mutt/muttrc --- Begin /usr/local/etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb ""~b "" ""search in message bodies"" macro index,pager \cb "" urlview"" ""call urlview to extract URLs out of a message"" macro attach,compose \cb "" urlview"" ""call urlview to extract URLs out of a message"" macro generic,pager "" less /usr/local/share/doc/mutt/manual.txt"" ""show Mutt documentation"" macro index,pager y ""?"" ""show incoming mailboxes list"" bind browser y exit attachments +A */.* attachments -A text/x-vcard application/pgp.* attachments -A application/x-pkcs7-.* attachments +I text/plain attachments -A message/external-body attachments -I message/external-body --- End /usr/local/etc/Muttrc }}}" vasily@… 3045 mutt-1.5.17: limiting by body pattern without gpg-agent asks for passphrase over and over again mutt defect mutt-dev infoneeded_new 2008-04-11T22:23:31-07:00 2011-04-13T04:29:08-07:00 " {{{ Package: mutt Version: 1.5.17 Severity: normal -- Please type your report below this line When trying to limit a folder that contains GPG-encrypted mail to myself with a body-pattern, such as ~Bfoo, mutt keeps asking for the GnuPG passphrase over and over again, so that ~B gets sort of unuseful for me. I am not using the gpg-agent (which gives me sorts of different problems). -- System Information System Version: Linux merlin 2.6.18.8-0.9-default #1 SMP Sun Feb 10 22:48:05 UTC 2008 i686 athlon i386 GNU/Linux SuSE Release: openSUSE 10.2 (i586) -- 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 Using built-in specs. Target: i586-suse-linux Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.1.2 --enable-ssp --disable-libssp --disable-libgcj --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit --enable-libstdcxx-allocator=new --program-suffix=-4.1 --enable-version-specific-runtime-libs --without-system-libunwind --with-cpu=generic --host=i586-suse-linux Thread model: posix gcc version 4.1.2 20061115 (prerelease) (SUSE Linux) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.17 (2008-03-09) Copyright (C) 1996-2008 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.6.18.8-0.9-default (i686) ncurses: ncurses 5.5.20060513 (compiled with 5.5) libidn: 0.6.8 (compiled with 0.1.14) hcache backend: qdbm 1.8.75 Compile options: -DOMAIN +DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP -USE_SMTP +USE_GSS +USE_SSL_OPENSSL -USE_SSL_GNUTLS +USE_SASL +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. patch-1.5.14.tamo.pgp_charsethack.1 }}}" m-a 3046 Bug mangling mbox files on 1.4.2.3 mutt 1.4 defect mutt-dev new 2008-04-14T15:17:39-07:00 2008-07-18T14:54:06-07:00 "I just tickled a bug in mutt 1.4.2.3, but unfortunately I'm not entirely sure how. It involved copying a message to, then linking a thread (using the edit-threads patch) in an mbox file under a softlink which has a folder hook attached to it, then saving and leaving mutt. The end result is that a number of messages get mangled in the following two ways: * The 12th character (starting from 1) of the line starting with ""From "" got replaced with a newline, like (using a diff-like format): {{{ -From email@address.tld Mon Apr 14 23:20:10 2008 +From email@ +ddress.tld Mon Apr 14 23:20:10 2008 }}} The place where it happens appears to be exactly at the 12th character and is not dependent on the actual content of the line. * The start of the body got mangled, like this: {{{ - ---fXStkuK2IQBfcDe+ +QBfcDe+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline }}} Or {{{ -This is a multi-part message in MIME format. +lti-part message in MIME format. }}} Most by far messages in that mbox contain attachments and I haven't spotted mangling of other messages (yet), but I cannot vouch for that not having happened, as this information was gathered after mbox reconstruction; the unmangled version was no longer available. The hook and the macro provided for completeness, I don't know if they have anything to do with it: {{{ macro index @@m_markings ""~F^M!*~d<2w!~v^M*"" folder-hook =mangledmbox push @@m_markings }}} And my version of mutt: {{{ Mutt 1.4.2.3i (2007-05-26) Copyright (C) 1996-2002 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: FreeBSD 6.2-RELEASE-p5 (i386) [using ncurses 5.2] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK +USE_POP +USE_IMAP +IMAP_EDIT_THREADS +USE_GSS +USE_SSL -USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +COMPRESSED +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 SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.4.2.dw.pgp-menu-traditional.2-fix 1.3.28.nr.threadcomplete 1.4.2.3-jpd.pgp-shorten-more patch-1.4.0.cd.edit_threads.9.5 pgp_shorten-1.3.27-sec-1 patch-1.3.23.bj.current_shortcut.1 vvv.initials rr.compressed }}} I can provide the precise patches as applied to stock 1.4.2.3 source, of course." cypherpunk 3070 Bug#482883: mutt: removes Mail-Followup-To header on postpone+resume (fwd) mutt 1.5.20 defect kevin8t8 assigned 2008-06-07T15:46:41-07:00 2013-04-22T13:44:46-07:00 " {{{ Mutt drops a manually added M-F-T header on postpone/resume, confirmed here for 1.5.18: ----- Forwarded message from Bas Wijnen ----- Date: Sun, 25 May 2008 20:08:01 +0200 From: Bas Wijnen Reply-To: Bas Wijnen , 482883@bugs.debian.org To: submit@bugs.debian.org Subject: Bug#482883: mutt: removes custom headers on postpone+resume Package: mutt Version: 1.5.17+20080114-1 Severity: minor When composing a message with edit_headers=yes, adding a custom header (such as Mail-Followup-To:) and postponing, then this header is nicely sent with the message. However, if the message is postponed and then resumed, it is not shown anymore. When the message is then sent, it is indeed not present. Thanks, Bas ----- End forwarded message ----- }}}" myon 3082 current input not preserved in history when cycling mutt defect kevin8t8 assigned 2008-06-23T06:54:43-07:00 2013-04-27T15:43:43-07:00 "The up/down keys allow you to use previously used subject lines (and other lines, too). But if you have started to write a new one and then press up (or down), your current line is lost. It would be better that mutt would remember the current line and one could return to it with the same number of ups and downs." Ulrich 3083 tag-prefix save lets you save files under specified directory and a new name - but not first file mutt defect mutt-dev new 2008-06-23T06:57:55-07:00 2008-06-23T06:57:55-07:00 tag-prefix save (with a directory as argument) always saves the first file under the name specified in the email. The names of all subsequent files can be changed. Ulrich 3188 mutt-1.5.18: Brightness problem with ncurses display defect mutt-dev new 2009-02-10T05:09:50-08:00 2009-06-30T07:16:59-07:00 " {{{ Package: mutt Version: 1.5.18 Severity: normal -- Please type your report below this line All foreground colors are bright if normal foreground color is brigth. The following configuration displays right colors (cyan body text and brightcyan header): color normal cyan blue color hdrdefault brightcyan blue The following configuration displays wrong colors: (brightcyan body and brightcyan header): color normal brightcyan blue color hdrdefault cyan blue -- System Information System Version: FreeBSD zeus.colocall.net 7.1-RELEASE FreeBSD 7.1-RELEASE #9: Wed Jan 7 13:41:08 EET 2009 root@zeus.colocall.net:/usr/obj/usr/src/sys/zeus i386 -- 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 cc -I/usr/local/include Using built-in specs. Target: i386-undermydesk-freebsd Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 4.2.1 20070719 [FreeBSD] - CFLAGS -O2 -fno-strict-aliasing -pipe -- Mutt Version Information Mutt 1.5.18 (2008-05-17) Copyright (C) 1996-2008 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: FreeBSD 7.1-RELEASE (i386) ncurses: ncurses 5.6.20080503 (compiled with 5.6) libiconv: 1.11 hcache backend: Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003) Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK +USE_POP +USE_NNTP +USE_IMAP +USE_SMTP +USE_GSS +USE_SSL_OPENSSL -USE_SSL_GNUTLS +USE_SASL +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +COMPRESSED +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE ISPELL=""/usr/local/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. vvv.quote patch-1.5.0.ats.date_conditional.1 dgc.deepif.1 vvv.initials vvv.nntp rr.compressed }}}" vvv@… 3201 mutt-1.5.16: Saving attachments within mutt doesn't work well with POSIX ACLs. mutt defect mutt-dev new 2009-03-11T01:01:40-07:00 2009-03-11T01:01:40-07:00 " {{{ Package: mutt Version: 1.5.16 Severity: normal -- Please type your report below this line When saving an attachment from within mutt into a directory that has a default ACL, the effective permissions don't take effect. I think this is a problem with mutt as other utilities (e.g., 'touch') take on the proper effective permissions. Here's an example... Below is the output of getfacl on the directory with a default ACL, and two test files. One of the test files was an attachment saved from within mutt, the other was created with touch. Both operations were done from within the directory possessing the default ACL. *** DIRECTORY *** # file: . # owner: jcdenton # group: jcdenton user::rwx user:apache:--x group::--- mask::--x other::--- default:user::rwx default:user:apache:r-x default:group::--- default:mask::r-x default:other::--- *** CREATED BY 'touch' *** # file: test.html # owner: jcdenton # group: jcdenton user::rw- user:apache:r-x #effective:r-- group::--- mask::r-- other::--- *** CREATED BY 'mutt' *** # file: test2.html # owner: jcdenton # group: jcdenton user::rw- user:apache:r-x #effective:--- group::--- mask::--- other::--- Notice how the file created by mutt lacks effective read permission. Any help you can provide would be greatly appreciated! Thanks. -- System Information System Version: Linux masterchief 2.6.18-xen #1 SMP Tue Feb 12 06:40:50 UTC 2008 x86_64 Dual-Core AMD Opteron(tm) Processor 2212 AuthenticAMD GNU/Linux -- 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 x86_64-pc-linux-gnu-gcc Using built-in specs. Target: x86_64-pc-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-4.1.2/work/gcc-4.1.2/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.2 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.2 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.2/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.2/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/include/g++-v4 --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --enable-secureplt --enable-multilib --enable-libmudflap --disable-libssp --disable-libgcj --enable-languages=c,c++,treelang,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu Thread model: posix gcc version 4.1.2 (Gentoo 4.1.2 p1.1) - CFLAGS -Wall -pedantic -O2 -pipe -- Mutt Version Information Mutt 1.5.16 (2007-06-09) Copyright (C) 1996-2007 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.6.18-xen (x86_64) ncurses: ncurses 5.6.20061217 (compiled with 5.6) Compile options: -DOMAIN -DEBUG +HOMESPOOL -USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK -USE_INODESORT -USE_POP -USE_IMAP -USE_SMTP -USE_GSS -USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -HAVE_GETADDRINFO -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP -CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""Maildir"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc/mutt"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. patch-1.5.6.dw.pgp-timeout.1 patch-1.5.6.dw.mbox-hook.1 patch-1.5.16.rr.compressed.1 patch-1.5.4.lpr.collapse_flagged Lukas P. Ruf --- Begin /etc/mutt/Muttrc set mbox_type=Maildir set folder=~/.maildir set spoolfile=~/.maildir/ set record=~/.maildir-sent/ set move=no set index_format=""%4C %Z %{%b %d} %-16.16L %s"" --- End /etc/mutt/Muttrc }}}" matt+bugzilla@… 3298 Mutt's way to get the FQDN is broken mutt 1.5.20 defect mutt-dev reopened 2009-07-20T11:05:05-07:00 2013-04-15T03:32:48-07:00 "It seems that Mutt gets the FQDN by reading /etc/resolv.conf, but this is incorrect when this file doesn't have the precedence (see /etc/nsswitch.conf). The consequence is that incorrect Message-Id's are generated. (There seems to be some problems with the BTS, that's why I submit another bug.)" vinc17 3305 Attachment truncated if mime-type is multipart/related mutt 1.5.18 defect mutt-dev new 2009-07-22T18:16:29-07:00 2009-07-22T18:16:29-07:00 "If I try to attach a file with mime-type {{{ multipart/related; type=""text/html""; boundary=whatever }}} Mutt throws away whatever is in the file and replaces it with a single line of the form {{{ --whatever-- }}} To make this worse, the display continues to indicate the original size of the attachment until after I send the message, leaving recipients with a useless mail. A debug trace (mutt -d 5) seemed to produce nothing useful. ---- Steps to reproduce: 1. Outside Mutt, create a file with a mime type of ""multipart/related; type=""text/html""; boundary=whatever"". Microsoft calls such files "".mhtml"" files, on UNIX they can be made using tools such as mime-construct. I have attached a sample file to make testing easier. 2. In mutt, use the m command to start a new message, type in a test recipient, a sample subject, and a non-empty body. 3. On the send screen, press a to attach the file from step 1. 4. Press Ctrl-T and change the mime-type to ""multipart/related; type=""text/html""; boundary=galadriel"" just as indicated in the header of the .mhtml file. 5. Notice that the send screen correctly displays the file size and mime-type as if everything is OK 6. Press y to send the mail 7. Look in the sent or received mail, and notice that the content of the .mhtml attachment has been silently replaced by a single line consisting of two dashes, the inner boundary string and two more dashes. ---- Mutt version 1.5.18 (2008-05-17) Debian GNU/Linux 5.0 (lenny) package mutt 1.5.18-6 Linux 2.6.17 i586/133 MHz " jbohm_dk 3306 """bind generic"" does not work for keys that have default bindings" mutt defect mutt-dev new 2009-07-25T00:27:37-07:00 2009-07-25T00:29:49-07:00 "For instance, bind generic $ last-entry is accepted but $ does not do last-entry in the index menu, because of its default binding to sync-mailbox. This makes the generic menu quite useless. Because they are not controlled by the user and cannot be unbound (and some may change / be added in future versions), the default bindings should have a lower precedence. Alternatively, there should be a way to unbind everything in one command. Related bugs: #1880 and #2575 (but note that requiring the user to explicitly unbind some key for each menu before using ""bind generic"" because of a possible default binding would be unacceptable)." vinc17 3313 mutt not remembering that there's a postponed message mutt defect mutt-dev new 2009-08-11T09:41:42-07:00 2009-08-11T09:41:42-07:00 "Mutt from tip, from Aug. 10 I think. I've noticed for the last couple of weeks the following behavior: 1. I postpone a message, and it's saved to my Drafts folder (this is on IMAP). 2. I browse through the index view a bit. 3. I hit 'm' to compose a new message. 4. At this point mutt is supposed to ask me if I want to continue my postponed message. I have the relevant setting in my muttrc. But mutt doesn't ask me this, and instead asks for the ""To:"" of a brand new message. 5. I hit Ctrl-G, because I don't want to make a new message. 6. I hit 'm' again, and this time mutt does ask if I want to continue my postponed message. From here on, everything is normal. This only seems to happen when I postpone and then try to continue it later in that same mutt session. If I postpone, quit, and then later try to continue, everything works fine." balderdash 3318 Attachments not shown if mail is pgp/mime encrypted mutt 1.5.20 defect mutt-dev new 2009-08-25T01:21:55-07:00 2010-01-09T05:03:51-08:00 "Since using Version 1.5.20 on Arch Linux (1.5.18 was ok), i can't see attachments if the message is pgp/mime encrypted. i can use the mailcap file to show them inline. to complicate this, test mails send with mutt to myself worked without a problem. a typical output looks like this, here we have an rtf-file attached. {{{ [-- Attachment #1 --] [-- Type: multipart/encrypted, Encoding: 7bit, Size: 29K --] [-- PGP output follows (current time: Tue 25 Aug 2009 12:00:49 AM CEST) --] [-- End of PGP output --] [-- The following data is PGP/MIME encrypted --] [-- Attachment #1 --] [-- Type: text/plain, Encoding: quoted-printable, Size: 0.1K --] some text [-- Attachment #2: text.rtf --] [-- Type: application/rtf, Encoding: base64, Size: 75K -- [-- Autoview using unrtf --text '/tmp/text.rtf' --] [the rtf-file shown inline] }}} If i press 'v', i.e. to save the attachment, i only get this, with 1 being the the whole encrypted message, including all attachments: {{{ I 1 [multipa/encrypted, 7bit, 29K] I 2 [text/plain, quoted, iso-8859-1, 0.1K] }}} The gpg.rc is the one provided with the mutt package. My .mailcap: {{{ text/html; elinks -dump %s; nametemplate=%s.html; copiousoutput application/msword; antiword %s; copiousoutput text/rtf; unrtf --text %s; copiousoutput application/rtf; unrtf --text %s; copiousoutput image/*; feh %s > /dev/null; application/pdf; evince %s; }}} mutt -v: {{{ Mutt 1.5.20 (2009-06-14) Copyright (C) 1996-2009 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.6.30-ARCH (i686) slang: 20104 hcache backend: GDBM version 1.8.3. 10/15/2002 (built May 10 2009 07:54:56) Compile options: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS +USE_SASL -USE_GSS +HAVE_GETADDRINFO -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR -HAVE_START_COLOR -HAVE_TYPEAHEAD -HAVE_BKGDSET -HAVE_CURS_SET -HAVE_META -HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER }}} " tannhauser 3320 alias in the from field does not get expanded in mutt 1.5.20 mutt defect mutt-dev new 2009-08-27T20:09:47-07:00 2009-08-27T20:09:47-07:00 "when I do a ""set from=ALIAS"" where ALIAS is a valid alias, all outgoing emails have the sting ""ALIAS"" in the from field instead of the address that corresponds to this particular alias. This used to work fine in 1.5.16." redneb 3333 """no mailbox"" impossible to leave -- changeset 6020" mutt defect mutt-dev new 2009-09-10T15:38:11-07:00 2009-09-10T15:40:27-07:00 "Anders Helmersson wrote: If I end up with ""no mailbox"", it seems impossible to change it into another by ""c"" (change-folder) since the error messages "" is not a mailbox"" followed by ""No mailbox is opened"". In that case I have to exit mutt and start all over. This happens when I try to open a mailbox with an erroneous password. The problem was introduced by {{{ changeset: 6020:e67f4c347bb4 branch: HEAD user: Rocco Rutte date: Mon Aug 17 16:58:21 2009 +0200 summary: Require already opened folder when using templates for change-folder. $ hg diff -r 6019 -r 6020 diff --git a/curs_main.c b/curs_main.c --- a/curs_main.c +++ b/curs_main.c @@ -1082,7 +1082,7 @@ break; } } - else + else if (Context && Context->path) { mutt_buffy (buf, sizeof (buf)); }}} " agriffis 3337 [Bcc header showing] Mutt + Exim mutt 1.5.18 defect mutt-dev new 2009-09-21T02:54:25-07:00 2012-02-09T13:46:39-08:00 "Hi, I got stung by the following mutt+exim issue recently: http://sysmonblog.co.uk/2009/04/mutt-exim4-debian-unbuntu-and-bcc-fail-fix-included.html which starts: ""Take a default Ubuntu/Debian install using the Mutt mail client (MUA) then switch to exim4. You get the most monumental FAIL - your bcc addresses will be included in the message to everyone else. Dangerous and embarrassing! ..."" This page does offer a workaround, but I think this is really a bug in mutt that should be fixed. I cannot see why the Bcc information should EVER go out to all recipients. I have spoken to the original designer of Exim, Philip Hazel, who is now retired, about this and he tells me the following, i.e. it is a mutt bug. ""Exim will only remove Bcc headers when it is being used as a message *submission* agent, that is, if the -t (I think it is) option is used to ask it to take recipients from header lines. In all other cases, when Exim is a transport agent, it doesn't mess with headers. This has been argued before to be the correct approach. So, if mutt is calling Exim, not using -t, and expecting it to remove headers, it is mutt's problem."" Given I want mutt to save sent emails with the Bcc information but not send out the Bcc information to all recipients, I think that this is a mutt bug. (i.e. write_bcc=no is not the answer here.) I am using the sendmail -t and exim workaround mentioned in the URL above for now, but when I next upgrade I might forget to apply this workaround so I'll like mutt to be fixed, if you agree. Thanks in advance. " will177 3338 mutt unable to download and read header_cache from gmail if the number of headers is large. mutt 1.5.20 defect mutt-dev new 2009-09-22T02:54:43-07:00 2009-11-05T03:04:42-08:00 "mutt is unable to handle errors returned from gmail while downloading large number of headers. Full details of the bug are present in the following below thread. http://www.mail-archive.com/mutt-dev@mutt.org/msg06018.html" mkatiyar 3339 S/MIME Certificate Import Failures mutt 1.5.20 defect mutt-dev new 2009-09-22T16:19:04-07:00 2009-09-22T16:19:04-07:00 "When importing a certificate/signature chain included in an email from a Thunderbird user I was prompted for a label for the certificate, but later I wasn't able to lookup the user's certificate within mutt. After digging around, I saw that the 'smime_keys list' command also didn't show the certificate with the label I gave it. I googled around and found this page: http://kb.wisc.edu/middleware/page.php?id=4091 I applied his smime_keys patch and it fixed my problem. It looks like it might properly traverse a certificate chain, rather than just pulling the first one. However, I have not looked closely at how the import is done, so I'm not 100% sure he's implicitly trusting things in a dangerous way. Please review the changes and apply if it's safe. I'm running the stock 1.5.20 on Debian unstable right now. " adian 3340 Sending batch-mode SMTP messages cores if .mutt_certificates is missing or empty mutt 1.5.20 defect mutt-dev new 2009-09-23T07:48:24-07:00 2009-09-23T07:48:24-07:00 "While trying to send a message from the command-line via gmail, I found that mutt would dump core every time. I eventually discovered that it stopped crashing if my .mutt_certificates file was present and non-empty. I have attached a core file produced by a non-stripped executable. Here is the output of mutt -v: Mutt 1.5.20 (2009-06-14, Gentoo 1.5.20-r4) Copyright (C) 1996-2009 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.6.27-gentoo-r8 (x86_64) ncurses: ncurses 5.6.20061217 (compiled with 5.6) hcache backend: GDBM version 1.8.3. 10/15/2002 (built Aug 4 2007 02:04:35) Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK +USE_POP +USE_IMAP +USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS +USE_SASL -USE_GSS +HAVE_GETADDRINFO -HAVE_REGCOMP +USE_GNU_REGEX +COMPRESSED +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/spool/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc/mutt"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. dgc.subjrx fg.smarttime vvv.initials vvv.quote patch-1.5.6.dw.mbox-hook.1 rr.compressed patch-1.5.4.lpr.collapse_flagged Lukas P. Ruf " ewfalor 3342 mutt should use the Sender: header for evenlope from (for both sendmail and smtp) mutt defect mutt-dev new 2009-09-27T17:03:58-07:00 2009-10-21T14:33:10-07:00 "When mutt sends an e-mail (with use_envelope_from set in case of sendmail) it should use the contents of the `Sender:`, when available, before the `From:` header to construct the sender envelope. E.g. when a message is given with these headers: {{{ From: John Doe Sender: Michael Jones ... }}} This should be used for the envelope (or equivalent `-f` option for sendmail): {{{ MAIL FROM: }}} Currently, however, the code only looks for the contents of the `From:` header. Attached patch changes this by making sure the `Sender:` header is tried first, falling back to `From:` when failing that. Some people might dislike use of the ternary operator though. Please let me know if you'd rather see an explicit if-statement." Giel 3343 unset write_bcc removes BCC header in sent folder copy mutt 1.5.20 defect mutt-dev new 2009-10-15T20:08:01-07:00 2009-10-22T09:15:04-07:00 When write_bcc is not set, mutt also removes the BCC header from the mail it stores in the sent folder. Most definitely not what a user wants. chaoflow 3345 Mutt fails during SSL certificate checks mutt 1.5.20 defect mutt-dev new 2009-10-21T09:32:52-07:00 2010-08-24T10:10:48-07:00 "I have trouble with Mutt 1.5.20 (2009-06-14) where the SSL certificate check and save does not function properly. This is on CentOS 5.3. What happens is the SSL cert (self-generated) is saved to .mutt_certificates and subsequent actions continue to save/append the certificate to the file. In either case, I'm constantly asked whether I want to save the certificate. I've posted on Google before and there seems to be a few other people who experience this. Others don't. Previously, I had this on a FreeBSD-7.x system. On CentOS 5.3, a fresh and updated install, I have the same problem. I have not yet checked out and compiled the latest development code - I will be happy to, if this bug has been addressed. " forrie 3346 non-ASCII character in Subject not correctly handled with $edit_headers under UTF-8 locales mutt defect mutt-dev new 2009-10-21T16:02:46-07:00 2010-06-21T01:00:15-07:00 "Under UTF-8 locales and with $edit_headers set, when I reply to some mail (see attached mailbox, which contains 1 message to reply to) with an accented character in the Subject, the character gets corrupt when I quit the editor. This can be seen in the compose menu and when one edit the message again (Mutt sends a file with an invalid UTF-8 sequence to the editor). This bug does not occur when the non-ASCII character occurs early enough in the Subject header. I wonder whether this problem is related to header folding. The bug doesn't occur under ISO-8859-1 locales. I can always reproduce it with Mutt 1.5.20-6026 under Mac OS X 10.4.11, but not under Linux." vinc17 3347 pgpewrap compilation depends on optimization turned on mutt defect mutt-dev new 2009-10-22T02:02:15-07:00 2010-01-15T14:01:51-08:00 "The situation observed on (Open)Solaris when compiled mutt-1.5.20 with SunStudio cc with not enough optimization turned on: If the target platform does not have its own wcscasecmp() implementation the mutt's wcscasecmp.c is compiled as a replacement. The wcscasecmp.c indirectly includes ascii.h (via mutt.h). The ascii.h contains static inline ascii_strlower() implementation. The ascii_strlower() calls ascii_tolower(). If there is no optimization used in a C compiler, the wcscasecmp.o compiled contains also ascii_strlower() implementation referring to the ascii_tolower symbol. The pgpewrap compilation/linking rules does not contain ascii.o (where the ascii_tolower symbol is implemented) to be linked into pgpewrap. This makes the pgpewrap compilation/linking failed missing the ascii_tolower symbol." marcel 3351 Mails sent via mutt's batch mode don't end up in $record mutt 1.5.20 defect mutt-dev new 2009-11-12T20:40:28-08:00 2009-11-12T20:59:21-08:00 "In an effort to work around bug #3323 by properly creating the mails through mutt, I looked at mutt's batch mode. However, mails sent via mutt's batch mode, either using ""mutt -s 'subject' recipient@example.org < body"" or using ""mutt -H mail-with-headers < /dev/null"", also do not end up in $record." josh 3357 imap server socket communication trouble IMAP defect brendan new 2009-11-23T07:43:52-08:00 2009-12-17T10:47:28-08:00 "In some sense, this is a continuation of ticket 3000. Open an INBOX containing 230,000 messages, tag 9,000 messages, and tag copy them to a new mailbox on a cyrus imap server (translates to an empty directory). What ends up happening is that that directory gets filled with multiple copies of the messages, each having the same inode number but different filenames. So where are these multiple copies coming from? Mutt sends multiple UID COPY commands so as not to overflow the command buffer (ie is kind to cyrus) The last line in the block is: {{{ a0232 UID COPY 326160:326161,326188,326202,326225,326237:326243,326251,326266,326277,326336,326362,326380:326381,326393,326400,326411,326422,326447,326522,326545,326677:326680,326686,326701:326704,326714,326718:326719,326758,326775,326799,326857:326865,326868,326906,326961:326963,326974,326996,327020,327081,327119,327129,327135,327147,327160,327184:327187,327225:327227,327233:327241,327251,327263,327341:327342,327388,327406,327446,327560,327585,327598:327601,327789:327792,327800,327820:327821,327960,328011,328053:328054,328091:328092,328102,328114:328123,328131,328147,328150,328221,328229,328232,328256,328302:328305,328307:328312,328321:328322,328341,328387,328393,328416,328443,328488,328522,328581:328600,328607:328615,328719,328770,328868,328870,328873:328875,328908:328914,328925:328927,328950:328951,328972:328975,329049:329055,329079:329084,329132:329150,329152,329158,329178,329212:329217,329232,329234,329238:329241,329248:329251,329260,329270,329297,329307:329308,329310:329323,329325:329328,329337:329338,329343:329347 ""http""^M [2009-11-12 18:56:28] mutt_socket_write: short write (4091 of 16720 bytes) [2009-11-12 18:56:28] mutt_socket_write: short write (4091 of 12629 bytes) [2009-11-12 18:56:28] mutt_socket_write: short write (4091 of 8538 bytes) [2009-11-12 18:56:28] mutt_socket_write: short write (4091 of 4447 bytes) }}} What is mystifying is the later OK which mutt records as coming from cyrus: {{{ [2009-11-12 18:56:39] 4< a0232 OK [COPYUID 1258034308 171084,171095,171120,171125,171199,171211,171291,171320,171328,171394,171396,326160:326161,326188,326202,326225,326237,326243,326251,326266,326277,326336,326362,326380:326381,326393,326400,326411,326422,326447,326522,326545,326677,326680,326686,326701,326704,326714,326718:326719,326758,326775,326799,326857,326863,326865,326868,326906,326961,326963,326974,326996,327020,327081,327119,327129,327135,327147,327160,327184,327187,327225,327227,327233,327236,327239,327241,327251,327263,327341:327342,327388,327406,327446,327560,327585,327598,327601,327789,327791:327792,327800,327820:327821,327960,328011,328053:328054,328091:328092,328102,328114,328123,328131,328147,328150,328221,328229,328232 2363:2461] Completed }}} Where did ID 171084 suddenly spring from? It's hard to work out which end is having the problem, but I also wonder what imap/command.c:cmd_start() is meant to do with the length return value of mutt_socket_write_d() This was either Mutt 1.5.20 (2009-08-27) or Mutt 1.5.20 (2009-10-28) " prlw1 3359 mutt-1.5.20: segfault when entering an imap folder using db4 and hcache mutt defect mutt-dev new 2009-12-07T02:10:07-08:00 2010-04-11T19:53:55-07:00 " {{{ Package: mutt Version: 1.5.20 Severity: important -- Please type your report below this line Works OK until I enter an imap folder: logs in OK, but when going to read the message headers, dumps a core. Seems db4 related.... -- System Information System Version: NetBSD droog 5.0.1_PATCH NetBSD 5.0.1_PATCH (sdf) #1: Wed Nov 18 17:52:24 UTC 2009 root@droog:/var/netbsd/sys/arch/alpha/compile/sdf alpha -- 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 cc Using built-in specs. Target: alpha--netbsd Configured with: /usr/src/tools/gcc/../../gnu/dist/gcc4/configure --enable-long-long --disable-multilib --enable-threads --disable-symvers --build=x86_64-unknown-netbsd4.99.72 --host=alpha--netbsd --target=alpha--netbsd --enable-__cxa_atexit Thread model: posix gcc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) - CFLAGS -Wall -pedantic -Wno-long-long -O2 -mieee -DHAVE_WCHAR=1 -I/usr/include -I/usr/pkg/include/db4 -- Mutt Version Information Mutt 1.5.20 (2009-06-14) Copyright (C) 1996-2009 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: NetBSD 5.0.1_PATCH (alpha) hcache backend: Berkeley DB 4.7.25: (May 15, 2008) Compile options: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP -USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR -HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE ISPELL=""/usr/pkg/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/pkg/share/mutt"" SYSCONFDIR=""/usr/pkg/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. --- Begin /usr/pkg/etc/Muttrc ignore * unignore from: subject to cc date x-mailer x-url user-agent hdr_order date from to cc subject macro index \eb ""~b "" ""search in message bodies"" macro index,pager,attach,compose \cb ""\ set my_pipe_decode=\$pipe_decode pipe_decode\ urlview\ set pipe_decode=\$my_pipe_decode; unset my_pipe_decode"" \ ""call urlview to extract URLs out of a message"" macro generic,pager "" less /usr/pkg/share/doc/mutt/manual.txt"" ""show Mutt documentation"" macro index,pager y ""?"" ""show incoming mailboxes list"" bind browser y exit set hostname=SDF-EU.ORG mime_lookup application/octet-stream attachments +A */.* attachments -A text/x-vcard application/pgp.* attachments -A application/x-pkcs7-.* attachments +I text/plain attachments -A message/external-body attachments -I message/external-body --- End /usr/pkg/etc/Muttrc }}}" Pedro Fortuny 3366 mutt-1.5.20: message-hooks and alternative_order don't seem to get along mutt defect mutt-dev new 2010-01-10T18:15:19-08:00 2010-01-10T18:42:32-08:00 " {{{ Package: mutt Version: 1.5.20 Severity: normal -- Please type your report below this line The following two .muttrc lines do not work, regardless of order: message-hook '~f order@dominos' 'alternative_order text/html text/plain' message-hook ~A 'alternative_order text/plain text/html' -- System Information System Version: Linux warhead 2.6.30-gentoo-r6-warhead #1 SMP Tue Sep 8 22:48:44 EDT 2009 i686 Intel(R) Core(TM)2 CPU E7400 @ 2.80GHz GenuineIntel GNU/Linux -- 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 i686-pc-linux-gnu-gcc Using built-in specs. Target: i686-pc-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-4.3.4/work/gcc-4.3.4/configure --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/4.3.4 --includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.3.4/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.3.4 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.3.4/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.3.4/info --with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.3.4/include/g++-v4 --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec --disable-fixed-point --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --enable-secureplt --disable-multilib --enable-libmudflap --disable-libssp --enable-libgomp --disable-libgcj --with-arch=i686 --enable-languages=c,c++,treelang,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.3.4 p1.0, pie-10.1.5' Thread model: posix gcc version 4.3.4 (Gentoo 4.3.4 p1.0, pie-10.1.5) - CFLAGS -Wall -pedantic -Wno-long-long -O2 -march=nocona -pipe -- Mutt Version Information Mutt 1.5.20 (2009-06-14, Gentoo 1.5.20-r10) Copyright (C) 1996-2009 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.6.30-gentoo-r6-warhead (i686) ncurses: ncurses 5.7.20081102 (compiled with 5.7) hcache backend: GDBM version 1.8.3. 10/15/2002 (built Jan 1 2010 21:22:44) Compile options: -DOMAIN -DEBUG +HOMESPOOL -USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK -USE_POP -USE_IMAP -USE_SMTP -USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -USE_GSS -HAVE_GETADDRINFO -HAVE_REGCOMP +USE_GNU_REGEX +COMPRESSED +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP -CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""Maildir"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc/mutt"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. dgc.subjrx fg.smarttime vvv.initials vvv.quote patch-1.5.6.dw.mbox-hook.1 rr.compressed patch-1.5.4.lpr.collapse_flagged Lukas P. Ruf }}}" matt+bugzilla@… 3367 mutt-1.5.20hg: Cursor's shape is not preserved on a text console mutt defect mutt-dev new 2010-01-12T09:27:06-08:00 2010-01-12T10:10:37-08:00 " {{{ Package: mutt Version: 1.5.18-6 (Debian) Severity: normal The shape of the cursor is changed for the tcsh login shell with set cursor = '\033[?3c' echo ""$cursor"" After mutt finishes, the shape is the default one (like an underscore). -- 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 Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.2-1.1' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --enable-cld --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.3.2 (Debian 4.3.2-1.1) - CFLAGS -Wall -pedantic -Wno-long-long -g -O2 -- Mutt Version Information Mutt 1.5.20hg (2009-12-10) Copyright (C) 1996-2009 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.6.26ed (i586) ncurses: ncurses 5.7.20081213 (compiled with 5.7) Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP -USE_IMAP -USE_SMTP -USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -USE_GSS -HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID -USE_HCACHE ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. }}}" bjarniig@… 3369 Cannot send email after resume in different network mutt 1.5.20 defect mutt-dev new 2010-01-14T07:05:01-08:00 2010-08-30T04:22:06-07:00 "All done with mutt Mutt 1.5.20 (2009-12-10) (6035-1 in archlinux) 1. Open mutt, send email (have smtp_url and smtp_pass set) 2. email sends OK 3. hibernate notebook to memory (leave mutt open) 4. resume the operation, connect to *different* network 5. try to send email 6. the smtp_url host cannot be resolved" kolcon 3387 Mutt assumes that IMAP password and SSL client certificate password (if set) are the same mutt 1.5.20 defect mutt-dev new 2010-02-26T09:50:22-08:00 2010-03-10T08:47:53-08:00 "For accessing my IMAP account, I need to authenticate via an SSL client certificate and, additionally, a password set for the IMAP account. Mutt (with OpenSSL binding) can only handle this if the certificate file is not password protected or is protected via the same password as the IMAP account. I expect mutt to handle both passwords separately. A debugging session has revealed that the password callback ssl_passwd_cb() in mutt_ssl.c calls mutt_account_getpass(account). mutt_account_getpass determines that the account is of type IMAP and returns the IMAP password. However, it would need to return the password for the SSL client certificate." timow 3390 chdir dialog is nearly useless (and crashes mutt) user interface 1.5.18 defect mutt-dev new 2010-03-08T02:52:11-08:00 2010-03-17T20:47:58-07:00 "Hi there, I have severe problems when trying to work with deep directory structures. Main problem is when saving attachments. I can hardly navigate to a specfic directory from within mutt: 1.) Whats the point of the chdir dialog? v (view attachment) s (save to file) starting to enter directory name use tab twice to open chdir dialog i can navigate directorys y goes back to the point where i pressed tab twice when trying to make a bugreport for this i found something even worse: 2.) I can crash mutt with chdir dialog v (view attachment) s (save to file) starting to enter directory name use tab twice to open chdir dialog navigate to a directory c (shows current directory) enter (dialog line disappears) enter (screen goes blank) enter (segfault) debian lenny i386 mutt-patched 1.5.18-6" qwqwqw 3392 Whitespace garbage in pager mode user interface 1.5.20 defect mutt-dev new 2010-03-12T02:49:16-08:00 2012-12-26T20:45:27-08:00 "Situation: mutt compiled with slang, running on OpenSolaris. When I switch from the index mode to pager mode in most cases the background is printed using spaces. It means that lines does not terminates with ""\n"", but they are full of spaces till end of the terminal line. When I use gnome-terminal with mutt and I want to copy and paste a message text (several lines) using mouse, I'll get all lines with additional spaces on the line ends. It seems the mutt_pager() function does not clear the screen before displayed leaving the screen full of spaces. As a workaround I found that the simple additional clearok(stdscr,TRUE); call in mutt_pager() fixes the issue for me. I am not sure whether this fix is correct or not, but in my case it works. For reference: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6796795" marcel 3398 mutt 1.5.20 core dumps when trying to use smtp to send mail mutt 1.5.20 defect mutt-dev new 2010-03-30T14:06:59-07:00 2010-03-31T04:52:37-07:00 " I have installed mutt 1.5.20 on FreeBSD 8.0 as follows: [[BR]] Mutt 1.5.20 (2009-06-14)[[BR]] Copyright (C) 1996-2009 Michael R. Elkins and others.[[BR]] Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.[[BR]] Mutt is free software, and you are welcome to redistribute it[[BR]] under certain conditions; type `mutt -vv' for details.[[BR]] System: FreeBSD 8.0-RELEASE (i386)[[BR]] ncurses: ncurses 5.7.20081102 (compiled with 5.7)[[BR]] libiconv: 1.13[[BR]] libidn: 1.14 (compiled with 1.14)[[BR]] Compile options:[[BR]] -DOMAIN[[BR]] +DEBUG[[BR]] -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK[[BR]] -USE_POP +USE_IMAP +USE_SMTP [[BR]] -USE_SSL_OPENSSL -USE_SSL_GNUTLS +USE_SASL -USE_GSS [[BR]] +HAVE_GETADDRINFO [[BR]] +HAVE_REGCOMP -USE_GNU_REGEX [[BR]] +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET [[BR]] +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM [[BR]] +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME [[BR]] -EXACT_ADDRESS -SUN_ATTACHMENT [[BR]] +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET [[BR]] +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID -USE_HCACHE ISPELL=""/usr/local/bin/ispell""[[BR]] SENDMAIL=""/usr/sbin/sendmail""[[BR]] MAILPATH=""/var/mail""[[BR]] PKGDATADIR=""/usr/local/share/mutt""[[BR]] SYSCONFDIR=""/usr/local/etc""[[BR]] EXECSHELL=""/bin/sh""[[BR]] -MIXMASTER[[BR]] To contact the developers, please mail to .[[BR]] To report a bug, please visit http://bugs.mutt.org/.[[BR]] I have set up my .muttrc as follows:[[BR]] ...[[BR]] set mime_forward=yes[[BR]] set mail_check=90[[BR]] set timeout=15[[BR]] set imap_user=""mylogin""[[BR]] set imap_pass=mypassword[[BR]] set smtp_url=""smtp://mylogin@mymailhost.com:25/""[[BR]] set smtp_pass=""mypassword""[[BR]] set spoolfile=imap://mymailhost/INBOX[[BR]] set folder=imap://mylogin/[[BR]] The mailhost is an exchange server running smtp relay on port 25 only.[[BR]] Whenever I try to send email mutt core dumps as follows:[[BR]] $ gdb /usr/local/bin/mutt mutt.core[[BR]] GNU gdb 6.1.1 [FreeBSD][[BR]] Copyright 2004 Free Software Foundation, Inc.[[BR]] GDB is free software, covered by the GNU General Public License, and you are[[BR]] welcome to change it and/or distribute copies of it under certain conditions.[[BR]] Type ""show copying"" to see the conditions.[[BR]] There is absolutely no warranty for GDB. Type ""show warranty"" for details.[[BR]] This GDB was configured as ""i386-marcel-freebsd""...[[BR]] Core was generated by `mutt'.[[BR]] Program terminated with signal 11, Segmentation fault.[[BR]] Reading symbols from /lib/libncursesw.so.8...done.[[BR]] Loaded symbols for /lib/libncursesw.so.8[[BR]] Reading symbols from /usr/local/lib/libsasl2.so.2...done.[[BR]] Loaded symbols for /usr/local/lib/libsasl2.so.2[[BR]] Reading symbols from /usr/local/lib/libintl.so.8...done.[[BR]] Loaded symbols for /usr/local/lib/libintl.so.8[[BR]] Reading symbols from /usr/local/lib/libiconv.so.3...done.[[BR]] Loaded symbols for /usr/local/lib/libiconv.so.3[[BR]] Reading symbols from /usr/local/lib/libidn.so.16...done.[[BR]] Loaded symbols for /usr/local/lib/libidn.so.16[[BR]] Reading symbols from /lib/libc.so.7...done.[[BR]] Loaded symbols for /lib/libc.so.7[[BR]] Reading symbols from /usr/local/lib/sasl2/libanonymous.so.2...done.[[BR]] Loaded symbols for /usr/local/lib/sasl2/libanonymous.so.2[[BR]] Reading symbols from /usr/local/lib/sasl2/libcrammd5.so.2...done.[[BR]] Loaded symbols for /usr/local/lib/sasl2/libcrammd5.so.2[[BR]] Reading symbols from /usr/local/lib/sasl2/libdigestmd5.so.2...done.[[BR]] Loaded symbols for /usr/local/lib/sasl2/libdigestmd5.so.2[[BR]] Reading symbols from /lib/libcrypto.so.6...done.[[BR]] Loaded symbols for /lib/libcrypto.so.6[[BR]] Reading symbols from /usr/local/lib/sasl2/libgssapiv2.so.2...done.[[BR]] Loaded symbols for /usr/local/lib/sasl2/libgssapiv2.so.2[[BR]] Reading symbols from /usr/lib/libgssapi.so.10...done.[[BR]] Loaded symbols for /usr/lib/libgssapi.so.10[[BR]] Reading symbols from /usr/lib/libheimntlm.so.10...done.[[BR]] Loaded symbols for /usr/lib/libheimntlm.so.10[[BR]] Reading symbols from /usr/lib/libkrb5.so.10...done.[[BR]] Loaded symbols for /usr/lib/libkrb5.so.10[[BR]] Reading symbols from /usr/lib/libhx509.so.10...done.[[BR]] Loaded symbols for /usr/lib/libhx509.so.10[[BR]] Reading symbols from /usr/lib/libcom_err.so.5...done.[[BR]] Loaded symbols for /usr/lib/libcom_err.so.5[[BR]] Reading symbols from /usr/lib/libasn1.so.10...done.[[BR]] Loaded symbols for /usr/lib/libasn1.so.10[[BR]] Reading symbols from /usr/lib/libroken.so.10...done.[[BR]] Loaded symbols for /usr/lib/libroken.so.10[[BR]] Reading symbols from /lib/libcrypt.so.5...done.[[BR]] Loaded symbols for /lib/libcrypt.so.5[[BR]] Reading symbols from /usr/local/lib/sasl2/liblogin.so.2...done.[[BR]] Loaded symbols for /usr/local/lib/sasl2/liblogin.so.2[[BR]] Reading symbols from /usr/local/lib/sasl2/libntlm.so.2...done.[[BR]] Loaded symbols for /usr/local/lib/sasl2/libntlm.so.2[[BR]] Reading symbols from /usr/local/lib/sasl2/libotp.so.2...done.[[BR]] Loaded symbols for /usr/local/lib/sasl2/libotp.so.2[[BR]] Reading symbols from /usr/lib/libopie.so.6...done.[[BR]] Loaded symbols for /usr/lib/libopie.so.6[[BR]] Reading symbols from /lib/libmd.so.5...done.[[BR]] Loaded symbols for /lib/libmd.so.5[[BR]] Reading symbols from /usr/local/lib/sasl2/libplain.so.2...done.[[BR]] Loaded symbols for /usr/local/lib/sasl2/libplain.so.2[[BR]] Reading symbols from /usr/local/lib/sasl2/libsasldb.so.2...done.[[BR]] Loaded symbols for /usr/local/lib/sasl2/libsasldb.so.2[[BR]] Reading symbols from /usr/lib/libgssapi_krb5.so.10...done.[[BR]] Loaded symbols for /usr/lib/libgssapi_krb5.so.10[[BR]] Reading symbols from /usr/lib/libgssapi_spnego.so.10...done.[[BR]] Loaded symbols for /usr/lib/libgssapi_spnego.so.10[[BR]] Reading symbols from /libexec/ld-elf.so.1...done.[[BR]] Loaded symbols for /libexec/ld-elf.so.1[[BR]] #0 0x2832b04c in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7[[BR]] (gdb) backtrace[[BR]] #0 0x2832b04c in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7[[BR]] #1 0x2832ce40 in _malloc_prefork () from /lib/libc.so.7[[BR]] #2 0x2833277e in free () from /lib/libc.so.7[[BR]] #3 0x28662b42 in gss_release_buffer () from /usr/lib/libgssapi.so.10[[BR]] #4 0x28662512 in gss_release_name () from /usr/lib/libgssapi.so.10[[BR]] #5 0x2865ee69 in gss_init_sec_context () from /usr/lib/libgssapi.so.10[[BR]] #6 0x283f7a0f in gssapi_client_mech_step () from /usr/local/lib/sasl2/libgssapiv2.so.2[[BR]] #7 0x281824b1 in sasl_client_step () from /usr/local/lib/libsasl2.so.2[[BR]] #8 0x2843eb80 in ?? ()[[BR]] #9 0x00000000 in ?? ()[[BR]] #10 0x00000000 in ?? ()[[BR]] #11 0xbfbfa944 in ?? ()[[BR]] #12 0xbfbfa93c in ?? ()[[BR]] #13 0xbfbfa938 in ?? ()[[BR]] #14 0x29683860 in ?? ()[[BR]] #15 0x281823fe in sasl_client_step () from /usr/local/lib/libsasl2.so.2 #16 0xbfbf94f8 in ?? () #17 0x28183135 in sasl_client_start () from /usr/local/lib/libsasl2.so.2[[BR]] #18 0x00000000 in ?? ()[[BR]] #19 0x00000000 in ?? ()[[BR]] #20 0xbfbfa944 in ?? ()[[BR]] #21 0xbfbfa93c in ?? ()[[BR]] #22 0xbfbfa938 in ?? ()[[BR]] #23 0x2832fd4b in malloc () from /lib/libc.so.7[[BR]] Previous frame inner to this frame (corrupt stack?)[[BR]] (gdb) [[BR]] [[BR]] I have also downloaded and installed the latest nightly snapshot of mutt with the same results.[[BR]] " fulltlt 3405 NTLM authentication hangs (and fails) on outgoing mails (exchange) mutt 1.5.20 defect mutt-dev new 2010-04-13T14:28:15-07:00 2010-04-13T14:39:51-07:00 "Hey, I'm having a bit of trouble with sending a mail via imap, the server is an exchange server and the specific error message given is ""SASL authentication failed"" I've attempted with a patch (http://marc.info/?l=mutt-dev&m=116129270115584&w=2) to no avail. The manual refers to Grant Edwards patch (I've been unable to find it). The mailbox doesn't close or anything of the sort, the mail just doesn't get sent. Let me know what you need (with commands to run as well, please) and I'll provide." zeerak 3413 incorrect charset of forwarded attachment in MIME format charset defect mutt-dev new 2010-05-26T16:49:06-07:00 2010-05-26T16:49:06-07:00 "1. Open a terminal in UTF-8 locales.[[BR]] 2. Open a mailbox having a message with a body in iso-8859-1.[[BR]] 3. Set $mime_forward to ""yes"".[[BR]] 4. View the attachments of this message with (v).[[BR]] 5. Forward the body with (f).[[BR]] 6. Enter some address for the To header, and proceed until the Compose menu.[[BR]] 7. The Compose menu says for the attachment: text/plain, 8bit, iso-8859-1. Look at this attachment with . The non-ASCII characters appear as encoded in UTF-8. Tested with the trunk (no patches) and -F /dev/null." vinc17 3415 HTML Rendering with elinks fails with different content encodings or mail and terminal mutt 1.5.20 defect mutt-dev new 2010-05-30T10:23:48-07:00 2010-05-31T11:55:49-07:00 "When using elinks to view html parts of emails, the following problem arises: mutt exports the part into the file using the terminal encoding (which seems to be fine for most text attachements, e.g. plain, tex, c source, ...) and calls elinks with the in .mailcap specified command. Now elinks reads the html file, finds a header with charset=""..."" different from the terminal charset and tries to decode all the characters using that other charset given by the meta header. The output of elinks is then encoded using the terminal character set and read by mutt using the same character set. But unfortunately elinks interprets the characters in a wrong way since the encoding of the file is not equal to that in the meta header. To reproduce: .mailcap: text/html; elinks -dump -default-mime-type text/html %s; needsterminal; copiousoutput; Have a terminal using e.g. utf-8 and read a mail using iso-8859-15. No put a few special characters into that mail like öäüß and try to read it using elinks via mutt. To workarounds: 1) Use sed to replace the charset= value of the meta header to the terminal character set, or 2) Use iconv to convert the file output by mutt to the character set specified by charset= value of meta header, or 3) Tell mutt to export text/html parts of emails using the character set given by the header actually this is difficult since mutt does not have a html parser. 4) [which is best in my eyes] Let mutt export the file in the encoding given by the associated email header, as far as i can see, that is the same encoding as the header says. This problem happens to me with emails from e-bay. Best Regards and thanks for such a useful email client, Clemens" sum 3418 ~h should be usable in send-hooks mutt 1.5.20 defect mutt-dev new 2010-06-14T01:15:56-07:00 2010-06-15T02:09:27-07:00 "Forwarded from http://bugs.debian.org/585764: Mutt allows the use of patterns in hooks, but http://www.mutt.org/doc/devel/manual.html#pattern-hook states: Mutt allows the use of the search pattern language for matching messages in hook commands. This works in exactly the same way as it would when limiting or searching the mailbox, except that you are restricted to those operators which match information Mutt extracts from the header of the message (i.e., from, to, cc, date, subject, etc.). Ironically, I cannot use ~h though, even though that searches the header. If I try, I get told: h: not supported in this mode It would be nice if ~h were usable, or if the restriction that only certain patterns are available in hooks were removed altogether, though I assume there is a good technical reason it exists. " madduck 3419 X-Label swallowed from message under composition mutt 1.5.20 defect mutt-dev new 2010-06-14T01:20:53-07:00 2010-06-14T01:20:53-07:00 "From http://bugs.debian.org/583251: I have $edit_headers set. I quite often add headers to messages I compose. This works fine, except for X-Label. If I add X-Label to the message, the header seems to get removed after the editor exits. Re-editing, or saving the message as a draft and inspecting the raw message both show the absence of the header. " madduck 3421 View limited to threads with ~() does not update properly mutt 1.5.20 defect me accepted 2010-06-15T07:26:28-07:00 2010-09-15T09:30:52-07:00 "If I limit a folder's messages e.g. with '~C mutt-dev' and I create a copy of a matching message (e.g. set editor=/bin/touch && edit-message, or by saving it to the same folder), then the new message shows up right away, giving the impression that the limit works in real-time. If, however, I limit a folder's messages with '~(~C mutt-dev)', then I need to re-execute the limit in order to see the update. This is with header_cache turned on, if it makes a difference." madduck 3453 mutt-1.5.18: wrap line as they can be selected with a double click mutt defect mutt-dev new 2010-09-20T07:32:05-07:00 2012-10-29T22:27:11-07:00 "{{{ Package: mutt Version: 1.5.18-6 Severity: wishlist -- Please type your report below this line it would be nice if mutt could wrap long line (url for exemple) as irssi does, that is, selectable with a double click and pastable as this in a browser. -- 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 Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.2-1.1' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --enable-cld --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.3.2 (Debian 4.3.2-1.1) - CFLAGS -Wall -pedantic -Wno-long-long -g -O2 -- Mutt Version Information Mutt 1.5.18 (2008-05-17) Copyright (C) 1996-2008 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.6.18-6-686 (i686) ncurses: ncurses 5.7.20081213 (compiled with 5.7) libidn: 1.8 (compiled with 1.10) hcache backend: GDBM version 1.8.3. 10/15/2002 (built Apr 24 2006 03:25:20) Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +USE_SMTP +USE_GSS -USE_SSL_OPENSSL +USE_SSL_GNUTLS +USE_SASL +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. patch-1.5.13.cd.ifdef.2 patch-1.5.13.cd.purge_message.3.4 patch-1.5.13.nt+ab.xtitles.4 patch-1.5.4.vk.pgp_verbose_mime patch-1.5.6.dw.maildir-mtime.1 patch-1.5.8.hr.sensible_browser_position.3 }}} " fraff@… 3460 "view-attachments menu ""view-attach"" command uses auto_view for all text attachments, even when a suitable interactive command is in the mailcap file. This is particularly bad for text/html attachments." mutt 1.5.20 defect mutt-dev reopened 2010-10-07T21:16:39-07:00 2011-04-28T04:18:36-07:00 "In mutt-1.5.19, the following entries in /etc/mailcap gave the desired result: text/html; w3m -T text/html %s text/html; w3m -T text/html -dump %s ; copiousoutput When the attachment was viewed from the mime viewer (""v"") menu, the first command was used to launch w3m interactively. And the autoview would work fine in non-interactive pager mode. But as of 1.5.20 (and also in 1.5.21), the first command is never triggered. Instead, it always uses the autoview copiousoutput command even when viewed from inside the mime viewer. I debugged the changes in the source, and the problem is in muttlib.c:mutt_needs_mailcap. In 1.5.19, it used to check the subtype for TYPETEXT and return false only for a few explicit subtypes. But in 1.5.20 and later, it returns false for any TYPETEXT body. This causes text/html attachments to use only the autoview solution. The patch may be to revert to the 1.5.19 behavior, but I don't claim to be an expert. Thanks, Andy" ajschorr 3463 message incorrectly displayed: bad scrolling position display defect mutt-dev new 2010-10-13T04:36:43-07:00 2010-12-20T01:07:06-08:00 "Mutt displayed a message as if it were completely empty (with no headers), but with a strange %P value. See attached screenshot, in particular the (211) corresponding to the %P value. AFAIK, this is the first time such a problem occurs. I use Mutt based on rev 6161 with some patches (but no patches should be related to the scrolling position)." vinc17 3472 Lines over 1024 in message body are broken, possibly also broking multi-byte charsets mutt 1.5.20 defect mutt-dev new 2010-11-21T09:46:57-08:00 2010-12-30T06:48:34-08:00 "When viewing a mail body, lines containing more than 1024 bytes are broken (a return is inserted). In general, it is innocuous but if ever the 1024th byte is a multi-byte character (e.g. a non-ascii utf-8 character), then the multi-byte character is split into two parts and the meaning of the character is lost (possibly also fooling the encoding recognition at the time of replying and messing the whole quoted message to which one replies). An artificial though typical example of line fooling mutt if appearing in the body of a mail is the following 1025-bytes line: ""éaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaé"" If encoded in utf-8 in the body of the mail, one will see ""\303 \251"" instead of the last ""é"" and if one replies, the first é will become ""é"" as if mutt had decided (because of the \303 and \251) that the mail was not in utf-8 but in iso-latin. I quickly looked at the code of mutt but could not figure out which of the numerous 1024-sized buffers mutt uses was the faulty one. " herbelin 3475 New mail not detected in current maildir folder mutt defect me accepted 2010-12-05T20:30:03-08:00 2012-12-07T10:25:09-08:00 "In the current folder, several minutes after new mail has arrived: {{{ ---Mutt: =Maildir [Msg:954 New:468 Inc:12 128M]---(threads)---------------(end)- }}} Moving the cursor has no effect on the folder (the new message is still missing from the index). If I open the same folder in another Mutt instance: {{{ ---Mutt: =Maildir [Msg:955 New:469 Inc:12 128M]---(threads)---------------(end)- }}} This is the first time I notice such a problem (but this doesn't mean that it hasn't occurred before)." vinc17 3476 copyright years are not up-to-date mutt defect mutt-dev new 2010-12-05T20:37:04-08:00 2010-12-05T20:37:04-08:00 The copyright years in main.c should be updated (the latest one is currently 2009). vinc17 3479 Incorrect MIME header decode MIME 1.5.20 defect mutt-dev new 2010-12-16T11:47:43-08:00 2010-12-16T11:47:43-08:00 "Header line {{{ From: =?KOI8-R?B?7MXbwT1BLkRlc2hlcmU=?= http://sos.karelia.ru/desher/ }}} displays as {{{ From: =?KOI8-R?B?7MXbwT1BLkRlc2hlcmU=?= http: ""//sos.karelia.ru/desher/"" }}} but not as {{{ From: Леша=A.Deshere http://sos.karelia.ru/desher/ }}} which is correct AFAIU. I can get additional info (full header, mutt config) if it's needed for reproducing." gul 3482 IMAP Segmentation fault when fetching message headers IMAP 1.5.21 defect brendan infoneeded_new 2010-12-30T00:24:08-08:00 2011-06-25T21:42:12-07:00 "Hi, I have 2 accounts with the same IMAP server configured in one .muttrc. the 2 accounts have the same common configurations. but one is ok, the other has a segmentation fault. it is very strange. what the differences I could tell between the 2 accounts is that, one's username has a '_', one not. I have tried to delete the last message read on the IMAP server before segmentation happened and I also tried to clean and disable header cache, but all take no effect. I really want to make it works, and I debug a lot but failed, so I put a bug here to try to find a solution. Log information attached below. 2 .muttdebug file attached, one for working account, one for non-working account PS. the mutt version is 1.5.21, but it is not in the list, so I chose 1.5.20. Thanks a lot! Best Regards Du Yang mutt -v ---------------------------------------- {{{ Mutt 1.5.21 (2010-09-15, Gentoo 1.5.21-r1) Copyright (C) 1996-2009 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.6.34-gentoo-r1 (i686) ncurses: ncurses 5.7.20081102 (compiled with 5.7) hcache backend: GDBM version 1.8.3. 10/15/2002 (built Feb 20 2009 23:12:51) Compile options: -DOMAIN +DEBUG +HOMESPOOL -USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK -USE_POP -USE_NNTP +USE_IMAP -USE_SMTP -USE_SSL_OPENSSL +USE_SSL_GNUTLS -USE_SASL -USE_GSS +HAVE_GETADDRINFO -HAVE_REGCOMP +USE_GNU_REGEX +COMPRESSED +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP -CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""Maildir"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc/mutt"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. dgc.subjrx fg.smarttime vvv.initials vvv.quote vvv.nntp patch-1.5.20hg.pdmef.progress.vl.2 rr.compressed patch-1.5.4.lpr.collapse_flagged Lukas P. Ruf }}} core {{{ ----------------------------------------------------GNU gdb (Gentoo 7.2 p1) 7.2 Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type ""show copying"" and ""show warranty"" for details. This GDB was configured as ""i686-pc-linux-gnu"". For bug reporting instructions, please see: ... Reading symbols from /usr/bin/mutt...(no debugging symbols found)...done. [New Thread 5015] warning: Can't read pathname for load map: Input/output error. Reading symbols from /lib/libncursesw.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libncursesw.so.5 Reading symbols from /usr/lib/libgnutls.so.26...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgnutls.so.26 Reading symbols from /usr/lib/libgdbm.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgdbm.so.3 Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /usr/lib/libtasn1.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libtasn1.so.3 Reading symbols from /lib/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.1 Reading symbols from /usr/lib/libgcrypt.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgcrypt.so.11 Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /usr/lib/libgpg-error.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgpg-error.so.0 Reading symbols from /lib/libnss_compat.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_compat.so.2 Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libnsl.so.1 Reading symbols from /lib/libnss_nis.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_nis.so.2 Reading symbols from /lib/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_files.so.2 Reading symbols from /lib/libnss_dns.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_dns.so.2 Reading symbols from /lib/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libresolv.so.2 Reading symbols from /usr/lib/gconv/GB18030.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/gconv/GB18030.so Reading symbols from /usr/lib/gconv/EUC-CN.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/gconv/EUC-CN.so Reading symbols from /usr/lib/gconv/libGB.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/gconv/libGB.so Core was generated by `mutt -d2 -F /home/duyang/.muttrc.imap'. Program terminated with signal 11, Segmentation fault. #0 0x0808dd59 in ?? () (gdb) q ---------------------------------------------------- }}}" duyang 3494 \Cj results in a bind to rather than ctrl+j mutt 1.5.21 defect mutt-dev new 2011-01-02T20:01:04-08:00 2011-01-03T06:51:30-08:00 "This bug has been reported to debian at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547661 . I tried it and I could reproduce it as well. I even compiled the official version and still the error was reproducible there. The problem happens when I try to bind \Cj, mutt interprets that as . Even if execute ``bind -r '\C-j''' in my shell first, I still get the same error. I used mutt's what-key function and both C-j and report: Char = , Octal = 12, Decimal = 10 There was one person on Debian's bug report who couldn't reproduce the bug. So I suspect it might be related to the terminal or the shell. I'm using rxvt-unicode (urxvt) v9.07 and bash 4.1.5, both stock from Debian squeeze repository. Though I've also tried from tty and xterm using both csh and bash. I made a small curses program (it's attached) that reads a key press and prints the character. Running it in my setup gives me 10 for C-j and 13 for . Afaik 10 is the character of \n and 13 is the character number for \r. So I guess I can see where the confusion arises from. But note how that differs from what-key output." rafael 3497 Mutt crashes when terminal window becomes too small mutt 1.5.21 defect mutt-dev new 2011-01-20T09:34:57-08:00 2011-01-20T09:34:57-08:00 "When the terminal window containing mutt becomes too small (i.e. is resized), mutt crashed with a segfault. For the main window, this occurs when the terminal is less that two characters high, when a message is open it occurs below five lines and when composing an email (i.e. after having closed the editor, but before sending the email), it occurs below ~8 lines. Especially the last crash is critical, as it leads to loss of data (the newly written email). It is also the only one that occurs for me in normal use. This happens because I am using a tiling window manager with a small terminal below mutt; when viewing an attachment (such as when confirming that the right file is attached), mutt is then temporarily demoted to be in the small window. While I realise mutt is not very useful in a terminal that is less than eight characters high, I would expect it to survive without segfaulting; and either suspend drawing of the screen until the terminal becomes large enough, or at least exit gracefully without data loss." tohojo 3499 MUTT and GMAIL SMTP RELAY. Issues using mutt from command line mutt 1.5.20 defect mutt-dev new 2011-02-02T12:04:29-08:00 2011-02-04T06:42:34-08:00 "I have installed and configured mutt with gmail with no issues I can send emails from mutt, but now I need to send email using scripts. If I try to use mutt from cmd line I have the following error. trst:~ # echo ""TESTING MUTT AND GMAIL SMTP RELAY"" | mutt -s ""test"" ""example@test.com"" SSL connection using TLSv1/SSLv3 (RC4-MD5) Interactive SMTP authentication not supported Could not send the message. I found this article, but I don't understand what exactly needs to be done. http://bugs.mutt.org/trac/ticket/3289 Thanks " qsummon 3502 Issue with browsing IMAP folders, having a non-ASCII characters in names IMAP 1.5.21 defect brendan new 2011-02-16T03:50:00-08:00 2011-02-16T03:50:00-08:00 "I've found that there is an issue with browsing and navigating IMAP folders if folder's name contains non-ASCII characters (i.e. folder name is IMAPUTF-7 encoded). The reason is in comparison of strings in a different encodings. The attached patch fixes this issue. " alexz 3509 Various build errors after ./prepare is run mutt 1.5.21 defect mutt-dev infoneeded_new 2011-03-26T23:59:56-07:00 2011-03-30T08:02:29-07:00 "After applying VVV's rr-compressed patch, I needed to run {{{prepare}}} so the {{{--enable-compressed}}} option for {{{configure}}} was recognized. This led to a couple of subsequent build errors: {{{ brian@turquoise <11:44 PM> 598$ make mutt cd . && /bin/sh /usr/local/src/mutt-1.5.21/missing --run automake-1.9 --foreign Makefile.am: required file `./compile' not found make: *** [Makefile.in] Error 1 }}} This was resolved by adding the {{{-a}}} option to the automake-1.9 argument in the Makefile and re-running the make command. After configure ran again (!), this error cropped up: {{{ configure: creating ./config.status cd && /bin/sh ./config.status Makefile depfiles /bin/sh: ./config.status: No such file or directory make: *** [Makefile] Error 127 }}} This was resolved by running {{{./config.status Makefile depfiles}}} manually. Compilation after this was successful. Some other info that might be of interest: autoconf version: 2.59 automake version: 1.9.4 Linux O/S" brianko 3510 Expiration date of an SSL certificate not checked mutt 1.5.20 defect mutt-dev new 2011-04-10T06:59:45-07:00 2011-04-10T06:59:45-07:00 "My mail account provider netmark.pl (also using a name r1.2box.pl) has a mail server supporting IMAP with TLS. It is available at wodny.org:143. For some time the server used an expired certificate and something unusual happened. Fetchmail, esmtp and stunnel refused to connect, but mutt-1.5.20 still allowed that. The testing environment could be easily created, because the new certificate is valid only for one year. There were two certificates presented during the connection: 0 s:[...]/CN=r1.2box.pl i:/C=US/O=Equifax/OU=Equifax Secure Certificate Authority 1 s:/C=US/O=Equifax/OU=Equifax Secure Certificate Authority i:/C=US/O=Equifax/OU=Equifax Secure Certificate Authority The ssl_verify_dates option was enabled and Mutt recompiled by me entered the code checking certificates' dates. Still, this did not caused the process of connecting stop. Recompiled version was used for debug. Originally a Debian package version was used. Interesting part seems to be at the end of the mutt_ssl_gnutls.c file... The loop beginning at line 1003 does not do anything here, as the Equifax certificate is in /etc/ssl/certs and it is valid. The certificate issued to r1.2box.pl is not stored on the disk. The condition ""if (savedcert)"" at line 1008 is never true. Then code goes as far as to line 1032, where it returns 1 (everything OK) but being at the stage of checking the root CA. So the certificate issued by Equifax to r1.2box.pl is not checked. I have not been prompted if I would like add an exception as it usually happens. Debian Security Team has been informed. There has been the CVE-2011-0429 id assigned to this issue. Bug also present in the 1.5.21 version. Might be associated with bug #3506." wodny 3526 Building mutt-1.5.21 with SSL and SASL fails with undefined symbol mutt defect mutt-dev infoneeded_new 2011-06-26T16:14:25-07:00 2011-07-01T18:25:51-07:00 "I'm building this way on Solaris 10: --with-curses=/usr/local \ --enable-pop \ --enable-imap \ --with-sasl \ --with-ssl=/usr/local/openssl The result is this error: source='mutt_sasl.c' object='mutt_sasl.o' libtool=no \ DEPDIR=.deps depmode=none /bin/bash ./depcomp \ cc -DPKGDATADIR=\""/usr/local/share/mutt\"" -DSYSCONFDIR=\""/usr/local/etc\"" +-DBINDIR=\""/usr/local/bin\"" -DMUTTLOCALEDIR=\""/usr/local/share/locale\"" +-DHAVE_CONFIG_H=1 -I. -I. -I. -I./imap -Iintl -I/usr/local/include +-I/usr/local/openssl/include -g -c mutt_sasl.c cc -g -R/usr/local/openssl/lib:/usr/local/lib -L/usr/local/lib +-L/usr/local/openssl/lib -o mutt addrbook.o alias.o attach.o base64.o +browser.o buffy.o color.o crypt.o cryptglue.o commands.o complete.o compose.o +copy.o curs_lib.o curs_main.o date.o edit.o enter.o flags.o init.o filter.o ... +utf8.o wcwidth.o strsep.o wcscasecmp.o strcasestr.o mkdtemp.o -Limap -limap +-lncurses -lssl -lcrypto -lz -lsasl2 ./intl/libintl.a -lsocket -lnsl Undefined +first referenced symbol +in file imap_auth_cram_md5 imap/libimap.a(auth.o) imap_auth_anon imap/libimap.a(auth.o) As SASL only adds one more authentication method, DIGEST-MD5, I opted to build it with SSL only. That was successful. " jgmills 3529 trac logs me out while writing a ticket browser defect mutt-dev infoneeded_new 2011-06-29T06:30:28-07:00 2011-06-29T21:23:01-07:00 "Timeout too low! And browser's ""back"" doesn't bring me back to the nicely filled out form. :-(" barsnick 3530 Crash on search in IMAP(S) mailbox IMAP 1.5.21 defect brendan infoneeded_new 2011-06-29T06:40:58-07:00 2011-07-16T10:47:37-07:00 "mutt crashes on searching within an IMAP(S) mailbox. I connect and log in to a mailbox using an imaps:// type folder. I search (using '/') for this: {{{ ~h ""freshm|bugz"" }}} Resulting in this: {{{ Fetching message... 0K/1.0K (0%)*** glibc detected *** /usr/local/new/tools/networking/mail/mutt/mutt-hg/mutt-build/mutt: free(): invalid next size (fast): 0x081db720 *** [... glibc crash info ...] Program received signal SIGABRT, Aborted. 0x00bb7416 in __kernel_vsyscall () Missing separate debuginfos, use: debuginfo-install cyrus-sasl-lib-2.1.22-19.fc10.i386 cyrus-sasl-md5-2.1.22-19.fc10.i386 cyrus-sasl-ntlm-2.1.22-19.fc10.i386 cyrus-sasl-plain-2.1.22-19.fc10.i386 db4-4.7.25-7.fc10.i386 glibc-2.9-3.i686 gnutls-2.4.2-5.fc10.i386 libgcc-4.3.2-7.i386 libgcrypt-1.4.4-1.fc10.i386 libgpg-error-1.6-2.i386 libidn-0.6.14-8.i386 libtasn1-1.5-1.fc10.i386 ncurses-libs-5.6-20.20080927.fc10.i386 openssl-0.9.8g-14.fc10.i686 zlib-1.2.3-22.fc10.1sunshine.pentium4 (gdb) bt #0 0x00bb7416 in __kernel_vsyscall () #1 0x006d0460 in raise () from /lib/libc.so.6 #2 0x006d1e28 in abort () from /lib/libc.so.6 #3 0x0070dfed in __libc_message () from /lib/libc.so.6 #4 0x007143a4 in malloc_printerr () from /lib/libc.so.6 #5 0x00716356 in free () from /lib/libc.so.6 #6 0x080b6238 in safe_free (ptr=0xbfffcdb8) at lib.c:198 #7 0x080ab670 in write_one_header (fp=0x81da5d8, pfxw=0, max=, wraplen=78, pfx=0x0, start=0x81db1b1 ""Received: from AFAXSMK (unknown [68.178.18.24]) by xxx-xxx.xxx (Postfix) with ESMTP id 65C759B481C for ; Wed, 29 Jun 2011 06:07:39 +0200 (CEST)\nReceived: from 68.178.18.24""..., end=0x81db25e ""Received: from 68.178.18.24 by mail.lanuk.com; Tue, 28 Jun 2011 20:07:13 -0800\nMessage-ID: <000d01cc3612$069cc3b0$6400a8c0@huggingyw5>\nFrom: ?????? ??? \nTo: moritz@xxx.xxx\nS""..., flags=20) at sendlib.c:1825 #8 0x080ab9b4 in mutt_write_one_header (fp=0x81da5d8, tag=0x0, value=0x81d95f8 ""Return-Path: \nX-Original-To: moritz@xxx.xxx\nDelivered-To: xxxxx@xxx-xxx.xxx\nReceived: from AFAXSMK (unknown [68.178.18.24])\n\tby xxx-xxx.xxx (Postfix) with ""..., pfx=0x0, wraplen=78, flags=20) at sendlib.c:1894 #9 0x0805ef4c in mutt_copy_hdr (in=0x81da100, out=0x81da5d8, off_start=0, off_end=898, flags=20, prefix=0x0) at copy.c:289 #10 0x0805f5bc in mutt_copy_header (in=0x81da100, h=0x81b8c58, out=0x81da5d8, flags=20, prefix=0x0) at copy.c:350 #11 0x08096376 in msg_search (ctx=0x815f310, pat=0x8194280, msgno=) at pattern.c:174 #12 0x08096e54 in mutt_pattern_exec (pat=0x8194280, flags=M_MATCH_FULL_ADDRESS, ctx=0x815f310, h=0x81b8c58) at pattern.c:1144 #13 0x08098840 in mutt_search_command (cur=0, op=154) at pattern.c:1512 #14 0x0806474c in mutt_index_menu () at curs_main.c:901 #15 0x08080430 in main (argc=Cannot access memory at address 0x5dda ) at main.c:1020 }}} If I use this search: {{{ ~h ""freshm"" }}} I get a slightly different crash: {{{ Fetching message... 0K/1.0K (0%)*** glibc detected *** /usr/local/new/tools/networking/mail/mutt/mutt-hg/mutt-build/mutt: free(): invalid next size (normal): 0x081da318 *** [... glibc crash info ...] Program received signal SIGABRT, Aborted. 0x003cc416 in __kernel_vsyscall () Missing separate debuginfos, use: debuginfo-install cyrus-sasl-lib-2.1.22-19.fc10.i386 cyrus-sasl-md5-2.1.22-19.fc10.i386 cyrus-sasl-ntlm-2.1.22-19.fc10.i386 cyrus-sasl-plain-2.1.22-19.fc10.i386 db4-4.7.25-7.fc10.i386 glibc-2.9-3.i686 gnutls-2.4.2-5.fc10.i386 libgcc-4.3.2-7.i386 libgcrypt-1.4.4-1.fc10.i386 libgpg-error-1.6-2.i386 libidn-0.6.14-8.i386 libtasn1-1.5-1.fc10.i386 ncurses-libs-5.6-20.20080927.fc10.i386 openssl-0.9.8g-14.fc10.i686 zlib-1.2.3-22.fc10.1sunshine.pentium4 (gdb) bt all No symbol ""all"" in current context. (gdb) bt #0 0x003cc416 in __kernel_vsyscall () #1 0x006d0460 in raise () from /lib/libc.so.6 #2 0x006d1e28 in abort () from /lib/libc.so.6 #3 0x0070dfed in __libc_message () from /lib/libc.so.6 #4 0x007143a4 in malloc_printerr () from /lib/libc.so.6 #5 0x00717e46 in _int_realloc () from /lib/libc.so.6 #6 0x00718c86 in realloc () from /lib/libc.so.6 #7 0x080b62a2 in safe_realloc (ptr=0x81d9150, siz=0) at lib.c:176 #8 0x0805f07b in mutt_copy_hdr (in=0x81dade0, out=0x81db048, off_start=0, off_end=898, flags=, prefix=0x0) at copy.c:169 #9 0x0805f5bc in mutt_copy_header (in=0x81dade0, h=0x81b8c80, out=0x81db048, flags=20, prefix=0x0) at copy.c:350 #10 0x08096376 in msg_search (ctx=0x815f310, pat=0x81d7b58, msgno=) at pattern.c:174 #11 0x08096e54 in mutt_pattern_exec (pat=0x81d7b58, flags=M_MATCH_FULL_ADDRESS, ctx=0x815f310, h=0x81b8c80) at pattern.c:1144 #12 0x08098840 in mutt_search_command (cur=0, op=154) at pattern.c:1512 #13 0x0806474c in mutt_index_menu () at curs_main.c:901 #14 0x08080430 in main (argc=Cannot access memory at address 0x5e54 ) at main.c:1020 }}} mutt is latest (as of today) from hg (6187:b477d7c5733e on HEAD/tip). It is built as such: {{{ ./configure --enable-imap --with-sasl --with-gnutls }}} resulting in: {{{ barsnick@sunshine:/usr/new/tools/networking/mail/mutt/mutt-hg/mutt-build > ./mutt -v Mutt + (b477d7c5733e) (2010-12-30) Copyright (C) 1996-2009 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.6.27.41-170.2.117.fc10.i686 (i686) ncurses: ncurses 5.6.20080927 (compiled with 5.6) libidn: 0.6.14 (compiled with 0.6.14) Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP +USE_IMAP -USE_SMTP -USE_SSL_OPENSSL +USE_SSL_GNUTLS +USE_SASL -USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID -USE_HCACHE ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER }}} and executed as such: {{{ gdb --args ./mutt -F /dev/null -f /dev/null }}}" barsnick 3533 Mutt freezes on SASL authentication failure (imap) mutt 1.5.20 defect mutt-dev new 2011-07-26T00:27:08-07:00 2011-07-26T00:27:08-07:00 "Wrong IMAP password (or I hit ^G, not sure) and mutt freezed right after notifying: ""SASL authentication failure"". Attaching the process with gdb gives this backtrace: {{{ #0 0x00007f304fc5e472 in __libc_recv (fd=, buf=0x1b4b0c0, n=5, flags=) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:30 #1 0x00007f305099fc59 in ?? () from /usr/lib/libgnutls.so.26 #2 0x00007f305099ff23 in ?? () from /usr/lib/libgnutls.so.26 #3 0x00007f305099b8e1 in _gnutls_recv_int () from /usr/lib/libgnutls.so.26 #4 0x00007f305099cc8f in gnutls_bye () from /usr/lib/libgnutls.so.26 #5 0x00000000004981f7 in ?? () #6 0x0000000000496864 in ?? () #7 0x0000000000495464 in ?? () #8 0x00000000004675df in ?? () #9 0x000000000042308a in ?? () #10 0x000000000043d967 in ?? () #11 0x00007f304fb95c4d in __libc_start_main (main=, argc=, ubp_av=, init=, fini=, rtld_fini=, stack_end=0x7fffe2053c78) at libc-start.c:226 }}} Could be a gnutls issue..." strk 3535 check for new mail from the internal viewer in maildir mailboxes mutt defect mutt-dev new 2011-08-21T03:36:16-07:00 2011-08-21T03:36:16-07:00 When a message is viewed in a maildir mailbox, mutt does not check for new mail in the folders specified by the mailboxes command until back in the index mode. It would be nice if mutt could notify of new mail also in the pager mode. miguel 3539 User Input is often ignored mutt defect mutt-dev new 2011-09-21T05:43:03-07:00 2011-09-21T05:43:03-07:00 "Mutt often ignores the user or does not allow for interactivity. Many operations cannot be forced to cancel (such as downloading an email from a remote or closing a connection) and Mutt will perform them or infinitly try to perform then, completely ignoring the wish of the user. This is a somewhat general problem throughout Mutt. A start to remdedy that would be to allow the user to cancel operations such as connecting, disconnecting, performing operations on the remote and downloading data from the remote." ManDay 3540 Mutt crashes when connection terminates unexpectedly mutt defect mutt-dev new 2011-09-21T05:43:28-07:00 2011-09-21T05:43:28-07:00 When connected to an IMAP server and the connection is inproperly lost (network fail, etc) Mutt will never properly quit, only by external signal, not by pressing Q. This is somewhat related to #3539 ManDay 3542 mutt sometimes fails to detect new messages in the current maildir maildir/mh 1.5.21 defect mutt-dev new 2011-10-08T02:02:58-07:00 2011-10-09T19:07:29-07:00 "My inbox is a local maildir and I use ""set timeout=1"". Say my inbox is the current folder. Normally mutt will display any new mail to my inbox with a delay of at most one second. However when receiving a lot of new message more or less at the same time it sometimes happens that mutt will only detect some of them at all. The following command reproduces this rather reliably for me: {{{ $ for (( i=1; i<=20; i++ )); do mail -s kBqYKThe5q $USER < /dev/null; done }}} If I run this command mutt will (in maybe 2 out of 5 cases) only detect one or two of the 20 new messages. The only way I have found to make it find all the new messages is to explicitly open my inbox again with ""c!""." AopicieR 3543 mutt-1.5.20: charset-hook doesn't work for header line mutt defect mutt-dev new 2011-10-20T04:39:21-07:00 2011-10-21T07:48:39-07:00 "{{{ Package: mutt Version: 1.5.20 Severity: normal -- Please type your report below this line Hi, I received a delivery status notification e-mail with character set ""unicode-1-1-utf-7"". I managed to display the body correctly by issuing :charset-hook unicode-1-1-utf-7 utf-7 but this doesn't work for header lines; I still see: Subject: Benachrichtigung =?unicode-1-1-utf-7?Q?+ANw-bermittlungsstatus (Verz+APY-gerung)?= IMO, this needs to work for the header, too. Regards, -is -- System Information System Version: NetBSD marie 5.1 NetBSD 5.1 (MARIE) #0: Wed Jan 5 20:52:48 CET 2011 ignatios@random87:/var/itch/obj/shark/sys/arch/shark/compile/MARIE shark -- 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 cc Using built-in specs. Target: arm--netbsdelf Configured with: /usr/src/tools/gcc/../../gnu/dist/gcc4/configure --enable-long-long --disable-multilib --enable-threads --disable-symvers --build=x86_64-unknown-netbsd4.99.72 --host=arm--netbsdelf --target=arm--netbsdelf --enable-__cxa_atexit Thread model: posix gcc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) - CFLAGS -Wall -pedantic -Wno-long-long -O2 -I/usr/include -I/usr/pkg/include/db4 -- Mutt Version Information Mutt 1.5.20 (2009-06-14) Copyright (C) 1996-2009 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: NetBSD 5.1 (shark) hcache backend: Berkeley DB 4.8.30: (April 9, 2010) Compile options: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP -USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR -HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/pkg/share/mutt"" SYSCONFDIR=""/usr/pkg/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. --- Begin /usr/pkg/etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /usr/pkg/share/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /usr/pkg/share/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /usr/pkg/share/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" set hostname=beverly.kleinbus.org --- End /usr/pkg/etc/Muttrc }}} " is@… 3545 "IMAP header should continue to fetch after a ""tls_socket_read"" failure" header cache 1.5.21 defect mutt-dev new 2011-10-23T06:24:33-07:00 2011-10-23T06:24:33-07:00 "Hi, I have a gmail INBOX with more than 20,000 messages. I configured mutt IMAP to this mailbox. For this is the first time to this mailbox, mutt try to fetch all the headers at the beginning and always got the well-known problem ""tls_socket_read (A TLS packet with unexpected length was received.)"" when just fetched about 5000 headers. I've to set imap_keepalive to 300, 100, 30 and 10, but without success. mail_check and timeout is 30 and 10 respectively. Here are some error information with debug level 5: ======================================= [2011-10-23 08:16:18] tls_socket_read (A TLS packet with unexpected length was received.) [2011-10-23 08:16:22] imap_cmd_step: Error reading server response. [2011-10-23 08:16:22] Error opening mailbox ======================================= So I never get mutt to work with such a INBOX. In order to make it work, I think mutt needs to support 1)to manage a well-formated header cache file when connection not available temporarily or disconnected on the server end. 2) to re-fetching the remaining headers but not all headers each time.(The second one is rely on the first.) " duyang 3546 mutt-1.5.21: IMAP protocol problem: skipping FETCH response for unknown message number mutt defect mutt-dev new 2011-10-24T17:19:43-07:00 2011-10-24T17:19:43-07:00 "{{{ Package: mutt Version: 1.5.21 Severity: normal -- Please type your report below this line Hello, I'm trying to use mutt (1.5.21 on OpenBSD 4.9) to connect to an IMAP server. Connection and authentication work fine but then something goes wrong while fetching message headers: I get a ""skipping FETCH response for unknown message number"" error for every message and then mutt gets stuck and I have to kill it. Here's the log: [...] [2011-10-24 20:21:56] SSL connection using TLSv1/SSLv3 (ECDHE-RSA-AES256-SHA) [2011-10-24 20:21:57] Connected to some.imap.server.some.where:993 on fd=4 [2011-10-24 20:21:57] 4< * OK localhost CrediMail imapserver-2.5 ready. [2011-10-24 20:21:57] 4> a0000 CAPABILITY [2011-10-24 20:21:57] 4< * CAPABILITY IMAP4 IMAP4rev1 [2011-10-24 20:21:57] 4< a0000 OK CAPABILITY COMPLETED. [2011-10-24 20:21:57] imap_authenticate: Using any available method. [2011-10-24 20:22:00] Logging in... [2011-10-24 20:22:00] Sending LOGIN command for meunier... [2011-10-24 20:22:00] 4< a0001 OK LOGIN COMPLETED. [2011-10-24 20:22:00] Communication encrypted at 256 bits [2011-10-24 20:22:00] 4> a0002 CAPABILITY a0003 LIST """" """" [2011-10-24 20:22:00] 4< * CAPABILITY IMAP4 IMAP4rev1 [2011-10-24 20:22:00] 4< a0002 OK CAPABILITY COMPLETED. [2011-10-24 20:22:00] 4< * LIST (\NoInferiors \HasNoChildren) ""/"" ""Archives"" [2011-10-24 20:22:00] 4< * LIST (\NoInferiors \HasNoChildren) ""/"" ""Drafts"" [2011-10-24 20:22:00] 4< * LIST (\NoInferiors \HasNoChildren) ""/"" ""INBOX"" [2011-10-24 20:22:00] 4< * LIST (\NoInferiors \HasNoChildren) ""/"" ""Sent Messages"" [2011-10-24 20:22:00] 4< * LIST (\NoInferiors \HasNoChildren) ""/"" ""&wqTTOLpUx3zVaA-"" [2011-10-24 20:22:00] 4< * LIST (\NoInferiors \HasNoChildren) ""/"" ""Deleted Messages"" [2011-10-24 20:22:00] 4< a0003 OK LIST COMPLETED [2011-10-24 20:22:00] Selecting INBOX... [2011-10-24 20:22:00] 4> a0004 SELECT ""INBOX"" [2011-10-24 20:22:00] 4< * 12 EXISTS [2011-10-24 20:22:00] Handling EXISTS [2011-10-24 20:22:00] cmd_handle_untagged: New mail in INBOX - 12 messages total. [2011-10-24 20:22:00] 4< * 3 RECENT [2011-10-24 20:22:00] 4< * OK [UNSEEN 100028] Message 100028 is first unseen. [2011-10-24 20:22:00] 4< * OK [UIDVALIDITY 1319410466] UID validity status [2011-10-24 20:22:00] 4< * OK [UIDNEXT 100028] UIDNEXT [2011-10-24 20:22:00] 4< * FLAGS (\Deleted \Seen \Recent \Flagged \Draft \Recent) [2011-10-24 20:22:00] 4< * OK [PERMANENTFLAGS (\Deleted \Seen \*)] PermanentFlags [2011-10-24 20:22:00] 4< a0004 OK [READ-WRITE] SELECT COMPLETED [2011-10-24 20:22:00] Fetching message headers... (12) [2011-10-24 20:22:00] 4> a0005 FETCH 1:12 (UID FLAGS INTERNALDATE RFC822.SIZE BODY.PEEK[HEADER.FIELDS (DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES LIST-POST X-LABEL)]) [2011-10-24 20:22:01] 4< * 100027 FETCH (UID 100027 FLAGS (\Recent \Seen) INTERNALDATE ""24-Oct-2011 16:23:00 +0900"" RFC822.SIZE 39753 BODY[HEADER.FIELDS (DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES LIST-POST X-LABEL)] {312} [2011-10-24 20:22:01] imap_read_literal: reading 312 bytes [2011-10-24 20:22:01] 4< ) [2011-10-24 20:22:01] imap_read_headers: skipping FETCH response for unknown message number 100027 [2011-10-24 20:22:01] 4< * 100023 FETCH (UID 100023 FLAGS (\Recent \Seen) INTERNALDATE ""24-Oct-2011 11:15:00 +0900"" RFC822.SIZE 575722 BODY[HEADER.FIELDS (DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES LIST-POST X-LABEL)] {348} [2011-10-24 20:22:01] imap_read_literal: reading 348 bytes [2011-10-24 20:22:01] 4< ) [2011-10-24 20:22:01] imap_read_headers: skipping FETCH response for unknown message number 100023 [... and so on for every message ...] [2011-10-24 20:22:01] 4< * 100002 FETCH (UID 100002 FLAGS (\Seen) INTERNALDATE ""26-Jul-2011 11:31:00 +0900"" RFC822.SIZE 107354 BODY[HEADER.FIELDS (DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES LIST-POST X-LABEL)] {393} [2011-10-24 20:22:01] imap_read_literal: reading 393 bytes [2011-10-24 20:22:01] 4< ) [2011-10-24 20:22:01] imap_read_headers: skipping FETCH response for unknown message number 100002 [2011-10-24 20:22:01] 4< * 100001 FETCH (UID 100001 FLAGS (\Seen) INTERNALDATE ""01-Jul-2011 09:50:00 +0900"" RFC822.SIZE 26958 BODY[HEADER.FIELDS (DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES LIST-POST X-LABEL)] {357} [2011-10-24 20:22:01] imap_read_literal: reading 357 bytes [2011-10-24 20:22:01] 4< ) [2011-10-24 20:22:01] imap_read_headers: skipping FETCH response for unknown message number 100001 [2011-10-24 20:22:01] 4< a0005 OK FETCH COMPLETED. At that point mutt gets stuck and the log ends. So... anyone has any idea how I might get this to work? Please note: I have no control over the IMAP server. For reference, here's the log from thunderbird, which works fine: -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:NA:CreateNewLineFromSocket: * OK localhost CrediMail imapserver-2.5 ready. -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:NA:SendData: 1 capability -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=30 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:NA:CreateNewLineFromSocket: * CAPABILITY IMAP4 IMAP4rev1 -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=28 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:NA:CreateNewLineFromSocket: 1 OK CAPABILITY COMPLETED. -2056607744[8807fe00]: try to log in -2056607744[8807fe00]: IMAP auth: server caps 0x35, pref 0x1006, failed 0x0, avail caps 0x4 -2056607744[8807fe00]: (GSSAPI = 0x1000000, CRAM = 0x20000, NTLM = 0x100000, MSN = 0x200000, PLAIN = 0x1000, LOGIN = 0x2, old-style IMAP login = 0x4) -2056607744[8807fe00]: trying auth method 0x4 -2056607744[8807fe00]: got new password -2056607744[8807fe00]: IMAP: trying auth method 0x4 -2056607744[8807fe00]: old-style auth -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:NA:SendData: Logging suppressed for this command (it probably contained authentication information) -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=23 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:NA:CreateNewLineFromSocket: 3 OK LOGIN COMPLETED. -2056607744[8807fe00]: login succeeded -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:SendData: 4 list """" ""%"" -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=53 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: * LIST (\NoInferiors \HasNoChildren) ""/"" ""Archives"" -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=51 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: * LIST (\NoInferiors \HasNoChildren) ""/"" ""Drafts"" -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=50 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: * LIST (\NoInferiors \HasNoChildren) ""/"" ""INBOX"" -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=58 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: * LIST (\NoInferiors \HasNoChildren) ""/"" ""Sent Messages"" -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=61 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: * LIST (\NoInferiors \HasNoChildren) ""/"" ""&wqTTOLpUx3zVaA-"" -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=61 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: * LIST (\NoInferiors \HasNoChildren) ""/"" ""Deleted Messages"" -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=21 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: 4 OK LIST COMPLETED -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:SendData: 5 list """" ""%/%"" -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=21 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: 5 OK LIST COMPLETED -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:SendData: 6 list """" ""Shared Folders/User/%"" -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=21 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: 6 OK LIST COMPLETED -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:SendData: 7 list """" ""Shared Folders/User/%/%"" -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=21 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: 7 OK LIST COMPLETED -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:SendData: 8 list """" ""INBOX"" -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=50 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: * LIST (\NoInferiors \HasNoChildren) ""/"" ""INBOX"" -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=21 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: 8 OK LIST COMPLETED -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:SendData: 9 select ""INBOX"" -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=13 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: * 12 EXISTS -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=12 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: * 3 RECENT -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=54 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: * OK [UNSEEN 100028] Message 100028 is first unseen. -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=51 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: * OK [UIDVALIDITY 1319410466] UID validity status -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=31 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: * OK [UIDNEXT 100028] UIDNEXT -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=58 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: * FLAGS (\Deleted \Seen \Recent \Flagged \Draft \Recent) -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=58 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: * OK [PERMANENTFLAGS (\Deleted \Seen \*)] PermanentFlags -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=36 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:A:CreateNewLineFromSocket: 9 OK [READ-WRITE] SELECT COMPLETED -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:S-INBOX:SendData: 10 UID fetch 1:* (FLAGS) -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=54 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:S-INBOX:CreateNewLineFromSocket: * 100001 FETCH (UID 100001 FLAGS (\Seen) UID 100001) -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=54 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:S-INBOX:CreateNewLineFromSocket: * 100002 FETCH (UID 100002 FLAGS (\Seen) UID 100002) -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=54 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:S-INBOX:CreateNewLineFromSocket: * 100003 FETCH (UID 100003 FLAGS (\Seen) UID 100003) -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=54 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:S-INBOX:CreateNewLineFromSocket: * 100004 FETCH (UID 100004 FLAGS (\Seen) UID 100004) -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=54 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:S-INBOX:CreateNewLineFromSocket: * 100005 FETCH (UID 100005 FLAGS (\Seen) UID 100005) -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=54 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:S-INBOX:CreateNewLineFromSocket: * 100006 FETCH (UID 100006 FLAGS (\Seen) UID 100006) -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=54 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:S-INBOX:CreateNewLineFromSocket: * 100007 FETCH (UID 100007 FLAGS (\Seen) UID 100007) -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=54 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:S-INBOX:CreateNewLineFromSocket: * 100008 FETCH (UID 100008 FLAGS (\Seen) UID 100008) -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=54 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:S-INBOX:CreateNewLineFromSocket: * 100011 FETCH (UID 100011 FLAGS (\Seen) UID 100011) -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=62 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:S-INBOX:CreateNewLineFromSocket: * 100022 FETCH (UID 100022 FLAGS (\Recent \Seen) UID 100022) -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=62 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:S-INBOX:CreateNewLineFromSocket: * 100023 FETCH (UID 100023 FLAGS (\Recent \Seen) UID 100023) -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=62 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:S-INBOX:CreateNewLineFromSocket: * 100027 FETCH (UID 100027 FLAGS (\Recent \Seen) UID 100027) -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=28 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:S-INBOX:CreateNewLineFromSocket: 10 OK UID FETCH COMPLETED. -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:S-INBOX:SendData: 11 UID fetch 100027 (UID RFC822.SIZE FLAGS BODY.PEEK[HEADER.FIELDS (From To Cc Bcc Subject Date Message-ID Priority X-Priority References Newsgroups In-Reply-To Content-Type)]) -2056607744[8807fe00]: ReadNextLine [stream=8320a208 nb=213 needmore=0] -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:S-INBOX:CreateNewLineFromSocket: * 100027 FETCH (UID 100027 UID 100027 RFC822.SIZE 39753 FLAGS (\Recent \Seen) BODY[HEADER.FIELDS (From To Cc Bcc Subject Date Message-ID Priority X-Priority References Newsgroups In-Reply-To Content-Type)] {327} -2056607744[8807fe00]: 8600c000:some.imap.server.some.where:S-INBOX:STREAM:OPEN Size: 39753: Begin Message Download Stream [... etc, everything works ...] Thanks for any help, Philippe -- System Information System Version: OpenBSD some.imap.client.some.where 4.9 GENERIC#671 i386 -- 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/bin/../lib/gcc-lib/i386-unknown-openbsd4.9/4.2.1/specs Target: i386-unknown-openbsd4.9 Configured with: OpenBSD/i386 system compiler Thread model: posix gcc version 4.2.1 20070719 - CFLAGS -Wall -pedantic -Wno-long-long -g -O2 -- Mutt Version Information Mutt 1.5.21 (2010-09-15) Copyright (C) 1996-2009 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: OpenBSD 4.9 (i386) ncurses: ncurses 5.7.20081102 (compiled with 5.7) libiconv: 1.13 hcache backend: qdbm 1.8.77 Compile options: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID -USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK +USE_POP +USE_IMAP +USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL +USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE ISPELL=""/usr/local/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/etc/mutt"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. }}} " meunier@… 3561 Incorrect names of sent attachments with non-ascii characters mutt 1.5.21 defect mutt-dev new 2012-01-19T10:30:48-08:00 2012-01-23T15:09:05-08:00 "When I send out email and add attachments, that contain non-ascii characters in the name (such as žluťoučký-kůň.txt), the name is not correctly viewed in some clients. For example Outlook 2010+ changes it into ATT-00185.txt or similar. When I send the same attachment from Thunderbird, the name is displayed on recipient side without problems." kolcon 3563 "NO Beep for New Messages, but ""beep_new"" is set" mutt 1.5.21 defect mutt-dev new 2012-02-01T01:02:00-08:00 2012-02-01T01:02:00-08:00 "I use mutt on xterm, konsole and urxvt. I have ""set beep_new=yes"" in my ~/.muttrc, but there's no beep upon receiving new messages. I also have ""set beep=yes"", which works fine, as I get a beep when an error is encountered. I always get a notification ""New message in inbox"" when a new message is received, but no beep. It should have worked I think, since the variable is set. I have tried on a different computer with gnome-terminal, and no luck." riderplus 3569 Segmentation fault in sync_helper mutt 1.5.21 defect mutt-dev new 2012-03-27T01:14:33-07:00 2012-03-27T01:14:33-07:00 "Mutt sometimes crashes in sync_helper (imap.c:1131) because of a segmentation fault. Regarding the backtrace it fails because idata->ctx is NULL, which is not expected at this point, but seeing many similar failures in [1], [2] and [3], it really happens. What we know from bug reports, it usually happens after many changes in the imap folder or after imap server failure occurs. I suspect mutt to erased idata->ctx after it fails to communicate with imap server, but I don't know how to reproduce it. There are many checks of idata->ctx to be set before working with it in other places, so I'd suggest to add a check into sync_helper as well, for example as the following: {{{ diff -up mutt-1.5.21/imap/imap.c.syncdebug mutt-1.5.21/imap/imap.c --- mutt-1.5.21/imap/imap.c.syncdebug 2012-03-27 10:05:44.978962551 +0200 +++ mutt-1.5.21/imap/imap.c 2012-03-27 10:05:54.223252267 +0200 @@ -1128,7 +1128,7 @@ static int sync_helper (IMAP_DATA* idata char buf[LONG_STRING]; - if (!mutt_bit_isset (idata->ctx->rights, right)) + if (!idata->ctx || !mutt_bit_isset (idata->ctx->rights, right)) return 0; if (right == M_ACL_WRITE && !imap_has_flag (idata->flags, name)) }}} I know this doesn't fix the issue itself, but I still think it can be sufficient here. Thanks for consideration and any comments are welcome. {{{ [1] https://bugzilla.redhat.com/show_bug.cgi?id=691719 [2] https://bugzilla.redhat.com/show_bug.cgi?id=801277 [3] https://bugzilla.redhat.com/show_bug.cgi?id=640453 }}}" hhorak 3570 "use of socat with ""tunnel"" hang forever" mutt 1.5.21 defect mutt-dev infoneeded_new 2012-03-28T08:36:07-07:00 2012-12-31T07:13:02-08:00 "Using debian wheezy package mutt 1.5.21-5, and getting the same result with /usr/bin/mutt and /usr/bin/mutt-org using set tunnel='socat STDIO SOCKS4A:tor.example.com:imap.gmail.com:imaps,socksport=9100' gives the following output when running mutt -d 5: Connecting with ""socat STDIO SOCKS4A:tor.example.com:imap.gmail.com:imaps,socksport=9100""... Connected to imap.gmail.com:993 on fd=42 imap_cmd_step: grew buffer to 512 bytes and wait forever until I kill the socat process. A direct connection to the imap server works fine. For the same kind of problematic, fetchmail uses the ""plugin"" parameter with the same ""socat ..."" argument and succeeds in establishing a connection through the tor node and fetching mails from the IMAP server. The difference I spot is that fetchmail uses one socketpair() where mutt uses two pipe(). When I modify the tunnel_socket_read() and tunnel_socket_write() functions in mutt_tunnel.c with mutt_message() to print in the debug log what is read from or written to the tunnel, nothing appears. It seems that nothing is sent through the tunnel. That would be nice if someone with a good understanding of this code could fix this. thanks " pierrem 3582 smtp_auth_sasl: error base64-decoding server response mutt 1.5.21 defect mutt-dev infoneeded_new 2012-05-21T23:24:15-07:00 2012-07-06T23:44:03-07:00 "mutt can't send email version : mutt 1.5.21 host: smtp.163.com (gmail test ok) command like this:echo ""testmail"" | mutt -d 5 -s ""test"" -e 'set smtp_url=""smtp://user:pas@smtp.163.com:25/""' to@sina.com {{{ System: Linux 2.6.37.6-0.11-desktop (i686) ncurses: ncurses 5.7.20101009 (compiled with 5.7) compile options： -DOMAIN +DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP -USE_IMAP +USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS +USE_SASL -USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID -USE_HCACHE }}} log: {{{ [2012-05-22 14:12:58] Mutt/1.5.21 (2010-09-15) debugging at level 5 [2012-05-22 14:12:58] Reading configuration file '/usr/local/etc/Muttrc'. [2012-05-22 14:12:58] parse_attach_list: ldata = 0x80e49b0, *ldata = (nil) [2012-05-22 14:12:58] parse_attach_list: added */.* [9] [2012-05-22 14:12:58] parse_attach_list: ldata = 0x80e49b4, *ldata = (nil) [2012-05-22 14:12:58] parse_attach_list: added text/x-vcard [7] [2012-05-22 14:12:58] parse_attach_list: added application/pgp.* [2] [2012-05-22 14:12:58] parse_attach_list: ldata = 0x80e49b4, *ldata = 0x80f2a08 [2012-05-22 14:12:58] parse_attach_list: skipping text/x-vcard [2012-05-22 14:12:58] parse_attach_list: skipping application/pgp.* [2012-05-22 14:12:58] parse_attach_list: added application/x-pkcs7-.* [2] [2012-05-22 14:12:58] parse_attach_list: ldata = 0x80e49b8, *ldata = (nil) [2012-05-22 14:12:58] parse_attach_list: added text/plain [7] [2012-05-22 14:12:58] parse_attach_list: ldata = 0x80e49b4, *ldata = 0x80f2a08 [2012-05-22 14:12:58] parse_attach_list: skipping text/x-vcard [2012-05-22 14:12:58] parse_attach_list: skipping application/pgp.* [2012-05-22 14:12:58] parse_attach_list: skipping application/x-pkcs7-.* [2012-05-22 14:12:58] parse_attach_list: added message/external-body [4] [2012-05-22 14:12:58] parse_attach_list: ldata = 0x80e49bc, *ldata = (nil) [2012-05-22 14:12:58] parse_attach_list: added message/external-body [4] [2012-05-22 14:12:58] send.c:1214: mutt_mktemp returns ""/tmp/mutt-linux-008-1000-28292-13932838271170144133"". [2012-05-22 14:12:58] sendlib.c:2692: mutt_mktemp returns ""/tmp/mutt-linux-008-1000-28292-726912188748030617"". [2012-05-22 14:12:58] mwoh: buf[Subject: test] is short enough [2012-05-22 14:12:59] send.c:988: mutt_mktemp returns ""/tmp/mutt-linux-008-1000-28292-2054191190810729236"". [2012-05-22 14:12:59] mwoh: buf[Subject: test] is short enough [2012-05-22 14:12:59] Connected to smtp.163.com:25 on fd=4 [2012-05-22 14:12:59] 4< 220 gz-t-163smtp1.163.com SMTP Server for Netease [466] 529b9177-52e3-4e81-a5e4-a21fdf2ced48 [2012-05-22 14:12:59] 4> EHLO linux-008.site [2012-05-22 14:12:59] 4< 250-gz-t-163smtp1.163.com [2012-05-22 14:12:59] 4< 250-mail [2012-05-22 14:12:59] 4< 250-PIPELINING [2012-05-22 14:12:59] 4< 250-8BITMIME [2012-05-22 14:12:59] 4< 250-AUTH LOGIN PLAIN [2012-05-22 14:12:59] 4< 250-AUTH=LOGIN PLAIN [2012-05-22 14:12:59] 4< 250 STARTTLS 529b9177-52e3-4e81-a5e4-a21fdf2ced48 [2012-05-22 14:12:59] 4> STARTTLS [2012-05-22 14:12:59] 4< 220 2.0.0 Start TLS 529b9177-52e3-4e81-a5e4-a21fdf2ced48 [2012-05-22 14:12:59] ssl_check_preauth: hostname check passed [2012-05-22 14:12:59] X509_STORE_load_locations failed [2012-05-22 14:12:59] X509_verify_cert: unable to get local issuer certificate (20) [2012-05-22 14:12:59] [/serialNumber=p0JiiH1Hm6SVOaDND51IWyf9sq-PK1Td/C=CN/ST=Guangdong/L=Guangzhou/O=Guangzhou NetEase Computer System Co., Ltd./OU=MAIL Dept./CN=*.163.com] [2012-05-22 14:12:59] X509_STORE_load_locations failed [2012-05-22 14:12:59] ssl_check_preauth: signer check passed [2012-05-22 14:12:59] trusted: /C=US/O=GeoTrust, Inc./CN=GeoTrust SSL CA [2012-05-22 14:12:59] ssl_check_preauth: hostname check passed [2012-05-22 14:12:59] X509_STORE_load_locations failed [2012-05-22 14:12:59] ssl_check_preauth: signer check passed [2012-05-22 14:13:00] 4> EHLO linux-008.site [2012-05-22 14:13:00] 4< 250-gz-t-163smtp1.163.com [2012-05-22 14:13:00] 4< 250-mail [2012-05-22 14:13:00] 4< 250-PIPELINING [2012-05-22 14:13:00] 4< 250-8BITMIME [2012-05-22 14:13:00] 4< 250-AUTH LOGIN PLAIN [2012-05-22 14:13:00] 4< 250 AUTH=LOGIN PLAIN 529b9177-52e3-4e81-a5e4-a21fdf2ced48 [2012-05-22 14:13:00] SASL local ip: 192.168.0.111;45452, remote ip:113.108.225.9;25 [2012-05-22 14:13:00] External SSF: 128 [2012-05-22 14:13:00] External authentication name: tczengming [2012-05-22 14:13:00] 4> AUTH LOGIN [2012-05-22 14:13:00] 4< 334 VXNlcm5hbWU6 529b9177-52e3-4e81-a5e4-a21fdf2ced48 [2012-05-22 14:13:00] smtp_auth_sasl: error base64-decoding server response. [2012-05-22 14:13:01] mutt_free_body: unlinking /tmp/mutt-linux-008-1000-28292-13932838271170144133. }}}" tczengming 3583 mutt-1.5.21: extract-keys does not extract PGP keys from S/MIME signed mail mutt defect mutt-dev new 2012-05-23T11:54:06-07:00 2012-05-23T11:54:06-07:00 "{{{ Package: mutt Version: 1.5.21 Severity: normal -- Please type your report below this line When viewing a mail with a PGP key attachment named *.asc but with MIME type text/plain that has been signed with S/MIME (weird combination, I know, but my bank sends this stuff and I think it should work), the extract-keys command correctly extracts the S/MIME certificate but ignores the PGP key. Just a minor annoyance as people who use mutt for this kind of stuff will probably know what to do, but perhaps mutt should just try all candidate attachments in this case instead of quitting after the first one. -- System Information System Version: Linux aldous 2.6.38-xen #2 SMP Mon Nov 28 17:45:50 GALT 2011 x86_64 AMD Phenom(tm) II X6 1090T Processor AuthenticAMD GNU/Linux -- 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 x86_64-pc-linux-gnu-gcc Using built-in specs. COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3/x86_64-pc-linux-gnu-gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.5.3/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.5.3 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.5.3/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.5.3/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/include/g++-v4 --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec --disable-fixed-point --without-ppl --without-cloog --disable-lto --enable-nls --without-included-gettext --with-system-zlib --disable-werror --enable-secureplt --enable-multilib --enable-libmudflap --disable-libssp --enable-libgomp --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.5.3/python --enable-checking=release --enable-java-awt=gtk --enable-languages=c,c++,java,objc --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-targets=all --with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.5.3-r2 p1.2, pie-0.4.7' Thread model: posix gcc version 4.5.3 (Gentoo 4.5.3-r2 p1.2, pie-0.4.7) - CFLAGS -Wall -pedantic -Wno-long-long -Os -march=amdfam10 -pipe -fomit-frame-pointer -fno-ident -fforce-addr -- Mutt Version Information Mutt 1.5.21 (2010-09-15, Gentoo 1.5.21-r9) Copyright (C) 1996-2009 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.6.38-xen (x86_64) ncurses: ncurses 5.9.20110404 (compiled with 5.9) libidn: 1.24 (compiled with 1.24) hcache backend: tokyocabinet 1.4.47 Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK +USE_POP +USE_NNTP +USE_IMAP +USE_SMTP -USE_SSL_OPENSSL +USE_SSL_GNUTLS +USE_SASL -USE_GSS +HAVE_GETADDRINFO -HAVE_REGCOMP +USE_GNU_REGEX +COMPRESSED +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/spool/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc/mutt"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. fg.sidebar-dotpathsep ar.sidebar-utf8 sidebar fg.gpg_smime_output patch-1.5.11.vk.pgp_verbose_mime cd.trash_folder.3.4 dgc.subjrx fg.change_folder_next fg.smarttime vvv.initials vvv.quote vvv.nntp dgc.xterm.titles.v3 patch-1.5.20hg.pdmef.progress.vl.2 rr.compressed patch-1.5.4.lpr.collapse_flagged Lukas P. Ruf }}} " matthias@… 3597 more feedback on wrong GPG keys mutt defect me accepted 2012-11-01T06:16:27-07:00 2012-12-16T20:50:58-08:00 "The following lines in pgpkey.c: 949 for (k = keys; k; k = kn) 950 { 951 kn = k->next; 952 if (abilities && !(k->flags & abilities)) 953 continue; made my life miserable, because somehow I couldn't use a key for encryption. Mutt kept asking for the key ID. It would be nice if mutt displays an error like ""key not suitable for encrypting"" or ""Key expired"". " miekg 3623 line after full-length line vanishes mutt 1.5.21 defect mutt-dev new 2013-01-17T07:23:48-08:00 2013-03-16T03:37:13-07:00 "Running mutt 1.5.21 (2010-09-15) in an 80 character wide xterm, the line after a line of length 80 characters is blank. I was wondering why gnome.bugzilla.org comment messages looked odd: --- Comment #6 from Patrick Welche 2013-01-17 12:44:36 UTC --- I have finally removed enough spaghetti to add support for at-spi2 in dasher git-head. ""I have... dasher"" is not displayed. If I edit the raw message and say change the last ""---"" to ""--"", or if I widen the xterm, the line reappears." prlw1 3633 Hang during SMTP email submission SMTP defect me assigned 2013-02-01T09:11:37-08:00 2013-02-07T19:12:23-08:00 "I'm experiencing a number of ways of death or silent failure for which I'm going to submit a number of separate bug reports. Here's #1. In .muttrc I've defined: set smtp_url=smtp://rbaechle:xxxafoadsf!@mail3pops.myblurb.org:5225 Note that the password is incorrect. When sending out an email, I get: This certificate belongs to: mail3pops.myblurb.org mail3pops.myblurb.org Domain Control Validated This certificate was issued by: Go Granny Secure Certification Authority GoGranny.com, Inc. http://certificates.gogranny.com/repository Scottsdale Arizona US This certificate is valid from Wed, 26 May 2010 14:40:34 UTC to Wed, 20 Jun 2012 12:33:15 UTC SHA1 Fingerprint: adc8 3b19 e793 491b 1c6e a0fd 8b46 cd9f 32e5 92fc MD5 Fingerprint: 68b3 29da 9893 e340 99c7 d8ad 5cb9 c940 WARNING: Server certificate has expired (All domain / host names and checksums changed.) And Mutt is asking: (r)eject, accept (o)nce After I hit `o', I see ""SASL authentication failed"", then Mutt is hanging forever. strace is show it hanging in ""recvfrom(3, "" It seems I'm hitting this only with the combination of expired certificate and incorrect password. I'm hitting this with the Fedora 17 package mutt-1.5.21-12.fc17.x86_64." ralf 3640 Hangs on index view when connected with gmail imap server IMAP 1.5.21 defect brendan new 2013-04-24T08:43:26-07:00 2013-04-24T08:45:08-07:00 "Randomly hangs when connected with gmail When running 'strace' on the hanged mutt pid(983 in this example) I get: $ sudo strace -p 983 Process 983 attached - interrupt to quit recv(3, which netstat shows to be the fd representing the IMAP connection. I also ran: $ cat /proc/983/fdinfo/3 pos: 0 flags: 02000002 According to 'dalias'(#mutt on freenode) this bug seems to be related to a change google made in their ssl implementation about a week ago. " tarruda 3641 Latest commit causes mutt to quit after failed password attempt on OSX 10.8.3. IMAP defect brendan new 2013-04-24T22:25:55-07:00 2013-04-25T09:49:41-07:00 " Mutt from tip, OSX 10.8.3. Suddenly, after the April 16 commit, the following occurs (never once happened before): I do 'mutt' at the prompt to login to the IMAP server holding my mail (it's Zimbra). Next I type the incorrect password (I have $imap_pass unset). Next mutt says ""Zimbra IMAP server terminating connection"" (or something very similar). Then that message disappears and I see ""Login failed"". So far, so good. This is as it has always been and how it should be. But after the Apr 16th commit, this is followed up by *mutt* quitting, and after it's quit I see output between the last bash prompt and the new one: ""Login failed"". Formerly, mutt wouldn't quit, and the ""Login failed"" message *inside* mutt would stay there until I hit another key. I could then do, for example ""c="" to get a fresh password prompt. This only seems to happen on the account that uses Zimbra. Gmail and my other accounts (which is either Courier or Dovecot) don't exhibit this. And I've just verified that there is no problem with commit 4c5163. It's d3096e that's done this. " balderdash 3642 Missing header when building against S-Lang build defect mutt-dev new 2013-05-03T11:41:21-07:00 2013-05-03T12:03:40-07:00 "The following: {{{ ./prepare \ --prefix=/usr \ --sysconfdir=/etc \ --enable-gpgme \ --enable-hcache \ --with-slang=/usr \ --with-regex \ --with-idn make }}} yields {{{ crypt-gpgme.c: In function ‘init_common’: crypt-gpgme.c:4369:15: error: ‘true’ undeclared (first use in this function) has_run = true; }}} The following patch ''solves'' the problem: {{{ diff -r d498f0e91914 crypt-gpgme.c --- a/crypt-gpgme.c Mon Mar 04 04:14:43 2013 +0000 +++ b/crypt-gpgme.c Sat Mar 23 11:58:04 2013 +0100 @@ -39,6 +39,7 @@ #include #include #include +#include #include #include #include }}}" baskerville 2988 Mutt should recognize tab (width) display enhancement mutt-dev new 2007-11-19T05:59:19-08:00 2009-06-30T07:14:33-07:00 In mutt_strwidth() there's a check for printable chars which excludes tab chars resulting in a width of 1. However, this is likely not the display width resulting in wrong wrapping and possibly other undesired effects. pdmef 3086 Add NNTP support mutt enhancement mutt-dev new 2008-07-01T12:14:53-07:00 2008-07-01T13:48:34-07:00 "All newsreaders sucks, mutt could just suck less if it had NNTP support =) Here is a widely used patch for it: http://www.fiction.net/blong/programs/mutt/#nntp It would be great if you merge it to upstream. Thank you!" llucax 3210 Feature Request: IMAP keywords IMAP enhancement brendan new 2009-03-30T07:59:39-07:00 2010-08-04T03:10:18-07:00 "I think it'd be so useful being able to manage IMAP keywords (section 2.3.2 of the INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 [1]; also there's a draft of Common IMAP keywords [2]). It'd be nice to create, remove, and to know the differents keywords an email have. In addition it'll be great to list them, so someone can create ""virtual folders"" based on keywords. [1] http://www.ietf.org/rfc/rfc3501.txt [2] http://tools.ietf.org/id/draft-melnikov-imap-keywords-03.txt" alovse 3344 set smtp_ehlo_name mutt 1.5.20 enhancement mutt-dev infoneeded_new 2009-10-15T20:10:58-07:00 2010-08-24T10:21:50-07:00 It would be great to have a configuration option to set the name used for EHLO regardless of my current hostname/domainname. chaoflow 3355 """mode-hook"", for mode-specific settings" mutt enhancement mutt-dev new 2009-11-21T14:45:33-08:00 2009-11-21T14:45:33-08:00 "I'd like to set some settings differently depending on mutt's mode (pager, index, compose, ...). The most natural solution for this seems like a mode hook, using the same names as ""bind"", allowing the same comma-separated syntax with the addition of ! for negation (all modes except these). To give a simple example, the following should turn off help for the pager and index, but leave it on everywhere else: mode-hook pager,index 'set help=no' mode-hook !pager,index 'set help=yes'" josh 3361 Help should list most used operations first mutt enhancement mutt-dev new 2009-12-10T20:14:33-08:00 2009-12-10T20:14:33-08:00 When viewing help, it should show the most used operations (those that appear in the help line at the top if visible) at the top, followed by the bound then unbound commands as usual. josh 3382 RFE: auto-collect email addresses for future use mutt enhancement mutt-dev new 2010-02-17T05:35:35-08:00 2010-02-17T09:10:05-08:00 "This is a request for enhancement. Currently Mutt does not pick up and collect any addresses of emails that comes in. This patch enables the collecting feature. When user opens email, the email addresses will get stored in alias file for its future use. Take note that Mutt does not automatically refer to what's in alias file when it gets started. Users should make sure to source alias file by stating source command on rc file. Otherwise this patch will end up creating duplicate entries in alias file. " umeyatakuma 3383 RFE: disregard email from auto-collection if matches specified regex pattern mutt enhancement mutt-dev new 2010-02-17T05:47:02-08:00 2010-02-17T05:51:38-08:00 #3382 auto-collects email. With this patch users can disregard email addresses from getting auto-collected if it matches regex pattern specified in rc file. umeyatakuma 3408 Progress indicator when closing/changing mailbox. mutt enhancement mutt-dev new 2010-04-24T02:36:02-07:00 2010-08-09T13:37:02-07:00 "Closing or changing mailbox which has a lot of new messages can take some time, during which the user is not offered any feedback. A progress indicator similar the the one displayed as the mailbox is opened would reassure the user that mutt is not hanging. Thanks" vext01 3420 option to write fcc only after sendmail exits successfully mutt 1.5.21 enhancement mutt-dev new 2010-06-14T01:36:33-07:00 2011-07-01T06:44:49-07:00 "It would be nice if mutt grew an option that allowed me to toggle between (in shell pseudo-code): a. fcc && sendmail b. sendmail && fcc The current behaviour is (a.), but some of us would really like to only write a $record of a message if it has actually been sent. See also: http://bugs.debian.org/584264 and http://bugs.debian.org/264973:" madduck 3422 Do not remove temporary files when viewing attachments mutt 1.5.20 enhancement mutt-dev new 2010-06-16T04:33:50-07:00 2010-06-17T16:55:34-07:00 "When you press enter on an attachment, mutt saves it to a temporary file and spawns the viewer, passing it the filename as $1. When the viewer exits, mutt removes the file. I can think of three reasons not to do this: - Some viewers, like ooffice or iceweasel, return control to their caller before the application has actually started. In such cases, it can happen that the file is gone by the time the viewer tries to open it. - I might inadverently edit an image or document I received as an attachment and risk losing my changes if I don't save to a new name. To guard against the first, mutt could delay deleting by a few seconds. To guard against the second, mutt could check a timestamp, size, or hashsum, or combination thereof, and only delete if those have not changed. However, I think mutt should just not delete the temporary file, if it's an attachment. /tmp is set to autoclean itself on reboot anyway, and tmpreaper is used wherever this doesn't suffice. Plus, disk space is getting bigger (and so is /tmp), so I don't see the need to clean up " madduck 3464 Provide means to classify addresses expanded from aliases mutt enhancement mutt-dev new 2010-10-15T00:04:37-07:00 2010-10-17T22:14:15-07:00 "I am heavily using the feature of muttaliases, by which you can expand an alias name to a list of people, e.g. {{{ alias myteam alex barbara charlie dorothee }}} It would be really nice if I could somehow extend this so that if I send a message to myteam, another address is always added to the CC, e.g. {{{ alias myteam alex barbara charlie dorothee -c eric fiona }}} Obviously, if 'myteam' is used in a CC field, then eric and fiona would also be in CC. I realise this can probably be done with send-hooks, but I would find this approach cleaner." madduck 3465 imap4 partial fetch request mutt enhancement mutt-dev new 2010-10-17T21:18:44-07:00 2010-10-17T21:43:51-07:00 "Mutt is the best! However, it seems that there are only two major IMAP4 features mutt lacks so far: 1) The capability to fetch a tex/html part of a multipart message (by default) and then being able to retreive any of the individual MIME parts (or portions if possible) of the message (e.g. any attachment) upon request. 2) When searching outside of message headers (say with the ""~b"" key) it is done by downloading each message from the given mailbox. The search maybe problematic on big mailboxes and/or with thin bandwidth. It would be nice to be able to run an imap4 server-side search. Thanks a lot for the great work!" mutt_rocks 3471 utf-8 not detected mutt 1.5.20 enhancement mutt-dev new 2010-11-12T10:04:43-08:00 2010-11-23T10:40:23-08:00 "I wanted to setup random signature with custom fortunes (using fortune), the problem was that mutt was treating my native characters as binary data and converted them to escape sequiences... My localization environment LC_COLLATE=lv_LV.UTF-8 LC_TIME=lv_LV.UTF-8 LC_CTYPE=lv_LV.UTF-8 LC_MONETARY=lv_LV.UTF-8 LC_NUMERIC=lv_LV.UTF-8 LC_MESSAGES=en_GB.UTF-8 (Don't ask, why I mix them, I need to) I fixed problem by setting set charset = ""utf-8"" however, I think mutt should auto-detect that and manual says just that: http://www.mutt.org/doc/devel/manual.html#charset-handling Using mutt 1.5.21 on FreeBSD " killasmurf86 3519 Select nearest message when changing filters mutt 1.5.20 enhancement mutt-dev new 2011-05-26T04:31:15-07:00 2011-05-26T04:39:21-07:00 "When a message is visible before and after changing mutt's current message limiting filter, the row cursor remains on the same message, but if the message does not exist, the cursor is reset to the top-most message. Instead, the nearest message without rolling over to the top of the screen should be selected. This could be made an optional setting using something like filtered_message_selection (a terrible name) that could be set to ""off"", ""before"", ""after"" to determine if the nearest message before or after is selected. Another variable, ""limit_rollover"", would be used to determine whether or not mutt was allowed to wrap around to the next message if using ""before"" at the top of the mailbox or ""after"" at the end of the mailbox." ericpruitt 3532 Use $SHELL when running mailcap-related commands mutt enhancement mutt-dev new 2011-07-18T03:00:02-07:00 2011-07-20T03:19:09-07:00 "Mutt should run mailcap-related commands (and possibly all commands, in which case the change could be done in system.c) with the user's shell (provided by $SHELL, else his login shell?) instead of /bin/sh. The reason is that /bin/sh is very limited and doesn't allow the user to provide a file to source in order to dynamically update the environment (for instance, zsh will source the user's .zshenv file). This is needed when running Mutt in GNU Screen across X11 sessions: updating the XAUTHORITY value is necessary before running an X application. Notes: * Some other programs already use $SHELL (etc.) instead of /bin/sh for running commands (e.g. ssh, gdb). * This can be regarded as incompatible with the mailcap description in the mailcap(5) man page (at least under Debian), which says that system() is used, but anyway Mutt is already somewhat incompatible as it doesn't use system(), and I've reported a bug to change that: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634254" vinc17 3560 printf statement in mbox-hook mutt enhancement mutt-dev new 2012-01-17T01:56:38-08:00 2012-01-17T01:56:38-08:00 "A while ago, there was a patch that allowed mbox-hook to have printf-liek statements. This was really useful for archiving emails in different directories with a date in the directory name. Is this patch still around or has it been ported to the development version?" kierun 3572 Mutt doesn't know popular audio formats mutt 1.5.21 enhancement mutt-dev new 2012-04-10T10:27:21-07:00 2012-05-11T10:16:49-07:00 "After realizing in disbelief that Mutt had sent an mp3 attachment with MIME type 'application/octet-stream', I found the 'mime.types' file to be severely lacking in the audio department. This sucks more - and not less - than any other current mail client. The following lines must be added to the 'mime.types' file in order to reduce said suction: audio/mpeg mp3 mp2 audio/x-flac flac audio/ogg ogg oga audio/aac m4a aac This will provide correct MIME types for popular and relatively-popular audio formats." dnied 3586 "make ""simple search keywords"" optional" mutt enhancement mutt-dev new 2012-06-04T06:16:47-07:00 2012-06-04T06:16:47-07:00 "Simple search keywords should be made optional. Even though there is a way to avoid them, e.g. ""[f]lag"" instead of ""flag"", one can easily forget they exist if one never uses them (one can always use the pattern modifier, which works in more contexts), and searches can silently fail for such an obscure reason. I've spent some time wondering why simple search wasn't working on ""flag"" and ""tag"", and started to think it was no longer working at all (yes, it really happened that these were the two words I was searching for)." vinc17 3620 folder list does not respect current folder setting mutt 1.5.21 enhancement me accepted 2013-01-03T11:16:43-08:00 2013-01-03T12:32:13-08:00 "I am using folder-hooks to manager multiple mail accounts. {{{ # Switch to default account on startup. source $my_mutt_dir/identity_server1 # folder hooks to load custom configuration folder-hook 'imap.server1' 'source $my_mutt_dir/identity_user1' folder-hook 'imap.server2' 'source $my_mutt_dir/identity_user2' # bind the accounts to fn keys macro index 'imaps://imap.server1' macro index 'imaps://imap.server2' }}} When I start mutt and type 'c' to change-folder and '?' to get the folder list, the folders of the current account are displayed correctly. However, if I change to the server2 using the key and type 'c' + '?' again, mutt tries to retrieve the folder list from server1 and fails since it does not use the correct settings for imap_user/imap_pass. My identity_userN files contain these values (all imap account settings are defined for the corresponding server): {{{ # basic identity set realname = """" set from = """" alternates """" set hostname = """" set signature = """" # IMAP account settings set imap_user = """" set imap_pass = """" set folder = """" set spoolfile = """" mailboxes = """" set mbox = """" set record = """" set postponed = """" # SMTP mailing configuration (for sending mail) set smtp_url = """" }}} Expected behaviour: after hitting 'c' + '?' the folders on the current server are shown." yminus 3628 Woudl liek to have sendmail variable usable when smtp_url set mutt 1.5.20 enhancement mutt-dev new 2013-01-23T03:37:14-08:00 2013-01-23T03:37:14-08:00 "Hi, I would like to pre-filter an already formatted message before sending, like one does when setting $sendmail to a command different from the raw sendmail of the system, like they do in [http://dev.mutt.org/trac/wiki/ConfigTricks/CheckAttach] (i.e. having the whole formatted message sent through a pipe to the $sendmail command). However, as using the SMTP extension renders the $sendmail variable useless, there is no (easy) way to do this. The fact is I am planning on writing an extension and with the standard setting ($sendmail useful) it works pretty easily but if smtp_url is set, then it is a terrible hassle. Thanks." pfortuny 3150 garbage display with combining characters and Mutt's wc functions (--without-wc-funcs) charset 1.5.20 1.6 defect me accepted 2009-01-06T06:08:18-08:00 2013-01-17T03:54:42-08:00 When building Mutt with --without-wc-funcs, I get garbage output on combining characters. vinc17 3638 Compilation errors for 1.6 mutt 1.5.21 1.6 defect mutt-dev new 2013-03-03T13:10:49-08:00 2013-04-20T15:21:05-07:00 "FreeBSD 8.3 i386 mutt 1.5.21 hg (today's daily) Here are all the compile errors on the above with hg to look through for upcoming 1.6 release... imap.c:283: warning: dereferencing type-punned pointer will break strict-aliasing rules imap.c:1355: warning: dereferencing type-punned pointer will break strict-aliasing rules message.c:63: warning: unused variable 'buf' main.c:75: warning: string length '558' is greater than the length '509' ISO C90 compilers are required to support ascii.h:35: warning: 'ascii_tolower' declared inline after being called ascii.h:35: warning: previous declaration of 'ascii_tolower' was here pop_lib.c:67: warning: implicit declaration of function 'ntohs' lib.c:569: warning: warning: mktemp() possibly used unsafely; consider using mkstemp() byteorder(3) says ntohs is in either: #include #include mkstemp(3) actually creates the file returning fd, thus securing against races. I'd consider having configure test for it and implementing it in muttlib.c. I also get this difference when using LDFLAGS=-static ... < checking for idna_to_unicode_8z8z... yes > checking for idna_to_unicode_8z8z... no < checking for idna_to_ascii_8z... yes < checking for idna_to_ascii_lz... yes > checking for idna_to_ascii_8z... no > checking for idna_to_ascii_lz... no I can pull and retest as needed. Thanks. " grarpamp 3310 Overhaul new mail reporting mutt 1.6 task mutt-dev new 2009-07-29T21:46:04-07:00 2010-09-12T19:54:21-07:00 "Support notification for both new and old mail (configurable) for all mailbox types. See NewMailHandling. There are two separate issues: one is distinguishing between new mail and old mail, and the other is being able to tell whether a mailbox has changed since it was last opened, without regard to whether the mail in it is new or old. For problem 2 (has the mailbox changed?) I think we'll need a function for each mailbox type that returns a type-specific cookie (e.g., for mbox timestamp+size, for IMAP UIDVALIDITY+UIDNEXT, for maildir perhaps the number of files under new and the name of the most recent under cur). None of these should be more expensive to calculate than what the buffy check already does." brendan 2938 mutt freezes some times when accessing imap folders or messages IMAP 2.0 defect new 2007-08-03T21:57:38-07:00 2010-12-30T16:12:28-08:00 "Mutt sometimes hangs when fetching a message, or opening a folder while fetching headers from an imap server. The imap server is Cyrus IMAP4 2.2.12-Invoca-RPM-2.2.12-8.1.RHEL4. This happens also with mutt 1.5.12 on one machine, as well as with mutt 1.5.13. This happens occasionally, not that often, but enough to be frustrating since mutt has to be restarted and changes to the mail folder are lost. Several times a day. Mutt won't respond except for ctl-Z to stop it, then the mutt process must be killed. In one case I collected a debug log from mutt -d, which showed that mutt has frozen part way through downloading an attachment. No error messages are given, the log simply stops part way through outputing the attachment to the log file. Well I'm not sure this is mutt or cyrus imapd but not sure how to tell the difference and the imap server is not accessible to me. " b.macdonald 2946 mutt ignores commands when new mail arrives mutt 1.5.14 2.0 defect mutt-dev new 2007-08-23T15:57:43-07:00 2008-07-18T14:57:58-07:00 Mutt will abort the execution of various commands when new mail arrives in an mbox. mpm 2958 mutt-1.5.16: mutt crash at start when enabling header caching in nsf directory with a (non-root) install mutt 2.0 defect mutt-dev new 2007-09-16T04:16:37-07:00 2008-10-19T16:20:45-07:00 " {{{ Package: mutt Version: 1.5.16 Severity: normal -- Please type your report below this line I install mutt on a remote machine, which I access over ssh and have no root privilege. I installed mutt with root directory $HOME. The inbox is on an imaps server accessed, and the saved mail boxes are in my home directory $HOME mounted on NFS. When I enable header caching, the mutt crash when accessing the imaps inbox, but not when reading the mbox folders on my NFS mounted home directory. This happen whether I put the header cache folder on NFS home directory or in non NFS mounted /tmp directory. Curiously, this does not happen on my home computer when accessing the same remote imaps inbox with header cache enabled. There I installed mutt as root on /usr/local/ Jiang -- 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/i486-linux/3.3.5/specs Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --enable-__cxa_atexit --with-system-zlib --enable-nls --without-included-gettext --enable-clocale=gnu --enable-debug --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i486-linux Thread model: posix gcc version 3.3.5 (Debian 1:3.3.5-13) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.16 (2007-06-09) Copyright (C) 1996-2007 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.27-3-686-smp (i686) ncurses: ncurses 5.4.20040208 (compiled with 5.4) Compile options: -DOMAIN -DEBUG +HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_INODESORT +USE_POP +USE_IMAP +USE_SMTP -USE_GSS +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL +HAVE_GETADDRINFO -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""mailbox"" PKGDATADIR=""/home/jqian//share/mutt"" SYSCONFDIR=""/home/jqian//etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. --- Begin /home/jqian//etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less ${prefix}/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less ${prefix}/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less ${prefix}/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" --- End /home/jqian//etc/Muttrc }}}" jqian@… 3038 mutt cannot communicate with archiveopteryx IMAP 1.5.17 2.0 defect brendan infoneeded 2008-03-13T14:07:00-07:00 2009-06-06T23:00:15-07:00 "Hi, I've send this to the user list and was told that this might actually be a bug. The problem I see is that mutt hangs when trying to open any imap box I have on an archiveopteryx server. Mutt works fine against a locally running dovecot, but also other imap clients work fine with the archiveopteryx server. I've tried to produce useful debug information using mutt -d2, the generated file is attached (without a few lines about mailbox names that I cannot post here)." apaku 3074 Mutt hangs indefinitely IMAP 1.5.18 2.0 defect brendan accepted 2008-06-09T17:01:17-07:00 2009-06-06T23:04:03-07:00 "On many occasions, I find that an unattended mutt (1.5.17+20080114-1+b1 from Debian) will hang indefinitely. Never having time to debug it, I usually kill it and restart it, but today I let it run in strace until it happend. Here's what the end of the strace looks like - it seems to get an ERESTARTSYS while reading from the imaps socket! ERESTARTSYS is reserved as a signal between drivers and the kernel signal handling code and is, theoretically, never supposed to make it to userspace. Thus, this is quite odd. I'm happy to add ltraces or whatever else may be useful.... {{{ write(1, ""\r\33[17B\33[37m\33[40mFetching message""..., 76) = 76 write(1, ""\33[79;29H\33[37m\33[40m1834/1838 (99%""..., 54) = 54 gettimeofday({1212696193, 854853}, NULL) = 0 getrusage(RUSAGE_SELF, {ru_utime={0, 812050}, ru_stime={0, 236014}, ...}) = 0 time(NULL) = 1212696193 times({tms_utime=81, tms_stime=23, tms_cutime=1, tms_cstime=2}) = 1734919932 gettimeofday({1212696193, 855156}, NULL) = 0 getrusage(RUSAGE_SELF, {ru_utime={0, 812050}, ru_stime={0, 236014}, ...}) = 0 time(NULL) = 1212696193 times({tms_utime=81, tms_stime=23, tms_cutime=1, tms_cstime=2}) = 1734919932 send(4, ""\27\3\1\0\373*\341\374\221\t.p\233T*Y\354\0\223\303><\205""..., 256, 0) = 256 _llseek(5, 0, [0], SEEK_SET) = 0 recv(4, ""\27\3\1\v\33"", 5, 0) = 5 recv(4, ""x\204\315|I\203Ph`\317\205-\356\16L\315S\3551\263\302N""..., 2842, 0) = 1383 recv(4, ""\246\212O\2675gm\364wR!\16\31\256\361\374\373\21\352u#""..., 1459, 0) = 1388 recv(4, 0x81d31d0, 71, 0) = ? ERESTARTSYS (To be restarted) --- SIGWINCH (Window changed) @ 0 (0) --- sigreturn() = ? (mask now []) recv(4, }}} - Phil" jaymzh 2056 Attempt re-connect when idle mailbox connection closes IMAP 2.0 enhancement brendan new 2005-09-06T15:38:34-07:00 2011-07-17T19:32:21-07:00 "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 remains idle for more than a few minutes. That can happen when the user returns to the mailbox after viewing a message for a long time. Currently, mutt automatically closes the mailbox when this happens. This makes mutt nearly unusable in this type of IMAP/network environment. The correct behavior is for mutt to attempt to reconnect to the mailbox. Mutt should only close the mailbox if the reconnect attempt - or several attempts - fails. This seems to be standard behavior for most IMAP email clients." gale@… 2928 Read mail while downloading it mutt 1.5.16 2.0 enhancement mutt-dev new 2007-07-01T14:55:57-07:00 2007-11-15T11:31:34-08:00 "Reason :- I use lot of emails forwarded to one mail account. So my mail gets clogged up. RFE description :- To be more efficient mutt user, it would be great if mutt could read the mail whilst the next one is being downloaded (I use POP3 service) so that I can read the mail that's downloaded immediately without waiting (IMHO mutt is blocking somwhere down the code, one possible way would be to have a seperate thread handle the display whilst the main code are working on the fetching part [just a thought. :)]) Mutt version :- I am using Mutt 1.5.16 (2007-06-09) on Ubuntu feisty and Debian etch machine. Cheers" nepbabu.cx 3128 Make IMAP expunged message handling faster IMAP 1.5.18 2.0 enhancement brendan new 2008-10-19T14:37:20-07:00 2008-10-19T14:37:20-07:00 cmd_parse_expunge walks the entire mailbox for every expunge message received. For large mailboxes, this is extremely slow. We want two fixes: 1. maintain a header hash by index number, and 2. avoid having to decrement the index number for following messages at every expunge message. We might maintain a side list of expunges received and use it to offset the index number of live messages. Or maybe we'll just adjust the later messages lazily, by recording our current position in the list and only adjusting offsets when we touch messages after that point. Needs some thought. brendan 3423 Fetch headers X pages at a time. mutt 2.0 enhancement mutt-dev new 2010-06-16T12:38:55-07:00 2010-08-10T17:20:19-07:00 "Hi, Frustrated with how long mutt takes to fetch headers, I profiled HEAD on my OpenBSD system. Opening a large (~11,000) mailbox (with no existing headers cached), take about 5 minutes or so. Looking at the profiling information it seems that much of the time is spent processing headers. So I wonder if there is a way to optimise this? Perhaps by fetching (for example) 3 pages worth headers at a time and if more are required, fetch the next 3 pages on demand. I'm attaching my profiling data for the above experiment. The IMAP server was gmail by the way, which probably is not helping. " vext01 3518 IDNA2008 support by libidn2 usage in mutt mutt 2.0 enhancement mutt-dev new 2011-05-22T05:23:15-07:00 2011-06-20T16:56:31-07:00 "At the moment, mutt only has IDNA2003 support by GNU libidn. As IDNA2003 was updated, changed and revised by IDNA2008, there's now GNU libidn2. Unfortunately IDNA2003 and IDN2008 are very different, thus the new library is also very different. Nevertheless I would like to see IDNA2008 support in mutt. As it is hard (and makes less to no sense) to support IDNA2003 and IDNA2008 in parallel, I would recommend to replace IDNA2003 by IDNA2008 support, which means that the requirement in the end switches over from libidn to libidn2 simply. GNU libidn2 upstream is http://www.gnu.org/s/libidn/#libidn2, the latest version at the moment is 0.5." rsc 3242 mutt: does not want to open dot subdirs via imap anymore browser 1.5.21 2.0 task lucki2791 accepted 2009-06-03T00:37:06-07:00 2012-05-13T17:43:59-07:00 "Forwarding from http://bugs.debian.org/530671 This bug seems to happen only with dovecot, which is using a dot (""."") as folder separator, particularly it happens *only if* the subdirs starts with a dot (INBOX.subdir is not considered), if you have a look at the .muttdebug0 attached it is clear that mutt is trying to open ""/boot"" and not "".boot"". How to reproduce: {{{ 1) open mutt, insert imap password, got the INBOX list 2) c? 3) select a subdir, press enter 4) error message: Invalid mailbox name }}} This happens only with 1.5.19 and we also tried to release a new version with the following two commits integrated: {{{ Prioritize the entered IMAP folder delimiter. http://dev.mutt.org/hg/mutt/rev/d6ee34f3ccaf Fix last commit http://dev.mutt.org/hg/mutt/rev/f76046ce4686 }}} Unfortuantely this did not change the behavior. I'm setting the priority as 'normal' and not 'minor' as I do usually because this is an 'important' bug on the debian side. " antonio@… 814 Translation: in Czech confirmation should be by pressing a not y. mutt 1.3.22.1i defect mutt-dev new 2001-10-10T21:59:25-07:00 1969-12-31T16:00:00-08:00 "{{{ Package: mutt Version: 1.3.22.1i Severity: normal -- Please type your report below this line Hi, when Czech locale are set, mutt offers in confirmation dialog options [Ano/Ne] (which is Yes/No in Czech). However, for confirmation it expects Y on stdin not A. Thanks Matej Cepl -- Mutt Version Information Mutt 1.3.22.1i (2001-08-30) Copyright (C) 1996-2001 Michael R. Elkins a dal¹í. Mutt je roz¹iøován BEZ JAKÉKOLI ZÁRUKY; dal¹í informace získáte pøíkazem `mutt -vv'. Mutt je volné programové vybavení. Roz¹iøování tohoto programu je vítáno, musíte ov¹em dodr¾et urèitá pravidla; dal¹í informace získáte pøíkazem `mutt -vv'. System: Linux 2.2.16-22 [using slang 10401] Pøelo¾eno s volbami: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_NNTP +USE_IMAP -USE_GSS +USE_SSL -USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +COMPRESSED +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/local/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" INEWS=""/usr/bin/inews -hS"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER Vývojáøe programu mù¾ete kontaktovat na adrese (anglicky). Chyby v programu oznamujte pomocí utility flea(1). Pøipomínky k pøekladu zasílejte na adresu (èesky). >How-To-Repeat: >Fix: }}}" Matìj Cepl 897 Mutt should write Bcc: list in saved messages mutt defect mutt-dev new 2001-12-03T20:25:28-08:00 2008-05-26T15:46:08-07:00 "{{{ Package: mutt Version: 1.3.23-4 Severity: wishlist [NOTE: this bug report has been submitted to the debian BTS as Bug#122173. Please Cc all your replies to 122173@bugs.debian.org.] From: Steve McIntyre Subject: Mutt should write Bcc: list in saved messages Date: Mon, 3 Dec 2001 01:21:48 +0000 Package: mutt Version: 1.3.23-4 Severity: wishlist Even if configured to not include a Bcc: header when sending mail (as in the default config, so exim does not show it), mutt should still write one in a locally-saved copy. I've just sent a mail to a large list of people, and the only way of recalling the recipients was to read the exim log. -- Steve McIntyre, Cambridge, UK. stevem@chiark.greenend.org.uk My home page ""Can't keep my eyes from the circling sky, +------------------ ""Tongue-tied & twisted, Just an earth-bound misfit, I..."" |Finger for PGP key >How-To-Repeat: >Fix: }}}" Marco d'Itri 1070 unable to delete included messages if one of the included message is pgp-signed/encrypted crypto 1.3.25i defect mutt-dev new 2002-02-26T02:23:18-08:00 2009-06-30T07:19:11-07:00 "{{{ Package: mutt Version: 1.3.25-2 Severity: normal I encountered this while receiving a mailing list digest. There was a number of pgp-signed messages in it. When I tried to delete some of the attched messages (it did not matter if they were signed or not), I got the message Deletion of attachments from PGP messages is unsupported. This digest is not a PGP message at all. I was able to reproduce this (just forwarded a signed message to myself and then tried to delete it). Maybe this is just by design or something? For me, it was a bit unexpected. Regards, -- Misha -- 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 cc Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs gcc version 2.95.4 20011002 (Debian prerelease) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.3.25i (2002-01-01) Copyright (C) 1996-2001 Michael R. Elkins É ÄÒÕÇÉÅ. Mutt ÒÁÓÐÒÏÓÔÒÁÎÑÅÔÓÑ âåú ëáëéè-ìéâï çáòáîôéê; ÄÌÑ ÐÏÌÕÞÅÎÉÑ ÂÏÌÅÅ ÐÏÄÒÏÂÎÏÊ ÉÎÆÏÒÍÁÃÉÉ ××ÅÄÉÔÅ `mutt -vv'. Mutt Ñ×ÌÑÅÔÓÑ Ó×ÏÂÏÄÎÙÍ ÐÒÏÇÒÁÍÍÎÙÍ ÏÂÅÓÐÅÞÅÎÉÅÍ. ÷Ù ÍÏÖÅÔÅ ÒÁÓÐÒÏÓÔÒÁÎÑÔØ ÅÇÏ ÐÒÉ ÓÏÂÌÀÄÅÎÉÉ ÏÐÒÅÄÅÌÅÎÎÙÈ ÕÓÌÏ×ÉÊ; ÄÌÑ ÐÏÌÕÞÅÎÉÑ ÂÏÌÅÅ ÐÏÄÒÏÂÎÏÊ ÉÎÆÏÒÍÁÃÉÉ ××ÅÄÉÔÅ `mutt -vv'. System: Linux 2.4.17 (i586) [using ncurses 5.2] ðÁÒÁÍÅÔÒÙ ËÏÍÐÉÌÑÃÉÉ: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP -USE_GSS -USE_SSL +USE_GNUTLS +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 +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" þÔÏÂÙ Ó×ÑÚÁÔØÓÑ Ó ÒÁÚÒÁÂÏÔÞÉËÁÍÉ, ÉÓÐÏÌØÚÕÊÔÅ ÁÄÒÅÓ . þÔÏÂÙ ÓÏÏÂÝÉÔØ Ï ÏÛÉÂËÅ, ÉÓÐÏÌØÚÕÊÔÅ ÐÒÏÇÒÁÍÍÕ flea(1). patch-1.3.24.rr.compressed.1 patch-1.3.24.appoct.2 patch-1.3.15.sw.pgp-outlook.1 patch-1.3.24.admcd.gnutls.1 Md.use_editor Md.paths_mutt.man Md.muttbug_no_list Md.use_etc_mailname Md.muttbug_warning Md.gpg_status_fd patch-1.3.25.cd.edit_threads.9.1 patch-1.2.xtitles.1 patch-1.3.23.1.ametzler.pgp_good_sign >How-To-Repeat: >Fix: }}}" mss@… 1076 mutt: fsync()s repeatedly when saving messages to different folder mutt defect mutt-dev new 2002-03-01T04:40:38-08:00 2009-01-25T06:19:53-08:00 "{{{ Package: mutt Version: 1.3.27-2 Severity: normal [NOTE: this bug report has been submitted to the debian BTS as Bug#136139. Please Cc all your replies to 136139@bugs.debian.org .] From: Erno Kuusela Subject: mutt: fsync()s repeatedly when saving messages to different folder Date: Thu, 28 Feb 2002 07:47:32 +0200 when i tag some messages and hit s to move them to a different folder, mutt seems fsync()s the destination folder file after writing each message (checked with strace). this makes working with many messages incredibly slow. -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux fabulous 2.4.9-ac5 #3 Wed Sep 5 05:01:06 EEST 2001 i686 Locale: LANG=C, LC_CTYPE=fi_FI Versions of packages mutt depends on: ii libc6 2.2.5-3 GNU C Library: Shared libraries an ii libncurses5 5.2.20020112a-3 Shared libraries for terminal hand ii libsasl7 1.5.27-2 Authentication abstraction library ii postfix [mail-transport- 1.1.3-1 A high-performance mail transport >How-To-Repeat: >Fix: }}}" Marco d'Itri 1083 Attaching tagged files - problem if cursor ends up on a directory mutt 1.3.25i defect mutt-dev new 2002-03-04T23:07:01-08:00 2005-10-19T10:13:20-07:00 "{{{ Package: mutt Version: 1.3.25i Severity: normal -- Please type your report below this line Hi I have auto_tag turned on and auto advance to next message feature. Bascially, when I go to attach 5 files say from a given directory, I hit tab twice to open that dir and then hit the T key for each of the files that I want to attach/ When done I just hit ENTER and usually it works as expected. However, if the last file that I hit T for has a directory after it (in the list), and because my auto advance feature puts the cursor on the line after the tagged file (i.e the directory) then hitting ENTER takes me down into the directory. viz. 17 * -rw-r--r-- 1 user1 group1 1956 Feb 27 15:42 wrapperprogram.dia 18 * -rw-r--r-- 1 user1 group1 17433 Mar 01 09:13 wrapperprogram.ps 19 drwxr-sr-x 2 user1 group1 4096 Mar 01 09:26 trash/ As you can see, I tag items 18 and 19 by hitting t and the cursor ends up on item 19, OK. Then I hit enter to say attach these 2 and mutt takes me to the directory trash/. Perhaps it is supposed to do this but it threw me at first. I guess the use of the enter key to say FINISHED or to say ENTER DIR is the problem? HTH Will -- -- Mutt Version Information Mutt 1.3.25i (2002-01-01) 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.9-13 (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=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. --- Begin /home/berrisw/.muttrc macro index \A ""!abook\n"" ""Abook"" macro pager \A ""!abook\n"" ""Abook"" set realname=""William Berriss"" set sendmail=""/usr/sbin/sendmail -oem -oi"" set spoolfile=imap://staff/INBOX set folder=imap://staff/INBOX set from=""William.Berriss@vil.ite.mee.com"" set alternates=""william.berriss@vil.ite.mee.com"" set history=100 set print_cmd=""mpage -P -1 -f -o -bA4"" ## -f = fold long lines set abort_nosubject=ask-yes set abort_unmodified=ask-yes set alias_file=""~/.mutt/.aliases"" source ~/.mutt/.aliases source ~/.mutt/.aliases-vil source ~/.mutt/.aliases-mitsubishi source ~/.mutt/.aliases-private set alias_format=""%2n %-20t %-30a %r"" unset allow_8bit unset arrow_cursor unset ascii_chars unset askbcc set askcc set attach_format=""%u%D%t%2n %T%.90d%> [%.7m/%.10M, %.6e, %s] "" set attach_split unset autoedit set auto_tag set beep set beep_new set bounce_delivered set charset=""iso-8859-1"" unset check_new set collapse_unread unset confirmappend set confirmcreate set copy=yes set date_format=""%a %b %d %H:%M (%Z)"" set default_hook=""((~f %s) !~P) | (~P ~t %s)"" set delete=ask-yes set edit_headers set editor=""vim -c 'set ruler formatoptions=tl expandtab tw=72 noautoindent' '+/^$' '+noh' "" set escape=~ set fast_reply source ~/.mutt/.keybindings # my key bindingsi source ~/.mutt/.fcc-save-hooks # my fcc and save hooks folder-hook =[^I] exec collapse-all set followup_to set force_name set forward_decrypt set forward_format=""Fwd: %s"" set forward_quote set weed unhdr_order * hdr_order From Date: From: To: Cc: Bcc: Fcc: Subject: set hdrs set help set hidden_host set history=150 set hostname=""staff.vil.ite.mee.com"" set imap_user=berrisw unignore * ignore * unignore date delivery-date to from: subject cc importance pgp set ignore_list_reply_to set include=yes set indent_string=""> "" set index_format=""%3C%?M?+& ?%Z %{%a %d %b %Y %H:%M} %-25.25F %-50.50s %?M?[%e/%E]&(%3c)?"" set ispell=""aspell -e -c"" set mail_check=600 unset mark_old set markers set mask="".*"" set mbox_type=Maildir unset metoo set menu_scroll unset mh_purge set mime_forward=ask-yes set move=no set pager=builtin set pager_context=1 set pager_format=""%Z [%C/%m] %-20.20n %-50.50s %> [%e/%E mesgs] %l lines (%c)"" set pager_index_lines=12 set pager_stop source ~/.mutt/gpg.rc # Start up with GnuPG by default set pgp_good_sign=""good"" set pgp_entry_format=""%4n %t%f %[%y/%m/%d] %4l/0x%k %-4a %2c %u"" unset pipe_decode unset pipe_split set postpone=ask-yes set postponed=""~/.mutt/.postponed"" set print=ask-no unset prompt_after set query_command = ""mutt_ldap_query2.pl -s staff.vil.ite.mee.com -s ldap-cc.vil.ite.mee.com -b dc=vil,dc=com '%s' 2> /dev/null"" set quit=ask-yes set quote_regexp=""^([ \t]*[>%:|])+"" # less inclusive, useful w/mail w/code set read_inc=1 unset read_only set recall=ask-no set record=""=spammers"" set reply_regexp=""^((re|aw|antw.):[ \t]*)*"" unset reply_self set reply_to=ask-yes set reverse_alias set reverse_name unset save_address set save_empty set save_name set shell=""bash"" set sig_dashes set signature=""~/.signature"" set smart_wrap set smileys=""(>From)|(:[-^]?[][)(><}{|/DP])"" color body brightgreen white ""<[Gg]>"" color body brightgreen white ""<[Bb][Gg]>"" color body red default "" >?[;:][-^]?[][)(><}{|/DP][)}]*"" set sort=threads set sort_aux=reverse-last-date-received set sort_re set status_chars="" *%A"" set status_format=""%v@%h:%f (Sort=%s) [%M/%m(%P of %LB)] Limit=%V %> [postponed=%p|n=%n|u=%u|t=%t]"" set status_on_top unset strict_threads set suspend set thorough_search set tilde set timeout=60 set tmpdir=""~/tmp"" set to_chars=""LTGCF"" unset uncollapse_jump unset use_8bitmime set use_domain set use_from set visual=""vim"" set wait_key set wrap_search set write_inc=1 color body magenta default ""[^ <]*:\/\/[^ >]*"" # for URLs color normal default default color hdrdefault red default color header green default ^(From|Subject): color signature cyan default color indicator black white color error brightred default color status green default color tree magenta default # the thread tree in the index menu color tilde magenta default color message red default color markers brightblue default color attachment magenta default color search default green # how to hilite searches in the pager color quoted cyan default # quoted text color quoted1 magenta default color quoted2 red default color quoted3 green default color quoted4 blue default color quoted5 brightcyan default color quoted6 magenta default color quoted7 red default color quoted8 green default color quoted9 cyan default color underline brightgreen default color index green default ~F color body magenta default ""((ftp|http|https)://|(file|news):|www\\.)[-a-z0-9_.:]*[a-z0-9](/[^][{} \t\n\r\""<>()]*[^][{} \t\n\r\""<>().,:!])?/?"" color body green default [-a-z_0-9.]+@[-a-z_0-9.]+ # e-mail addresses unhdr_order * # clear system defaults hdr_order Date: From: Old-Return-Path: Reply-To: Mail-Followup-To: To: Cc: Bcc: Delivered-To: Subject: In-Reply-To: X-Mailing-List: X-Operating-System: X-Mailer: User-Agent: my_hdr X-Operating-System: `uname -sr` on an `uname -m` source ~/.mutt/.scores --- End /home/berrisw/.muttrc --- Begin /etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /usr/share/doc/mutt-1.2.5i/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /usr/share/doc/mutt-1.2.5i/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /usr/share/doc/mutt-1.2.5i/manual.txt\n"" ""Show Mutt documentation"" set pgp_decode_command=""gpg %?p?--passphrase-fd 0? --no-verbose --batch --output - %f"" set pgp_verify_command=""gpg --no-verbose --batch --output - --verify %s %f"" set pgp_decrypt_command=""gpg --passphrase-fd 0 --no-verbose --batch --output - %f"" set pgp_sign_command=""gpg --no-verbose --batch --output - --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a? %f"" set pgp_clearsign_command=""gpg --no-verbose --batch --output - --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f"" set pgp_encrypt_only_command=""pgpewrap gpg -v --batch --output - --encrypt --textmode --armor --always-trust -- -r %r -- %f"" set pgp_encrypt_sign_command=""pgpewrap gpg --passphrase-fd 0 -v --batch --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f"" set pgp_import_command=""gpg --no-verbose --import -v %f"" set pgp_export_command=""gpg --no-verbose --export --armor %r"" set pgp_verify_key_command=""gpg --no-verbose --batch --fingerprint --check-sigs %r"" set pgp_list_pubring_command=""gpg --no-verbose --batch --with-colons --list-keys %r"" set pgp_list_secring_command=""gpg --no-verbose --batch --with-colons --list-secret-keys %r"" set pgp_getkeys_command="""" color hdrdefault red default color quoted brightblue default color signature red default color indicator brightyellow red color error brightred default color status yellow blue color tree magenta default # the thread tree in the index menu color tilde magenta default color message brightcyan default color markers brightcyan default color attachment brightmagenta default color search default green # how to hilite search patterns in the pager color header brightred default ^(From|Subject): color body magenta default ""(ftp|http)://[^ ]+"" # point out URLs color body magenta default [-a-z_0-9.]+@[-a-z_0-9.]+ # e-mail addresses color underline brightgreen default mono quoted bold set ispell=""/usr/bin/aspell --mode=email check"" --- End /etc/Muttrc Received: (at submit) by bugs.guug.de; 2 May 2002 09:02:29 +0000 From frederic.gobry@smartdata.ch Thu May 02 11:02:29 2002 Received: from smartdatapc1.epfl.ch ([128.179.50.2] helo=rhin.smartdata.ch) by trithemius.gnupg.org with esmtp (Exim 3.35 #1 (Debian)) id 173CTt-0005j7-00 for ; Thu, 02 May 2002 11:02:29 +0200 Received: (from fred@localhost) by rhin.smartdata.ch (8.11.1/8.11.1) id g42947W23513; Thu, 2 May 2002 11:04:07 +0200 Date: Thu, 2 May 2002 11:04:07 +0200 From: Frédéric Gobry Message-Id: <200205020904.g42947W23513@rhin.smartdata.ch> Subject: mutt-1.3.99i: tag- does not behave as expected To: submit@bugs.guug.de Package: mutt Version: 1.3.99i Severity: normal -- Please type your report below this line When I want to attach several files to a mail, I usually tag the files and type ;- to select the group of files as a whole. This works unless the cursor is located on a directory entry when I hit ;-. In that case, the action is not to select the tagged files, but to enter the directory and discard the previous selection, which is rather annoying... This is a small incoherency, but in such a great tool that it is very outstanding :-) -- 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-redhat-linux/egcs-2.91.66/specs gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.3.99i (2002-05-02) Copyright (C) 1996-2001 Michael R. Elkins et autres. Mutt ne fournit ABSOLUMENT AUCUNE GARANTIE ; pour les détails tapez `mutt -vv'. Mutt est un logiciel libre, et vous êtes libre de le redistribuer sous certaines conditions ; tapez `mutt -vv' pour les détails. System: Linux 2.4.18 (i686) [using slang 10202] Options de compilation : -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=""/usr/sbin/sendmail"" MAILPATH=""/var/spool/mail"" PKGDATADIR=""/usr/local/stow/mutt-1.3.99/share/mutt"" SYSCONFDIR=""/usr/local/stow/mutt-1.3.99/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER Pour contacter les développeurs, veuillez écrire à . Pour signaler un bug, veuillez utiliser l'utilitaire flea(1). --- Begin /home/fred/.muttrc set spoolfile = ""=Inbox"" auto_view text/html set nowait_key unignore x-swish set mbox_type = maildir set editor = ""emacsnw -f text-mode "" set reply_regexp = ""^(r[eé]p?\.?([\[0-9\]+])*|aw)[ \t]*:?[ \t]*"" set folder = ~/Mail color index white red ~F set mime_forward = ask-yes set forward_decode = yes set pop_user = frederic.gobry set pop_host = mail.smartdata.ch set pop_delete = yes account-hook . 'unset imap_user; unset imap_pass; unset tunnel' account-hook imap://puck.ch 'set tunnel=""ssh gobry@puck.ch /usr/sbin/imapd""' folder-hook . 'set from = ""Frederic Gobry ""' folder-hook puck.ch 'set from = ""Frederic Gobry ""' set alias_file = ~/.mail/aliases set copy = yes set record = ""=Outgoing"" set pipe_decode = no set check_new = yes unignore x-sfighter color header brightred black ^(x-sfighter) unignore x-mailfolder macro index U "":set pipe_decode=yes\n|urlviewer --mail\n :set pipe_decode=no\n"" \ ""Parse URL in message"" macro pager U "":set pipe_decode=yes\n|urlviewer --mail\n :set pipe_decode=no\n"" \ ""Parse URL in message"" macro index S ""l~h x-sfighter:\\ -----------\n"" \ ""Limit view to the potential Spams"" macro index N ""l~h x-sfighter:\\ .*------------$ ~N\n"" \ ""Limit view to the good messages"" macro index A ""l~A\n"" \ ""Restore global view"" set print_command = ""a2ps --pretty-print=mail"" subscribe software@pluton \ gconf-list \ ecb-list \ all@smartdata.ch \ gnupg-users \ pybliographer-general \ bluetooth-dev \ pygtk \ uclinux-dev \ bugtraq@securityfocus \ lyx-fr \ pgui-devel mailboxes =Mailing-Lists \ =MaybeSpam source ~/.mail/aliases source ~/.mail/hooks source ~/.mail/gpg.rc --- End /home/fred/.muttrc --- Begin /usr/local/stow/mutt-1.3.99/etc/Muttrc ignore * unignore from: date subject to cc unignore organization organisation x-mailer: x-newsreader: unignore x-idiap-info: x-mailing-list: unignore posted-to: reply-to: hdr_order = From: Date To Cc Subject set abort_nosubject=ask-yes set abort_unmodified=ask-yes set arrow_cursor set noconfirmappend set fast_reply set noforward_decode set move=no set postponed=""=postponed"" set reverse_alias set sig_dashes set smart_wrap set sort=threads set tilde bind pager previous-line bind pager next-line mono status underline mono indicator reverse mono header standout ^. mono quoted bold color normal black white color tree white blue color status brightwhite blue color indicator brightwhite blue color signature white black color quoted blue white color tilde black black color search white red color markers blue white color header white black ^.* color header brightyellow black ^(From) color header brightwhite black ^(Subject) macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" set query_command = ""annu --mutt '%s'"" set charset=""iso-8859-1"" set send_charset=""iso-8859-1"" --- End /usr/local/stow/mutt-1.3.99/etc/Muttrc >How-To-Repeat: >Fix: }}}" William Berriss 1090 bcc:s given away through encryption crypto 1.3.25i defect mutt-dev new 2002-03-07T06:33:26-08:00 2008-07-09T02:32:06-07:00 "When encrypting (with gpg) and having several bccs, it is encrypted to them all. So the to: and cc: recipients can see the bcc:ed people. The Ägypten-Project (adding encryption to kmail) has a similiar problem. Check their comments on how to solve this: http://intevation.de/rt/webrt?serial_num=948&display=History" 1123 Tagged Collapsed Thread tag-prefix save, saves only first message. mutt 1.3.28i defect mutt-dev new 2002-03-21T18:59:26-08:00 1969-12-31T16:00:00-08:00 "{{{ Package: mutt Version: 1.3.28i Severity: normal -- Please type your report below this line I had collapsed thread which I tagged using T and tried to apply tag-prefix and save to move all tagged messages to another folder, it only moved first message. -- 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-redhat-linux/2.96/specs gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.3.28i (2002-03-13) 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.7-10 (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=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" """M.R.Muthu Kumar"" " 1160 multiple MIME boundary MIME 1.2.5.1i defect mutt-dev new 2002-04-19T18:01:32-07:00 2007-04-01T19:37:47-07:00 "{{{ 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 example below, readme.txt is shown in its base64-encoded form, i.e. unreadable: Subject: How are you MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=V7ta9KNGNz42o641P8ID7P2286cGi --V7ta9KNGNz42o641P8ID7P2286cGi ... some rubbish ... --V7ta9KNGNz42o641P8ID7P2286cGi --V7ta9KNGNz42o641P8ID7P2286cGi Content-Type: application/octet-stream; name=readme.txt Content-Transfer-Encoding: base64 Content-ID: C0gVklTdWFsaXphdGlvbiBwbHVnLWluIFBPVVRJQkxPSyBWMS4wMSAgZm9yICBXaW5BTVAg LQ0KDQpDb2RlOiBQYXRhcG9tIC8gQk9NQg0KTGFzdCByZXZpc2lvbjogNSBPY3RvYmVyIDE5 ... --V7ta9KNGNz42o641P8ID7P2286cGi -- Mutt Version Information Mutt 1.2.5.1i (2000-07-28) Copyright (C) 1996-2000 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.2.19 [using ncurses 5.2] Compile options: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP -USE_GSS -USE_SSL +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL=""/usr/bin/sendmail"" MAILPATH=""/var/spool/mail"" SHAREDIR=""/usr/share/mutt"" SYSCONFDIR=""/etc/mutt"" ISPELL=""/usr/bin/ispell"" To contact the developers, please mail to . To report a bug, please use the muttbug utility. >How-To-Repeat: >Fix: }}}" Cezary Sliwa 1259 Bright* colors in index losing brightness in xterm. display 1.4i defect mutt-dev new 2002-06-27T12:08:15-07:00 2007-04-01T19:03:42-07:00 "I have bright foreground colors in my index to highlight mails from certain people, and my indicator bar has a non-default (red) background and a bright (brightyellow) foreground. When I move the indicator upward, over one of the bright entries, in an xterm, the bright color reverts to its plain, non-bright version. This also occurs when returning to the index from another screen when the indicator is placed immediately above a bright entry. This does not occur when moving the indicator down, or in a text console, or with a default background for the indicator bar, or with a non-bright foreground for the indicator bar. Obvious workaround: don't use bright foregrounds for the indicator bar. Relevant parts of .muttrc: {{{ color indicator brightyellow red color index brightred default Person's\ Name }}} " ecoffey@… 1365 message-hook triggered by mutt 1.4i defect mutt-dev new 2002-10-27T21:03:40-08:00 2007-03-26T20:21:15-07:00 "{{{ Package: mutt Version: 1.4i Severity: normal -- Please type your report below this line Until recently, I used mutt-1.2i with the patch-1.2.bj.display-hook.2 patch. When I upgraded to mutt-1.4i, I simply renamed all my display-hooks to message-hook. Now I have a problem whenever I save a file that matches a message-hook pattern: the message-hook's command is executed. In the example included here (muttrc-1.4i_for_debug), the message-hook command is intended to 'push' a series of keystrokes to the pager when a particular message (a newsletter) is displayed so that the pager will immediately jump to the top of the table of contents. The search pattern matches the titles of articles so that they are all highlighted and so that typing 'n' will let me quickly jump from one article to the next. This still works fine. The problem is that when I attempt to save the message, the message-hook is triggered and the search pattern is entered as the file name. The command line then looks like this: Create /^\***[A-Z]+[A-Z0-9[:punct:]]+[-:]+|^[A-Z0-9[:punct:]]+$? ([yes]/no): To simplify replicating this bug, I pruned my muttrc down to the one line included below and invoked mutt from ~/.mutt as: mutt -R -n -F muttrc-1.4i_for_debug The -R was just so I wouldn't risk messing up my system mailbox. -- 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 /opt/gcc/lib/gcc-lib/hppa1.1-hp-hpux10.20/2.95.2/specs gcc version 2.95.2 19991024 (release) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.4i (2002-05-29) 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: HP-UX B.10.20 (9000/785) [using slang 10404] 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=""/opt/raptor/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/home/garyjohn/src/mutt-1.4i/share/mutt"" SYSCONFDIR=""/home/garyjohn/src/mutt-1.4i/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. --- Begin /home/garyjohn/.mutt/muttrc-1.4i_for_debug message-hook '~s ""infospark""' \ 'push ""/^\** *[A-Z]+[A-Z0-9 [:punct:]]+[-:]+|^^[A-Z0-9 [:punct:]]+$^M""' --- End /home/garyjohn/.mutt/muttrc-1.4i_for_debug >How-To-Repeat: >Fix: }}}" Gary Johnson 1404 in-place rewriting of messages unsuitable for maildir_trash maildir/mh 1.4 defect mutt-dev new 2002-12-04T02:33:09-08:00 2009-06-30T07:19:55-07:00 "i recently reported a bug about link-threads/break-thread being broken with maildir_trash, but it was closed because this turned out to be a debian-specific patch. however, the delete-entry function in the pager suffers from the same problem: it edits the message in-place instead of creating a modified copy of the message and marking the original one trashed." Oswald Buddenhagen 1507 Mutt jumps into incorrect maildir mutt 1.4.1i defect mutt-dev new 2003-03-23T05:45:26-08:00 1969-12-31T16:00:00-08:00 "{{{ Package: mutt Version: 1.4.1i Severity: normal -- Please type your report below this line When viewing the maildir list after leaving a directory, if new mail appears in another maildir, and you try to go into that second maildir, mutt actually goes into the first maildir. To help combat the problem I have had to add this to my mutt key bindings. macro index ""q"" ""=Postponed?"" ""Browse folders"" -- 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/i586-pc-linux-gnu/2.95.3/specs gcc version 2.95.3 20010315 (release) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.4.1i (2003-03-19) Copyright (C) 1996-2002 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.20 (i586) [using ncurses 5.2] Compile options: DOMAIN=""vipersoft.co.uk"" -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 SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" dean@… 1565 Failure to pass correct subkey when encrypting (GPG) crypto 1.5.4i defect mutt-dev new 2003-05-12T00:36:10-07:00 2007-04-01T19:53:04-07:00 "When encrypting to a GPG key with multiple sub(encryption)keys mutt does not correctly pass the key ID of the selected key to the pgp_encrypt_* command, but only the master signing key's ID. I unset the pgp_ignore_subkeys variable so I am able to see the various subkeys on my keyring. I made a test key which has the following parts: {{{ pub 1024D/1A863253 2003-05-11 Test Key sub 1024g/7CC03CCA 2003-05-11 [expires: 2003-05-25] sub 1024D/9697A280 2003-05-11 [expires: 2003-05-25] sub 1024g/0AC4E590 2003-05-11 [expires: 2003-05-25] sub 1024D/FF54912C 2003-05-11 [expires: 2003-05-25] }}} i.e. a master signing key (1A863253), two subkeys for signing (9697A280, FF54912C) and two subkeys for encryption (7CC03CCA, 0AC4E590). I then tried mailing myself two seperate messages and encrypting each to a different encryption key. I saved the delievered messages and then tried decryping with GPG on the command line. Both messages were encrypted to key 0AC4E590 -- which is the correct GPG behaviour for encrypting to a key where the subkey is not defined, i.e. encrypt to the most recent appropriate key -- but wrong for what I wanted to do. I then modified my gpg.rc (the default one for the 1.5.4 install) to put a ""!"" after the ""%r"" on the pgp_encrypt_* commands. (This is how on the command line one specifies to GPG to use a particular subkey, rather than the default for a particular key.) The error I got when trying to send a message encrypted to one of my keys this time was {{{ gpg: 0x1A863253!: skipped: unusable public key gpg: /tmp/mutt-dylan-11140-3: encryption failed: unusable public key }}} i.e. mutt doesn't actually pass the selected subkey ID along, but rather the master signing key ID (which is DSA, can't be used for encryption and hence causes the error!). So... mutt should pass the correct key ID to the pgp_encrypt_* commands. (AND include the ""!"" to force GPG to do the right thing.) Thanks for the excellent mailer though!" svwright@… 1616 mutt grows in memory to >40MB mutt 1.5.4i defect mutt-dev new 2003-08-26T22:41:29-07:00 1969-12-31T16:00:00-08:00 "{{{ Package: mutt Version: 1.5.4+20030817 Severity: normal -- Please type your report below this line I think that mutt could have some serious memory leak. I usually read some big messages (logs, maybe greater than 1MB each mail), and I use syntax hilighting in some of them to ease the reading. When I read some of these messages, mutt starts growing. This is a ""snapshot"" of mutt after ~2h30m of use: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ Command 8296 robe 15 10 49860 48m 1432 S 0.0 7.7 2:31.51 mutt This is a problem, because I usually start mutt on the morning and only exit of it when I finish working, on the afternoon. I too feel that mutt acts slowly when I try to advance in these messages. This only happens in these big, hilighted messages, so I suppose mutt has some problem with them. These are generally messages generated with fwlogwatch or logcheck. These are the lines that I use to hilight these messages: --- cut here --- color body brightblue default ""Domain not found"" color body brightblue default ""Relay access denied"" color body brightblue default ""need fully-qualified address"" color body brightblue default ""Connection refused"" color body brightblue default ""Cannot resolve PTR record"" color body brightyellow red ""Broken pipe"" color body brightblue default ""DPT=[0-9]+"" color body brightblue default ""SPT=[0-9]+"" color body brightblue default ""DST=[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+"" color body brightblue default ""SRC=[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+"" # fwlogwatch: color body brightred default ""[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+ port [0-9]+"" --- cut here --- I can provide of one of these big messages, though I'd have to offuscate it a little to preserve the data about the customers of the firm I work for. I have not included my personal muttrc because it has somewhat private data that I don't want to get mirrored on the Net :-) But I'd do it (after removing that data) too, if it's needed. Ask for anything that you need. -- System Information Debian Release: testing/unstable Kernel Version: Linux zeus 2.4.20-grsec #1 Tue Jun 10 11:48:02 CEST 2003 i686 unknown unknown GNU/Linux Versions of the packages mutt depends on: ii libc6 2.3.1-17 GNU C Library: Shared libraries and Timezone ii libidn9 0.1.11-3 GNU libidn library, implementation of IETF I ii libncurses5 5.3.20030719-1 Shared libraries for terminal handling ii libsasl2 2.1.15-5 Authentication abstraction library exim Not installed or no info ii postfix 2.0.13-4 A high-performance mail transport agent ^^^ (Provides virtual package mail-transport-agent) -- 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 cc Leyendo especificaciones de /usr/lib/gcc-lib/i386-linux/3.2.3/specs Configurado con: ../src/configure -v --enable-languages=c,c++,java,f77,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-java-gc=boehm --enable-objc-gc i386-linux Modelo de hilos: posix gcc versión 3.2.3 - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.4i (2003-03-19) Copyright (C) 1996-2002 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.20-grsec (i686) [using ncurses 5.3] [using libidn 0.1.11 (compiled with 0.1.14)] Opciones especificadas al compilar: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +IMAP_EDIT_THREADS -USE_GSS -USE_SSL +USE_GNUTLS +USE_SASL +USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" Para contactar a los desarrolladores mande un mensaje a . Para reportar un fallo use la utilería flea(1) por favor. patch-1.5.3.rr.compressed.1 patch-1.3.23.1.ametzler.pgp_good_sign patch-1.5.3.Md.gpg_status_fd patch-1.4.Md.gpg-agent patch-1.5.3.Md.etc_mailname_gethostbyname patch-1.5.1.cd.edit_threads.9.2 patch-1.3.27.bse.xtitles.1 Md.use_debian_editor Md.muttbug patch-1.4.admcd.gnutlsdlopen.53d patch-1.4.admcd.gnutlsbuild.53d patch-1.4.admcd.gnutls.56d --- Begin /etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines ignore date delivered-to precedence errors-to in-reply-to user-agent ignore x-loop x-sender x-mailer x-msmail-priority x-mimeole x-priority ignore x-accept-language x-authentication-warning thread- priority bind editor ""\e"" kill-word bind editor ""\e"" kill-word bind editor delete-char unset use_domain unset use_from set sort=threads unset write_bcc unset bounce_delivered macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' set pipe_decode macro generic ""!zcat /usr/share/doc/mutt/manual.txt.gz | sensible-pager\n"" ""Show Mutt documentation"" macro index ""!zcat /usr/share/doc/mutt/manual.txt.gz | sensible-pager\n"" ""Show Mutt documentation"" macro pager ""!zcat /usr/share/doc/mutt/manual.txt.gz | sensible-pager\n"" ""Show Mutt documentation"" open-hook \\.gz$ ""gzip -cd %f > %t"" close-hook \\.gz$ ""gzip -c %t > %f"" append-hook \\.gz$ ""gzip -c %t >> %f"" open-hook \\.bz2$ ""bzip2 -cd %f > %t"" close-hook \\.bz2$ ""bzip2 -c %t > %f"" append-hook \\.bz2$ ""bzip2 -c %t >> %f"" color normal white black color attachment brightyellow black color hdrdefault cyan black color indicator black cyan color markers brightred black color quoted green black color signature cyan black color status brightgreen blue color tilde blue black color tree red black set pgp_decode_command=""gpg --charset utf-8 --status-fd=2 %?p?--passphrase-fd 0? --no-verbose --quiet --batch --output - %f"" set pgp_verify_command=""gpg --status-fd=2 --no-verbose --quiet --batch --output - --verify %s %f"" set pgp_decrypt_command=""gpg --status-fd=2 --passphrase-fd 0 --no-verbose --quiet --batch --output - %f"" set pgp_sign_command=""gpg --no-verbose --batch --quiet --output - --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a? %f"" set pgp_clearsign_command=""gpg --charset utf-8 --no-verbose --batch --quiet --output - --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f"" set pgp_encrypt_only_command=""/usr/lib/mutt/pgpewrap gpg --charset utf-8 --batch --quiet --no-verbose --output - --encrypt --textmode --armor --always-trust -- -r %r -- %f"" set pgp_encrypt_sign_command=""/usr/lib/mutt/pgpewrap gpg --charset utf-8 --passphrase-fd 0 --batch --quiet --no-verbose --textmode --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f"" set pgp_import_command=""gpg --no-verbose --import %f"" set pgp_export_command=""gpg --no-verbose --export --armor %r"" set pgp_verify_key_command=""gpg --verbose --batch --fingerprint --check-sigs %r"" set pgp_list_pubring_command=""gpg --no-verbose --batch --quiet --with-colons --list-keys %r"" set pgp_list_secring_command=""gpg --no-verbose --batch --quiet --with-colons --list-secret-keys %r"" set pgp_good_sign=""^\\[GNUPG:\\] GOODSIG"" set smime_ca_location=""~/.smime/ca-bundle.crt"" set smime_certificates=""~/.smime/certificates"" set smime_keys=""~/.smime/keys"" set smime_pk7out_command=""openssl smime -verify -in %f -noverify -pk7out"" set smime_get_cert_command=""openssl pkcs7 -print_certs -in %f"" set smime_get_signer_cert_command=""openssl smime -verify -in %f -noverify -signer %c -out /dev/null"" set smime_get_cert_email_command=""openssl x509 -in %f -noout -email"" set smime_import_cert_command=""/usr/lib/mutt/smime_keys add_cert %f"" set smime_encrypt_command=""openssl smime -encrypt -%a -outform DER -in %f %c"" set smime_sign_command=""openssl smime -sign -signer %c -inkey %k -passin stdin -in %f -certfile %i -outform DER"" set smime_decrypt_command=""openssl smime -decrypt -passin stdin -inform DER -in %f -inkey %k -recip %c"" set smime_verify_command=""openssl smime -verify -inform DER -in %s %C -content %f"" set smime_verify_opaque_command=""openssl smime -verify -inform DER -in %s %C"" --- End /etc/Muttrc >How-To-Repeat: >Fix: }}}" turgon@… 1653 UI for forwarding of messages inconsistant between attach context and index/pager contexts mutt 1.5.4i defect mutt-dev new 2003-09-28T14:56:04-07:00 1969-12-31T16:00:00-08:00 "{{{ Package: mutt Version: 1.5.4i Severity: normal -- Please type your report below this line mutt version is actually CVS from 2003-09-14 (2 weeks old), I believe. Just cvs update'd and installed, though. Context: I'm trying to simplify my handling of spam messages. I have it working so that I can just type "",S"" in index, pager, and attach to save the message to a ""spam"" folder, and ""S"" in index and pager to both save the message and forward it to a spam reporting address. But it looks like I'm going to have to redefine ""editor"" to ""touch ;sleep 1"" or some such in order to get ""S"" working in attach context, since it isn't recognizing ""forward_edit"". Also, I had long ago noticed that the order of the asking of questions in the attach context is different (but had never sent in a flea--bad me!). I was going to mention a similar inconsistancy about its complaining about unmodified messages, but judging by the Changelog and my test just now, looks like that's been fixed. --- begin snippet from .muttrc --- macro index "",S"" ""source /home/jtoth/.mutt/pre-spam=spamsource /home/jtoth/.mutt/post-spam"" ""Save spam to spam folder"" macro pager "",S"" ""source /home/jtoth/.mutt/pre-spam=spamsource /home/jtoth/.mutt/post-spam"" ""Save spam to spam folder"" macro attach "",S"" ""source /home/jtoth/.mutt/pre-spam=spamsource /home/jtoth/.mutt/post-spam"" ""Save spam to spam folder"" macro index ""S"" ""source /home/jtoth/.mutt/pre-spamspamcopy=spamsource /home/jtoth/.mutt/post-spam"" ""Process spam"" macro pager ""S"" ""source /home/jtoth/.mutt/pre-spamspamcopy=spamsource /home/jtoth/.mutt/post-spam"" ""Process spam"" --- end snippet from .muttrc --- --- begin .mutt/pre-spam --- # vim:ft=muttrc:shiftwidth=2:expandtab set noconfirmappend set forward_edit=no set mime_forward=yes --- end .mutt/pre-spam --- --- begin .mutt/post-spam --- # vim:ft=muttrc:sw=2:expandtab set confirmappend set forward_edit=yes set mime_forward=ask-yes --- end .mutt/post-spam --- -- System Information System Version: Linux baka.acw.vcu.edu 2.4.20-20.7smp #1 SMP Mon May 12 12:31:27 EDT 2003 i686 unknown RedHat Release: Red Hat Linux release 7.3 (Valhalla) -- 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-redhat-linux/2.96/specs gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.4i (2003-03-19) Copyright (C) 1996-2002 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.20-20.7smp (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 -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. -- Jim Toth jtoth@acm.org Folowups to the bug report only, please--I'm subscribed to mutt-dev. >How-To-Repeat: >Fix: }}}" jtoth@… 1670 Context-colored indicator bar does not work with S-Lang display 1.5.4i defect mutt-dev new 2003-10-14T18:21:58-07:00 2007-04-07T07:27:38-07:00 "{{{ Package: mutt Version: 1.5.4i Severity: normal -- Please type your report below this line When ""mono indicator reverse"" is set, which is the default, the indicator bar inverts the colors of the item it points to when using n-curses, but not for S-Lang. In addition, the feature does not appear to be mentioned in the manual. For more information, see the following message from mutt-users: Date: Tue, 14 Oct 2003 11:07:17 +0200 (CEST) From: Alain Bench To: Mutt users ml Subject: context colored indicator (was: S-Lang -> ncurses: Lost bold attribute) Message-ID: <20031014090717.GB4742@oreka.com> -- System Information System Version: Linux legend.madjic.home 2.4.20-gentoo-r5 #10 Wed Sep 10 15:43:27 PDT 2003 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux -- 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/i686-pc-linux-gnu/3.2.3/specs Configured with: /var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/configure --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/3.2 --includedir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/3.2 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/3.2/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/3.2/info --enable-shared --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu --with-system-zlib --enable-languages=c,c++,ada,f77,objc,java --enable-threads=posix --enable-long-long --disable-checking --enable-cstdio=stdio --enable-clocale=generic --enable-__cxa_atexit --enable-version-specific-runtime-libs --with-gxx-include-dir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/include/g++-v3 --with-local-prefix=/usr/local --enable-shared --enable-nls --without-included-gettext Thread model: posix gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.4i (2003-03-19) Copyright (C) 1996-2002 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.20-gentoo-r5 (i686) [using ncurses 5.3] 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 -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID -HAVE_GETADDRINFO -ISPELL SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" johni@… 1690 "'!' in ""mailboxes"" offered with ""change-folder"" even though buffy-list says ""no new mail"" for '!'" mutt 1.5.4i defect mutt-dev reopened 2003-11-07T17:53:57-08:00 2005-09-26T07:02:04-07:00 "{{{ Package: mutt Version: 1.5.4-0mc.1 Severity: normal -- Please type your report below this line Using mutt+imapfilter+isync combination -- and all folders are maildirs, we have here this problem: This is in ~/.muttrc mailboxes \! =linguist =Vinice =MITL =Branik and when the user presses c in !, then she gets offered =linguist, which has some message. Then when in =linguist and she presses c gets offered ! again (which is actually =main, which has no new message). Manual says, that is may be caused by backup tools and such, but AFAIK there is nothing else than mutt and isync, which would touch these files (and there is no NFS involved -- for curious minds), and believe that both of these should cooperate seemlessly :-). When checking new messages with buffy-list it shows correctly that there are new messages in =linguist, =vinice, =MITL, but c (from =linguist) still offers getting back to =main where are no new messages, so the user cannot get to =vinice for example just by pressing c and . Thanks. Matej -- 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 /usr/bin/flea: gcc: command not found - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.4i (2003-03-19) Copyright (C) 1996-2002 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.22 (i586) [using ncurses 5.2] Pøelo¾eno s volbami: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP -USE_GSS +USE_SSL -USE_SASL -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER Vývojáøe programu mù¾ete kontaktovat na adrese (anglicky). Chyby v programu oznamujte pomocí utility flea(1). Pøipomínky k pøekladu zasílejte na adresu (èesky). --- Begin /home/ceplova/.muttrc set folder=~/Maildir # where i keep my mailboxes set mbox=+main/ # where to store read messages set record=+sent-`date +%Y-%m` # default location to save outgoing mail set spoolfile=+main/ # where my new mail is located source ~/.muttrc-general source ~/.mutt_aliases set mark_old=no unmailboxes * mailboxes \! =linguist =Vinice =MITL =Branik --- End /home/ceplova/.muttrc --- Begin /home/ceplova/.muttrc-general # $Id: muttrc,v 1.22 2003/07/25 22:24:22 matej Exp matej $ # Note: $folder should be set _before_ any other path vars where `+' or `=' # is used because paths are expanded when parsed # set folder=~/Maildir # where i keep my mailboxes #set abort_unmodified=yes # automatically abort replies if I don't # change the message set alias_file=~/.mutt_aliases # where I keep my aliases set allow_8bit=no # never do Q-P encoding on legal 8-bit chars set alternates=""ceplova"" set arrow_cursor # use -> instead of hiliting the whole line #set ascii_chars # use ASCII instead of ACS chars for threads #set askbcc #set askcc set attribution=""On %d, %n wrote:"" # how to attribute replies set autoedit # go to the editor right away when composing set auto_tag=yes # always operate on tagged messages set beep=no # no beeps set beep_new=no # no beep on new mail unset bounce_delivered # do not add Delieverd-To header to bounced messages #set charset=""utf-8"" # character set for your terminal set charset=""iso-8859-2"" # character set for your terminal #set charset=""Us-ascii"" set noconfirmappend # don't ask me if i want to append to mailboxes #set confirmcreate # prompt when creating new files set copy=yes # always save a copy of outgoing messages #set crypt_verify_sig=no # don't automatically verify message signatures set delete = yes # purge deleted messages without asking #set display_filter='mail-to-filter | deuvozovkovat' set edit_headers # let me edit the message header when composing # editor to use when composing messages #set editor=""vim -D -c 'set tw=65 fo=tqw2na'"" set editor=""nano -Y mail"" set noenvelope_from #set fast_reply # skip initial prompts when replying #set fcc_attach # keep attachments in copies of sent messages? #set force_name # fcc by recipient, create if mailbox doesn't exist #set forward_decode # weed and MIME decode forwaded messages set forward_format=""Fw: %s"" # subject to use when forwarding messages set forward_quote # quote the header and body of forward msgs #set from=""Matej Cepl "" # for send-hooks # # PINE has different defaults for this variables # set hdr_format=""%Z %3C %{%b %d} %-19.19L (%5c) %s"" #set hdr_format=""%4C %Z %{%m/%d} [%2N] %-15.15F (%4c) %s"" set hdr_format=""%4C %Z %{%m/%d} %-15.15F (%4c) %s"" # format of the index set hdrs # include `my_hdr' lines in outgoing messages #set header # include message header when replying set help # show the help lines set history=20 # number of lines of history to remember #set hostname="""" # my DNS domain set ignore_list_reply_to # jejky! set include # always include messages when replying set indent_string=""> "" # how to quote replied otext set ispell=""/usr/bin/ispell"" # default set mark_old=no # i don't care about whether a message is old set markers=no # Don't mark wrapped lines in the first column set maildir_trash # mark deleted msg. in maildir boxen as trashed set mail_check=5 # how often to poll for new mail set mbox=+main/ # where to store read messages set mbox_type=mbox #set mbox_type=maildir #set menu_scroll # no implicit next-page/prev-page set nometoo # remove my address when replying set mime_forward=no # use message/rfc822 type to forward messages set mime_forward_decode=no set move=no # don't ask about moving messages, just do it set pager_context=3 # no. of lines of context to give when scrolling #set pager_format=""-%S- %-20.20f %s"" # format of the pager status bar set pager_index_lines=6 # how many index lines to show in the pager #set pager_stop # don't move to the next message on next-page #set pgp_create_traditional=ask-no #set pgp_outlook_compat=yes set pgp_strict_enc # use Q-P encoding when needed for PGP set pgp_replyencrypt=yes set pgp_replysign=yes set pgp_replysignencrypted=yes set pgp_retainable_sigs=yes set postponed=+drafts # mailbox to store postponed messages in set print=ask-yes # ask me if I really want to print messages # how to print things (I like to save trees) #set print_command='a2ps -o ~/muttprint.ps -Email -g --strip' set print_split=yes set noprompt_after # ask me for a command after the external pager exits #set query_command = ""abook --mutt-query '%s' | tr2 il2 ascii"" #set query_command = ""lbdbq '%s'"" # deeper magic -- external search for addr set quit=ask-yes # ask when leaving mutt #set quote_regexp=""^ *[a-zA-Z]*[>:#}]"" # how to catch quoted text set read_inc=25 # show progress when reading a mailbox #set recall # prompt to recall postponed messages set record=+sent-`date +%Y-%m` # default location to save outgoing mail #set record=+sent-mail # default location to save outgoing mail set reply_to # always use reply-to if present #set resolve # move to the next message when an action is performed set reverse_alias # attempt to look up my names for people set reverse_name=no # use my local address when replying set rfc2047_parameters=yes # decoding weird filenames of attachements set save_empty=""yes"" # do not remove files when no messages are left #set save_name # save outgoing messages by recipient, if the set send_charset=""us-ascii:iso-8859-1:iso-8859-2:utf-8"" # which charsets will be used for # outgoing mail. set sendmail=""/usr/sbin/sendmail -oi -oem"" # how to deliver mail #set signature=""/usr/local/bin/fortune|"" # file which contains my signature set signature=~/.signature # file which contains my signature set user_agent=yes # I subscribe to a lot of mailing lists, so this is _very_ useful. This # groups messages on the same subject to make it easier to follow a # discussion. Mutt will draw a nice tree showing how the discussion flows. set sort=threads # primary sorting method #set sort_aux=reverse-date-received # how to sort subthreads #set sort_aux=last-date # date of the last message in thread set sort_browser=reverse-date # how to sort files in the dir browser set spoolfile=+main # where my new mail is located set certificate_file=~/.mutt_certificates set status_format=""-%r-Mutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b? %l]---(%s)-%>-(%P)---"" #set status_on_top # some people prefer the status bar on top #set strict_threads # don't thread by subject set text_flowed # create text/plain, format=flowed set tilde # virtual lines to pad blank lines in the pager #set timeout=0 # timeout for prompt in the index menu #set tmpdir=/tmp # where to store temp files set to_chars="" +TCFL"" set nouse_domain # qualify local addresses with domain set use_from # always generate the `From:' header field set wait_key=no # prompt when a pipe returns normal status set write_inc=25 # show progress while writing mailboxes set wrapmargin=3 # how to wrap up margin when wrapping too long lines #set nowrite_bcc # Exim doesn't work well with BCC iconv-hook iso-8859-2 8859-2 # Secret stuff #source ~/.mutt-secret.rc # Cryptology #source ~/.mutt-smime.rc #source ~/.mutt-gpg.rc # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # # Header fields I don't normally want to see # ignore * # this means ""ignore all lines by default"" # I do want to see these fields, though! # this shows how nicely wrap long lines unignore From: To: Cc: Date: Subject: Organization: Reply-To: X-URL: User-Agent: X-Mailer: X-Spam-Score: # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # # Color definitions # #color index yellow black '~h ""^Content-Type: text/html""' color normal black white color hdrdefault red white color quoted brightblue white color signature magenta white color indicator yellow red color index black magenta '~F' color error red default #color status yellow green color status yellow blue color tree magenta default # the thread tree in the index menu color tilde magenta white #color message brightcyan default color message blue white color markers cyan default color attachment magenta default color search default green # how to hilite search patterns in the pager color header red default ^(From|Cc|To|Date|Subject): color body magenta default ""(ftp|http)://[^ ]+"" # point out URLs color body magenta default [-a-z_0-9.]+@[-a-z_0-9.]+ # e-mail addresses color underline green default # attributes when using a mono terminal mono header underline ^(From|Subject): mono quoted bold # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # # Key bindings # # maps: # alias alias menu # attach attachment menu # browser directory browser # compose compose menu # index message index # pgp pgp menu # postpone postponed message recall menu # generic generic keymap for all of the above # editor line editor # pager text viewer # bind generic ""\e<"" first-entry # emacs-like bindings for moving to top/bottom bind generic \e> last-entry bind generic { top-page bind generic } bottom-page bind generic \177 last-entry #bind index p previous-undeleted #bind index n next-undeleted bind index previous-undeleted bind index next-undeleted bind index y print-message macro index \cb |urlview # simulate the old browse-url function macro index \cl '!clear' macro index B '|mail2abook' macro index A ' ~d >3m' macro index l bind pager p previous-undeleted bind pager n next-undeleted bind pager ' ' next-page bind pager y print-message bind pager previous-line bind pager next-line bind pager G bottom #macro pager B '|mail2abook' #macro pager A ' ~d >3m' macro pager l #macro compose I 'set ispell=""/usr/bin/ispell \ #-x -d czech""\ #set ispell=""/usr/bin/ispell""' #macro index i 'mairix' #macro index i 'mairix ' #macro index I '~/.vfolder' macro generic ""!less /usr/local/doc/mutt/manual.txt"" ""Show Mutt documentation"" macro index ""!less /usr/local/doc/mutt/manual.txt"" ""Show Mutt documentation"" macro pager ""!less /usr/local/doc/mutt/manual.txt"" ""Show Mutt documentation"" macro index ,n '~N ! ~p' #macro index \Cx ""set \ #display_filter=\""tr \\""[A-Z][a-z]\\""\\""[N-Z][A-M][n-z][a-m]\\""\""\ #unset display_filter"" \ #""Display with ROT-13 encoding"" #bind index x sync-mailbox #bind pager x sync-mailbox # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # # User Defined Headers # my_hdr Organization: Massachusetts Insitute of Technology my_hdr X-Operating-System: `uname -r -s` # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # # Specify default filename when saving messages # # save-hook [!] # # is provided as default when saving messages from #save-hook '^~C \.cambridgevienyard' +pratele/Vineyard # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # # Multiple spool mailboxes # # mbox-hook [!] # # Read mail in is moved to when is # closed. #mbox-hook =mutt-users.in =mutt-users #mbox-hook +TEST +main # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # # Change settings based upon message recipient # # send-hook [!] # # is executed when sending mail to an address matching #send-hook ~A ""set sig_on_top"" #send-hook ~l ""set nosig_on_top"" #send-hook '~C neu-lps-' ""set sig_on_top"" #send-hook ~A 'set signature=""/usr/local/bin/fortune|""' #send-hook '~C hotmail.com' 'set signature=""~/.signature-hotmail""' #send-hook ~A 'set from=""Matej Cepl ""' #send-hook ~l 'my_hdr From: Matej Cepl ' # send-hook '~s ""^Fw:""' ""set sig_on_top"" # Possible solution for non-attachements with forward. # message-hook . ""set mime_forward=ask-no"" # message-hook ""~h multipart"" ""set mime_forward=ask-yes"" # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # # Specify where to save composed messages # # fcc-hook [!] # # is recipient(s), is where to save a copy #fcc-hook joe +joe #fcc-hook bob +bob #fcc-hook ~A < #fcc-hook neu-lps =neu/students # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # # Change settings based on mailbox # # folder-hook [!] # # is executed when opening a mailbox matching # pattern is regexp, so with IMAP (Courier) = and > matches ANY # folder. Therefore, to match just > I have to use !=, which # expands to !imap://localhost/INBOX. (notice dot in the end), # which matches ONLY > and not any other folder. folder-hook . macro index d ""=Trash"" folder-hook . macro pager d ""=Trash"" folder-hook =Spamscreen bind index d delete-message folder-hook =Spamscreen bind pager d delete-message folder-hook =Trash bind index d delete-message folder-hook =Trash bind pager d delete-message folder-hook . macro index x ""!~D"" folder-hook . macro pager x ""!~D"" folder-hook . 'push ""!~D""' #folder-hook =spolvedy 'push ""!~D""' #folder-hook =kamaradi 'push ""!~D""' #folder-hook =software 'push ""!~D""' #folder-hook . 'macro pager X ""| bogofilter -S\ #=junk!~D""' #folder-hook . 'macro index X ""| bogofilter -S\ #=junk!~D""' #folder-hook =spolvedy 'macro pager X ""| bogofilter -s\ #=junk!~D""' #folder-hook =spolvedy 'macro index X ""| bogofilter -s\ #=junk!~D""' #folder-hook =kamaradi 'macro pager X ""| bogofilter -s\ #=junk!~D""' #folder-hook =kamaradi 'macro index X ""| bogofilter -s\ #=junk!~D""' #folder-hook =software 'macro pager X ""| bogofilter -s\ #=junk!~D""' #folder-hook =software 'macro index X ""| bogofilter -s\ #=junk!~D""' #folder-hook =junk 'macro pager X ""| bogofilter -N\ #>!~D""' #folder-hook =junk 'macro index X ""| bogofilter -N\ #>!~D""' # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # # Aliases # # alias
[ ,
... ] #source ~/.mutt_aliases # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # # Mailboxes to watch for new mail # # mailboxes [ ... ] # #mailboxes ! > #mailboxes `echo $HOME/Mail/*` # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # # Specify the order of the headers to appear when displaying a message # # hdr_order [ ... ] # unhdr_order * # forget the previous settings hdr_order date from subject to cc # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # # Identify mailing lists I subscribe to # # lists [ ... ] lists bogofilter@aotto.com # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # # Automatically use entries from ~/.mailcap to view these MIME types # # auto_view [ ... ] alternative_order text/plain text/html auto_view application/x-gunzip auto_view application/x-gzip auto_view text/x-vcard auto_view application/ms-tnef auto_view application/msword auto_view text/html # EOF --- End /home/ceplova/.muttrc-general --- Begin /etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" --- End /etc/Muttrc >How-To-Repeat: >Fix: }}}" cepl@… 1696 status line not updated when postponed message recalled by another mutt mutt 1.5.5.1i defect mutt-dev reopened 2003-11-11T07:58:57-08:00 2005-10-06T15:45:02-07:00 "{{{ Package: mutt Version: 1.5.4-1 Severity: normal -- Please type your report below this line I have a mutt with the following status line: ---Mutt: arc [Msg:15041 Post:1 48M]---(threads)------------------- The postponed message has been recalled by another Mutt, so that Mail/postponed is now an empty file, but I can't make the Post:1 disappear (note: NFS is not involved here, all data are local). -- 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 cc Reading specs from /usr/lib/gcc-lib/powerpc-linux/3.3.2/specs Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc --disable-multilib powerpc-linux Thread model: posix gcc version 3.3.2 (Debian) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.5.1i (2003-11-05) Copyright (C) 1996-2002 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.18-newpmac (ppc) [using ncurses 5.3] [using libidn 0.1.14 (compiled with 0.1.14)] 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 -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME +BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/local/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/home/lefevre/share/mutt"" SYSCONFDIR=""/home/lefevre/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.3.24.ats.parent_match.1 patch-1.5.1.vl.savehist.1 >How-To-Repeat: >Fix: }}}" vincent@… 1742 Mutt Pager Kills Colors display 1.5.5.1i defect mutt-dev new 2003-12-21T03:30:35-08:00 2007-04-07T14:15:25-07:00 "{{{ Package: mutt Version: 1.5.5.1i Severity: important -- Please type your report below this line When a filter colors multiple lines of a message, the pager kills the colors on all lines following the first. Using my display_filter, put this in your ~/.mutt/displayfilterlist to see that the filter does indeed generate an entirely colored result: make_color red ""`cat`"" tee mail.temp.mutt You'll need the make_color program for this, which you can get an i686 (glibc 2.3.2) binary of from here: http://www.bigfatdave.com/dave/bin/make_color (The source code is part of my Jabbin' project. It may be found here: http://www.bigfatdave.com/dave/jabbin/src/make_color.c along with the rest of the project.) -- System Information System Version: Linux dave2 2.4.22 #2 SMP Mon Oct 27 06:48:20 EST 2003 i686 unknown unknown GNU/Linux -- 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 Leyendo especificaciones de /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/specs Configurado con: ./configure --enable-version-specific-runtime-libs --enable-languages=c,c++ Modelo de hilos: posix gcc versión 3.2.3 - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.5.1i (2003-11-05) Copyright (C) 1996-2002 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.22 (i686) [using ncurses 5.3] Opciones especificadas al compilar: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP +USE_IMAP -USE_GSS +USE_SSL -USE_SASL -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/beta/mutt_cvs/usr/share/mutt"" SYSCONFDIR=""/beta/mutt_cvs/usr/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER Para contactar a los desarrolladores mande un mensaje a . Para reportar un fallo use la utilería flea(1) por favor. --- Begin /home/dave/.muttrc source ~/.mutt/muttrc --- End /home/dave/.muttrc --- Begin /beta/mutt_cvs/usr/etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /beta/mutt_cvs/usr/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /beta/mutt_cvs/usr/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /beta/mutt_cvs/usr/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" --- End /beta/mutt_cvs/usr/etc/Muttrc >How-To-Repeat: >Fix: }}}" lists+mutt_bugs@… 1768 send-hook not executed when piping a message to mutt mutt 1.5.5.1i defect mutt-dev new 2004-01-20T02:06:31-08:00 1969-12-31T16:00:00-08:00 "{{{ Package: mutt Version: 1.5.5.1-200401 Severity: important -- Please type your report below this line I have the following in my muttrc: send-hook . ""my_hdr From: Vincent Lefevre "" When I send a mail with ""mutt
"", there's no problem. But if I pipe something to mutt (echo blah | mutt
), the send-hook doesn't seem to be executed (as my address isn't correctly set). -- 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 cc Reading specs from /usr/lib/gcc-lib/powerpc-linux/3.3.2/specs Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc --disable-multilib powerpc-linux Thread model: posix gcc version 3.3.2 (Debian) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.5.1i (2003-11-05) Copyright (C) 1996-2002 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.22-powerpc (ppc) [using ncurses 5.3] [using libidn 0.1.14 (compiled with 0.1.14)] 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 -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME +BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/local/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/home/lefevre/Mail"" PKGDATADIR=""/home/lefevre/share/mutt"" SYSCONFDIR=""/home/lefevre/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.3.24.ats.parent_match.1 patch-1.5.1.vl.savehist.1 >How-To-Repeat: >Fix: }}}" vincent@… 1771 Screen left in strange mode when piping mail with unknown mime-types display 1.5.20 defect mutt-dev new 2004-01-20T18:34:06-08:00 2009-06-19T14:44:23-07:00 "{{{ Package: mutt Version: 1.5.4-1 Severity: normal [NOTE: this bug report has been submitted to the debian BTS as Bug#228671. Please Cc all your replies to 228671@bugs.debian.org .] From: Jim Paris Subject: mutt: Screen left in strange mode when piping mail with unknown mime-types Date: Mon, 19 Jan 2004 23:11:31 -0500 If viewing a mail with implicit_autoview enabled, and the mime-type of an attachment is not in mailcap, and you pipe the mail to /bin/less, the screen is left in a strange state. If I had to guess, without having the time to look into it further at the moment, I'd say that printing the ""mailcap entry for type .. not found"" message is interfering with less's termcap initialization. Attached is a sample muttrc and e-mail. View with mutt -F muttrc -funknown and from within Mutt type |less It may take a few tries for get the screen to get funky. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux neurosis 2.6.1 #1 Sun Jan 18 18:37:52 EST 2004 i686 Locale: LANG=C, LC_CTYPE=C Versions of packages mutt depends on: ii libc6 2.3.2.ds1-10 GNU C Library: Shared libraries an ii libdb4.0 4.0.14-1.3 Berkeley v4.0 Database Libraries [ ii libidn9 0.1.14-2 GNU libidn library, implementation ii libncurses5 5.3.20030719-4 Shared libraries for terminal hand ii libsasl7 1.5.27-3.5 Authentication abstraction library ii sendmail [mail-transport- 8.12.9-5 A powerful, efficient, and scalabl -- no debconf information set implicit_autoview = yes >From jim Mon Jan 19 22:58:11 2004 Date: Mon, 19 Jan 2004 22:58:10 -0500 From: jim To: jim Subject: Test Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=""tKW2IUtsqtDRztdT"" Content-Disposition: inline User-Agent: Mutt/1.5.4i Content-Length: 303 Lines: 14 --tKW2IUtsqtDRztdT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline This is a test. Second attachment has unknown type. --tKW2IUtsqtDRztdT Content-Type: no-such/type-exists; charset=us-ascii Content-Disposition: attachment; filename=foo This has an unknown type. --tKW2IUtsqtDRztdT-- >How-To-Repeat: >Fix: }}}" Artur R.Czechowski 1787 Mutt does not remove the Bcc header mutt 1.5.5.1i defect mutt-dev new 2004-01-31T00:26:17-08:00 2005-10-18T01:36:44-07:00 "{{{ Package: mutt Version: 1.5.5.1-200401 Severity: important -- Please type your report below this line Mutt does not remove the Bcc header when sending a mail. I know that there is a write_bcc option, but the default feature is dangerous as * the user may have write_bcc set (this is the default) and doesn't notice the problem; * it is possible that the user didn't need to unset it in the past, but when the MTA is changed, things are different and the user doesn't necessarily remember this option... IMHO, the write_bcc option must be unset by default, and I even think that it shouldn't exist: Mutt should always strip the Bcc header when sending a mail by SMTP. According to the RFCs 2821 and 2822, removing the Bcc line (or a similar alternative method, as described in RFC 2822) is the responsability of the MUA, except in the case where the envelope is to be built from the headers by the MTA. (I'm using exim, but according to the RFCs, it does nothing 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 cc Reading specs from /usr/lib/gcc-lib/i386-linux/3.2.3/specs Configured with: ../src/configure -v --enable-languages=c,c++,f77,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-objc-gc i386-linux Thread model: posix gcc version 3.2.3 (Debian) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.5.1i (2003-11-05) Copyright (C) 1996-2002 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.24 (i686) [using ncurses 5.3] [using libidn 0.1.14 (compiled with 0.1.14)] 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 -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""mailbox"" PKGDATADIR=""/home/lefevre/share/mutt"" SYSCONFDIR=""/home/lefevre/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.3.24.ats.parent_match.1 patch-1.5.1.vl.savehist.1 >How-To-Repeat: >Fix: }}}" Vincent Lefèvre 1798 Threading is all screwed up :-( mutt 1.5.5.1i defect mutt-dev assigned 2004-02-05T17:09:35-08:00 2008-07-09T03:13:23-07:00 "{{{ Package: mutt Version: 1.5.5.1i Severity: normal -- Please type your report below this line Notice that this is totally bogus (copy/paste from GNU Screen): 753 F feb 05 To Mut Usrs (3,9K) ┌─>Re: backticks in muttrc 754 r L ene 26 To Mut Usrs ( 33) │ ┌─> 755 sL ene 26 To Mut Usrs ( 48) │ ┌─> 756 L ene 26 To Mut Usrs ( 15) │ ┌─> -> 757 sL ene 25 To Mut Usrs ( 33) ┴─>backticks in muttrc Even after syncing the mailbox, switching out of threading view, and then back into threading view, the same crazy tree is displayed again. (Often, switching out of and then back into threading view fixes the problem, especially when one of my messages is misthreaded.) There's no way in the world that the original message in a thread can come from nowhere, and my reply on the top is even stranger, coming from that same ""missing link"" as the original message. (That last message was a reply to the previous message - look at the real messages in question, or I'll post a tarball here if anybody's interested.) I don't know if this has anything to do with the bug at hand, but the fact that I'm running IMAP certainly doesn't help anything ;-/ -- System Information System Version: Linux dave2 2.4.25-pre6 #1 SMP Mon Jan 19 19:27:48 EST 2004 i686 unknown unknown GNU/Linux -- 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 Leyendo especificaciones de /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/specs Configurado con: ./configure --enable-version-specific-runtime-libs --enable-languages=c,c++ Modelo de hilos: posix gcc versión 3.2.3 - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.5.1i (2003-11-05) Copyright (C) 1996-2002 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.25-pre6 (i686) [using ncurses 5.3] Opciones especificadas al compilar: -DOMAIN +DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP +USE_IMAP -USE_GSS +USE_SSL -USE_SASL -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/beta/mutt_cvs/usr/share/mutt"" SYSCONFDIR=""/beta/mutt_cvs/usr/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER Para contactar a los desarrolladores mande un mensaje a . Para reportar un fallo use la utilería flea(1) por favor. --- Begin /home/dave/.muttrc source ~/.mutt/muttrc --- End /home/dave/.muttrc --- Begin /beta/mutt_cvs/usr/etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /beta/mutt_cvs/usr/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /beta/mutt_cvs/usr/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /beta/mutt_cvs/usr/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" --- End /beta/mutt_cvs/usr/etc/Muttrc >How-To-Repeat: >Fix: }}}" lists+mutt_bugs@… 1879 mutt: Wrong ISO2022 -> locale charset conversion charset defect mutt-dev new 2004-05-19T05:31:30-07:00 2007-04-07T14:17:21-07:00 "{{{ Package: mutt Version: 1.5.6-1 Severity: important [NOTE: this bug report has been submitted to the debian BTS as Bug#249626. Please Cc all your replies to 249626@bugs.debian.org .] From: Ambrose Li Subject: mutt: Wrong ISO2022 -> locale charset conversion Date: Tue, 18 May 2004 11:20:07 -0400 Suppose mutt is to display some kanji on a Big5 terminal (either in the header or in the message body), say where each is a kanji. Now further suppose that and do not exist in Big5. Often, mutt will display unexpected output, for example ?? where is a random kanji, apparently having no relation to or or any of their EUC-JP, Shift_JIS, or UTF8 forms. The expected behaviour is to display either ???? for , or to display some kanji equivalent to ; neither of which is mutt's current behaviour. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.23-ow1 Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5 Versions of packages mutt depends on: ii libc6 2.3.2.ds1-12 GNU C Library: Shared libraries an ii libgnutls10 1.0.4-3 GNU TLS library - runtime library ii libidn11 0.4.1-1 GNU libidn library, implementation ii libncursesw5 5.4-3 Shared libraries for terminal hand ii libsasl2 2.1.18-4 Authentication abstraction library ii postfix [mail-transport-age 2.0.19-1 A high-performance mail transport -- no debconf information >How-To-Repeat: >Fix: }}}" Marco d'Itri 1266 create/delete mailboxes not available in the mailboxes view of browser when using imap IMAP 1.4i defect mutt-dev reopened 2005-07-24T09:02:25-07:00 2007-02-07T11:35:57-08:00 "{{{ From twells@fsckit.net Mon Jul 08 20:49:54 2002 Received: from 70.muca.bstn.bstnmaco.dsl.att.net ([12.98.14.70] helo=pulse.fsckit.net) by trithemius.gnupg.org with esmtp (Exim 3.35 #1 (Debian)) id 17Rda6-0007X1-00 for ; Mon, 08 Jul 2002 20:49:54 +0200 Received: from twells by pulse.fsckit.net with local (Exim) id 17Rdbb-0000eg-00 for submit@bugs.guug.de; Mon, 08 Jul 2002 14:51:27 -0400 Subject: mutt-1.4i: create/delete mailboxes not available in the mailboxes view of browser when using imap To: submit@bugs.guug.de Message-Id: From: ""Tabor J. Wells"" Date: Mon, 08 Jul 2002 14:51:27 -0400 Package: mutt Version: 1.4i Severity: normal -- Please type your report below this line In the Mailboxes view of the browser, where it looks like: 1 imaps://localhost/INBOX 2 19 imaps://localhost/INBOX.folder attempting to delete (or create) a mailbox results in ""Delete is only supported for IMAP mailboxes"" (or ""Create is only supported for IMAP mailboxes"" as appropriate). In the Directory view it appears to work as expected. This is somewhat counter-intuitive. :) Thanks, Tabor >How-To-Repeat: >Fix: }}}" """Tabor J. Wells"" " 2015 menu_move_off side effect? display 1.5.9 defect mutt-dev new 2005-07-29T10:41:21-07:00 2009-06-30T07:23:40-07:00 "{{{ http://marc.theaimsgroup.com/?l=mutt-dev&m=111122926423777&w=2 | There is an annoying interaction with page jumps near top of index: | Like with $[menu]_context=7 and $menu_scroll=yes do a | then in index: You should see top page | again, say lines #1 to #34. But you see lines #8 to #41. | | | More generally, I wonder if it would be possible or interesting to | have $[menu]_context act on scrolls (line by line), but still have | full page jumps, perhaps with 0 or 1 line of context. Or *another* | variable to set lines of context in page jump case. The indicator | would still be placed $[menu]_context lines from bottom of next page, | but the said page would be fully new. | | I'm not sure, but seem to have understood that's this very effect on | page jumps that caused not inclusion in Mutt... Source: Discussion by | Michael Elkins on mutt-dev, msgid <20020329183608.GA3064@sigpipe.org>. >How-To-Repeat: >Fix: http://marc.theaimsgroup.com/?l=mutt-dev&m=111228023029057&w=2 + http://marc.theaimsgroup.com/?l=mutt-dev&m=111272711601157&w=2 or some part of http://www.momonga-linux.org/~tamo/patch-1.5.9.ab+tg+tamo.menu.1 }}}" ttakah@… 2019 menu_context itches display defect mutt-dev reopened 2005-08-01T09:33:44-07:00 2007-04-09T21:46:32-07:00 "when the cursor is outside of the area menu_context is supposed to keep it in (this happens quite often when exiting from some sub-view), one is often faced with unexpected scrolls. ""correct position by one line"" seems to be applied blindly regardless of the preceding operation. e.g., moving the cursor in the direction of the ""allowed region"" should not scroll. anyway, the simplest and in many/all cases correct fix would be just re-adjusting the position when returning to a menu." Oswald Buddenhagen 2082 S/MIME signature verification fails on encrypted and signed messages crypto 1.5.11 defect mutt-dev new 2005-09-21T20:12:59-07:00 2007-04-01T20:08:45-07:00 "Everytime I try to open a encrypted and signed message I get the following error: {{{ [-- OpenSSL output follows (current time: Fr 16 Sep 2005 17:38:55 CEST) --] Error reading S/MIME message 18891:error:0D06B08E:asn1 encoding routines:ASN1_d2i_bio:not enough data:a_d2i_fp.c:240: [-- End of OpenSSL output --] }}} This error does not effect the display of the body of the message, it only lets mutt say ""S/MIME signature coud NOT be verired."" I use the default smime_* commands from debians /etc/Muttrc [which can be found at: http://people.debian.org/~adeodato/tmp/2005-09-22/extra/smime-paths.rc --dato]." debian-bugs@… 2088 "%N in folder_format properly displays in ""mailboxes"" but not folder-browser (cTAB) view" IMAP 1.5.13cvs 2007-01-09 defect mutt-dev new 2005-09-25T19:02:16-07:00 2007-01-30T10:53:46-08:00 "{{{ The browser for IMAP folders does not show message/new message counts, mailboxes view contains unnecessary $folder prefix but does not show hierarchy. >How-To-Repeat: missing NEW flag: define %N in folder_format, have new mail in IMAP, change-folder, enter IMAP-path, TAB-expand => no new mail Flag/ number shown, change-folder, TAB-TAB (== mailboxes) => all fine. $folder prefix: - ??? >Fix: Unknown }}}" thomasz@… 2110 decode-copy decode-save create empty parts / messages in case of decoding errors mutt defect mutt-dev new 2005-10-10T14:07:14-07:00 2005-10-10T18:15:02-07:00 "{{{ Mutt creates empty messages if there's some error while decode-{copy,save} e.g. wrong passphrase. It gives an error for pgp/mime types (Could not decrypt PGP message / Could not copy message) or if check-traditional-pgp is used. Nontheless a message with an empty body is copied/saved. This should not happen. In case of decode-save it could result in mail loss. Mutt should warn the user about the error and either copy the message as is (encoded) or refuse to write the message at all. >How-To-Repeat: decode-copy or decode-save an encrpted message and enter a wrong passphrase. >Fix: }}}" michael.tatge@… 2147 Unbale to see the image as a part of email message body - mutt with -i option mutt mutt version = mutt-1.4.1-10 Red Hat Enterprise Linux ES release 4 defect mutt-dev new 2005-12-08T07:21:27-08:00 2005-12-14T13:45:01-08:00 "{{{ Unbale to see the image as a part of email message body - mutt with -i option I am new to mutt. I need help with one of the mutt option. The option is -i My requirement is to send the image as a part of the message body instead of an attachment. This is what I am doing mutt -s ""test email"" myemail@email.com -i file.jpg I am not getting any problem while sending this but while reading I am not seeing this image as a part of message body instead I am getting binary message (some junk characters) I am using yahoo mail and Microsoft outlook to read this email. Can you please help me so that I can see the image as a part of message body? Note: 1) When I send this image as an attachment I can see the image while reading the email in yahoo as well as Microsoft outlook (When I click to open the image) 2) mutt version = mutt-1.4.1-10 3) Red Hat Enterprise Linux ES release 4 Thanks for the help. Raj >How-To-Repeat: mutt -s ""test email"" myemail@email.com -i file.jpg >Fix: Unknown }}}" jagtapr@… 2155 Mutt displays garbage display defect mutt-dev new 2005-12-21T07:46:38-08:00 2007-04-07T14:21:48-07:00 "When displaying e-mail contents, Mutt often leaves garbage from the previous mail on the screen. The same happens when displaying index of e-mails. I tried different combinations: Mutt-1.4.2.1 + ncurses-5.4 or with slang-2.0.5 and problem persists. After CTRL-L screen is OK. >Fix: Clean the screan before displaying current page ? " yawitkow@… 2184 SEGV in mutt_match_rx_list() mutt 1.5.11 (CVS from 2006-02-04) defect mutt-dev new 2006-02-13T07:59:21-08:00 2007-03-30T23:07:16-07:00 "Since I rebuilt mutt from a recent CVS checkout, I observe sporadic crashes. Today I managed to create a core: {{{ Core was generated by `mutt'. Program terminated with signal 11, Segmentation fault. warning: current_sos: Can't read pathname for load map: Eingabe-/Ausgabefehler Reading symbols from /usr/lib/libncursesw.so.5...done. Loaded symbols for /usr/lib/libncursesw.so.5 Reading symbols from /usr/lib/libssl.so.0.9.7...done. Loaded symbols for /usr/lib/libssl.so.0.9.7 Reading symbols from /usr/lib/libcrypto.so.0.9.7...done. Loaded symbols for /usr/lib/libcrypto.so.0.9.7 Reading symbols from /usr/lib/libidn.so.11...done. Loaded symbols for /usr/lib/libidn.so.11 Reading symbols from /usr/lib/tls/libdb-4.3.so...done. Loaded symbols for /usr/lib/tls/libdb-4.3.so Reading symbols from /lib/tls/libc.so.6...done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/tls/libpthread.so.0...done. Loaded symbols for /lib/tls/libpthread.so.0 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /lib/libnss_files.so.2...done. Loaded symbols for /lib/libnss_files.so.2 Reading symbols from /usr/lib/gconv/ISO8859-1.so...done. Loaded symbols for /usr/lib/gconv/ISO8859-1.so #0 0x4035ffcb in re_search_internal () from /lib/tls/libc.so.6 (gdb) bt #0 0x4035ffcb in re_search_internal () from /lib/tls/libc.so.6 #1 0x403613e9 in regexec@@GLIBC_2.3.4 () from /lib/tls/libc.so.6 #2 0x080aa9b8 in mutt_match_rx_list (s=0x8670108 ""TEXTGRID-INTERN@D-GRID.DE"", l=0x403d8ff4) at muttlib.c:1577 #3 0x08074734 in mutt_is_mail_list (addr=0x8671320) at hdrline.c:38 #4 0x0808e91f in mutt_is_list_cc (alladdr=0, a1=0x8671320, a2=0x0) at pattern.c:1004 #5 0x0809c026 in mutt_set_followup_to (e=0x8670490) at send.c:853 #6 0x080a0ea1 in mutt_prepare_envelope (env=0x8670490, final=1) at sendlib.c:2100 #7 0x0809c7b9 in ci_send_message (flags=, msg=0x843c860, tempfile=0x0, ctx=0x8414ed0, cur=0x0) at send.c:1598 #8 0x080623bb in mutt_index_menu () at curs_main.c:1964 #9 0x0807a583 in main (argc=1, argv=0xbfb0d444) at main.c:960 (gdb) up 2 #2 0x080aa9b8 in mutt_match_rx_list (s=0x8670108 ""TEXTGRID-INTERN@D-GRID.DE"", l=0x403d8ff4) at muttlib.c:1577 1577 if (regexec (l->rx->rx, s, (size_t) 0, (regmatch_t *) 0, (int) 0) == 0) (gdb) print *l->rx Cannot access memory at address 0x11ad3c (gdb) print *l $1 = { rx = 0x11ad3c, next = 0x40030d18 } }}} FWIW, the segfault occured when I called send-message for a mailing list posting. >How-To-Repeat: Unfortunately, I don't know yet how to reproduce the crash." ludwig@… 2201 a message/rfc822 misses $display_filter display 1.5.11 defect mutt-dev new 2006-03-28T16:38:31-08:00 2009-06-30T07:25:03-07:00 "{{{ There are two issues regarding display filters: 1) I did a small perl script to strip multiple To: and Cc: lines (yes, I know there are other scripts that do the same but I wanted a simple one to add to my custom ""adds remover"" filter). It's quite simple: ##################################################### #!/usr/bin/perl -p undef $/; s/((To:|Cc:).*\n)(^[\t\s].*\n)+(^[^ ].*)/\1 \[---=| STRIPPED |=---\]\n\4/mg; ##################################################### It works very well stripping the anoying multiple lines in those headers BUT ONLY when mutt does not weed headers ('h' keyword). With stripped headers, it just does not work. I would expect to behave consistently. 2) I also use another filter to strip adds in messages, like the ones added by Yahoo and other mailing lists, or virus scan programs. I call the filters with set display_filter='mutt-display.pl' in my .muttrc file. However, I realized that when I receive a message diggest (many messages in one, that appear as separate 'message/rfc822' attachments), and I try to see one attachment, the filter programs are not called, and the adds are shown. I tried to configure my .mailcap with: message/rfc822; cat %s | mutt-display.pl ; copiousoutput but that didn't make any difference. >How-To-Repeat: For (1), just toggle the view of all the headers with 'h' of a mail with many To: addresses. When all headers are shown, the multiple To: and Cc: lines are stripped. When not shown, they are not stripped (i.e., the filter does not work). For (2), just try to see the attachments using 'v' and then ENTER in the corresponding message. For example, you can use the mutt mailing list daily diggest... :) >Fix: For (1), perhaps this is some silly regexp problem. Not a clue for (2). }}}" mutt-bugs@… 2335 munges messages containing DEL mutt 1.5.11 (CVS 2006-07-05) defect mutt-dev new 2006-07-07T03:57:24-07:00 2006-07-19T15:05:01-07:00 "{{{ Hi ALL. Compose: function extracts a message from a folder, and attaches it as message/rfc822. The message is sent as-is. Verbatim body, and nearly verbatim header, except removal of local only scope lines as From_, (X-)Status:, Content-Length:, and Lines:. The attached mbox contains one message, a table of bytes from 20 to FF, text/plain 8bit CP-1252. When I it, Mutt modifies the message: -1) transcodes 8bit ==> QP -2) adds spurious field: | Content-Disposition: inline; filename=mutt-$HOSTNAME-$UID-$PID-8 The trigger seems to be the presence of control char 7F (DEL). Effect (1) is unexpected, breaks the ""verbatim"" goal, and hurts the whole purpose of sending such tables. But perhaps has some reason. Effect (2) discloses private infos: Bad. Bye! Alain. >How-To-Repeat: >Fix: }}}" Alain Bench 2362 my_foo and environment not interpreted correctly with mailboxes and ignore and probably other commands mutt defect mutt-dev new 2006-07-16T07:11:46-07:00 2006-07-16T09:25:01-07:00 "{{{ set my_mbox_list=""+foo +bar"" mailboxes $my_mbox_list The result seems to interpreted as one argument which is not considered for tokenizing. I was told the problem lies in mutt_extract_token(). >How-To-Repeat: set my_mbox_list=""+foo +bar"" or enviremtn accordingly with existing mailboxes mailboxes $my_mbox_list enter mailboxes view >Fix: Unknown }}}" michael.tatge@… 2390 tag-prefix (and auto_tag) don't work for mutt CVS HEAD defect mutt-dev new 2006-07-28T09:49:42-07:00 1969-12-31T16:00:00-08:00 "{{{ The synopsis says it pretty well. If I tag two unrelated messages and (whether I do it in a macro, or via keypresses), only the highlighted message will be deleted: the tagged messages are ignored. Additionally (and bizarrely), if one of the tagged messages is currently highlighted (and is the one that is deleted), it will lose its tag. This is very different from how works. >How-To-Repeat: tag multiple messages, then >Fix: Unknown }}}" kyle-mutt-dev@… 2402 damaged regexps in folder-hooks mutt 1.5.10 up to CVS defect mutt-dev new 2006-08-02T23:31:38-07:00 2006-08-04T03:15:02-07:00 "{{{ Hello ALL, In Mutt 1.5.10 and more, the regexp in folder-hooks can be damaged in some circumstances, leading to false positive matches. That seems to happen when the regexp both: Has uppercase characters (is case-significant), and begins by an '^' anchor. Example, in muttrc: | folder-hook ^ABC$ yaddahyaddah ...and: | $ cd /tmp | $ touch nomatchABC | $ mutt -f nomatchABC ...beeps and shouts: | yaddahyaddah: unknown command The hook wrongly matched, as if the ^ anchor had been lost. And Tamo's comval.9 feature confirms, the function showing the hook as stored internally: | Status of commands: | | folder-hook | ABC$ | yaddahyaddah ...no more anchor. Note this does not happen with Mutt up to 1.5.9, nor with all-lowercase regexps. Alain. >How-To-Repeat: >Fix: }}}" Alain Bench 2421 mutt does not show number of or indicator for new mails for Maildir mailboxes maildir/mh 1.5.13 defect mutt-dev new 2006-08-15T13:31:06-07:00 2009-07-31T09:50:30-07:00 "{{{ consider a Maildir mailbox 'foo' and its 'cur,new,tmp' subdirectories. mutt does not indicate in the 'change mailbox directory browser' if a Maildir has new unread emails or not. Or if one cares about the change date of a Maildir, the toplevel directory info for 'foo' is shown in the browser, instead of the more accurate directory info for 'foo/new'. The attached patch demonstrates a possible change. Instead of caring about 'foo', the browser.c:examine_directory() looks at 'foo/new' if a subdirectory is in Maildir format. >How-To-Repeat: >Fix: Unknown }}}" olaf@… 2520 Mutt line editor displays nonspacing characters at control escapes mutt 1.4.2.2 defect mutt-dev new 2006-10-10T01:18:12-07:00 2007-11-20T06:23:40-08:00 "{{{ >How-To-Repeat: >Fix: enter.c: lines 38 and 61 should use >= 0 instead of > 0 (line numbers for version 1.4.2.2) }}}" dalias@… 2713 memory allocation bug mutt 1.5.16 defect mutt-dev new 2007-01-26T19:27:55-08:00 2007-09-11T03:53:03-07:00 "{{{ Will malloc checking, Mutt aborts on my mail archives. More precisely, in gdb: set env MallocLogFile /tmp/malloc.log set env MallocGuardEdges 1 set env MallocPreScribble 1 set env MallocScribble 1 set env MallocCheckHeapStart 1060820 set env MallocCheckHeapEach 1 set env MallocCheckHeapAbort 1 set env MallocBadFreeAbort 1 run -F /dev/null -f ~/Mail/oldarc Then I get: Reading /Users/vinc17/Mail/oldarc... 20370 Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x00000000 0x900029c8 in strlen () (gdb) bt #0 0x900029c8 in strlen () #1 0x90130748 in _simple_vdprintf () #2 0x9012bc44 in malloc_printf () #3 0x90116bcc in szone_check () #4 0x90002c1c in malloc () #5 0x0006b538 in safe_malloc (siz=1) at lib.c:149 #6 0x0006b744 in safe_strdup (s=0x995f4 ""plain"") at lib.c:220 #7 0x0004c154 in mutt_read_rfc822_header (f=0xa000db34, hdr=0x15dc280, user_hdrs=0, weed=0) at parse.c:1319 #8 0x0003d9b4 in maildir_parse_message (magic=4, fname=0xbfffd218 ""/Users/vinc17/Mail/oldarc/cur/1076519289.5337_386.ay:2,S"", is_old=1, _h=0x15dc280) at mh.c:603 #9 0x0003ddf0 in maildir_delayed_parsing (ctx=0x11062e0, md=0x0, progress=0xbfffd38c) at mh.c:990 #10 0x0004022c in mh_read_dir (ctx=0x11062e0, subdir=0xa1a70 ""cur"") at mh.c:1047 #11 0x000402a0 in maildir_read_dir (ctx=0x11062e0) at mh.c:1059 #12 0x000411cc in mx_open_mailbox (path=0xb0cb4 """", flags=0, pctx=0x20) at mx.c:691 #13 0x00037730 in main (argc=5, argv=0xbfffe104) at main.c:960 /tmp/malloc.log contains: [...] mutt(28682) malloc: MallocCheckHeap: PASSED check at 1060835th operation mutt(28682) malloc: MallocCheckHeap: PASSED check at 1060836th operation mutt(28682) malloc: *** invariant broken for 0x1861400 (2 free in a row) mutt(28682) malloc: *** small region 2 incorrect szo Then I don't know how to debug this. The bug is always reproducible, but on a smaller mailbox containing hundreds of messages around the one that appears in the backtrace, it no longer occurs. >How-To-Repeat: >Fix: Unknown }}}" vincent@… 2735 printing mails with/without attachments mutt 1.5.13 defect mutt-dev new 2007-01-31T21:58:22-08:00 1969-12-31T16:00:00-08:00 "{{{ scenario: There several tagged messages. All of the tagged messages are to be printed. wish: An option to print the emails with or without their attachments. >How-To-Repeat: >Fix: Copy messages for printing in a separate mailbox, delete all attachments, tag them, print them. }}}" slrn_robert@… 2775 OpenPGP message headers not shown on display-toggle-weed crypto defect mutt-dev new 2007-02-17T23:29:42-08:00 2009-06-30T07:26:37-07:00 "{{{ When viewing message headers of a decrypted GPG message, the headers that are part of the encrypted block do not show up. Note, however, that if the encrypted message itself has multiple parts (e.g., you included an attachment), those subpart headers do indeed show up. >How-To-Repeat: Email yourself a GPG-encrypted message, decrypt/open the message, and press 'h' to view headers. The main message headers show up but the headers in the decrypted GPG block do not. Now try saving the message to a new file and decrypting it on the command line with `gpg -d`. You'll see something such as the following: Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit [...decrypted text...] >Fix: Unknown }}}" software@… 2776 Header colors not applied to MIME subpart headers display 1.5.13 defect mutt-dev new 2007-02-17T23:35:09-08:00 2007-04-07T07:26:34-07:00 "Header colors (e.g., ""color hdrdefault yellow black"") are not applied to the headers in MIME subparts when displaying headers. The headers are shown in the default body text color. >How-To-Repeat: Set your hdrdefault color to something other than the body text color. Send yourself a message with an attachment, then view the headers. The subpart headers (e.g., Content-Type, Content-Disposition) will be the color of the body text, not hdrdefault." software@… 2791 problems with filename MIME parameter and newlines display 1.5.13 defect mutt-dev new 2007-02-20T19:58:01-08:00 2007-04-02T18:26:14-07:00 "Create a file with embedded newlines. Attach it in mutt. Mail it. View the results in mutt and see that part of the filename ends up shown as attachment content. Whilst RFC2183 has cautions for receiving MUAs, it says little about restrictions on sending MUAs. It seems reasonable though to expect that the MUA be able to parse its own output. :-) >How-To-Repeat: Using zsh: {{{ % echo foo > $'foo\n.\nbar' % mutt -a foo?* -s test recipient % mutt }}} view message In a slightly different test, same file, I saw: {{{ [-- Attachment #3: foo --] [-- Type: text/plain, Encoding: 7bit, Size: 0.1K --] bar"" foo }}} Viewing headers revealed: {{{ [-- Attachment #3: foo --] [-- Type: text/plain, Encoding: 7bit, Size: 0.1K --] Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=""foo . bar"" foo }}} >Fix: Map newline-matching characters to space? Or question-mark." muttbug@… 2803 """:source file"" errors will be overwritten when file has ""set sort=..."" and folder contains msgs" mutt 1.5.14cvs defect mutt-dev new 2007-02-27T12:39:56-08:00 2008-04-08T12:15:38-07:00 "When a sort order change is "":source""d via ""set sort=..."" != unsorted to provoke a call to mutt_sort_headers, then any/ all error messages in that file are not visible due to the ""sorting ..."" msg, which comes after the :source-errors are parsed/ displayed. Even setting sleep_time doesn't help because mutt_sleep isn't called anywhere between sourcing and redisplaying the index. How-To-Repeat: {{{ file: set sort=size blablub (literal to provoke an error) }}} open folder with some mails, then source the above file. " rado 2804 Bug#305069: mutt: extra redraw, scroll when resuming display defect mutt-dev new 2007-02-27T13:15:02-08:00 2009-06-30T07:26:27-07:00 "{{{ The following was submitted as Debian bug #305069: ----- Forwarded message from Andrew Pimlott ----- Date: Sun, 17 Apr 2005 19:46:00 -0700 From: Andrew Pimlott Reply-To: Andrew Pimlott , 305069@bugs.debian.org To: Debian Bug Tracking System Subject: Bug#305069: mutt: extra redraw, scroll when resuming Package: mutt Version: 1.5.9-1 Severity: normal Starting with the upgrade to 1.5.8, mutt has displayed a weird behavior when resuming from a suspend while displaying the message index. What appears to happen is, it initially redraws the screen as it was before, as expected; but then it immediately draws the screen again, this time scrolling so that the selected message is at the bottom of the screen. (Or, with nomenu_scroll, so that the index is at a natural ""page"".) Even if was already in this position, so that no scrolling is done, the redraw is visible as an annoying flash. To reproduce, open a mailbox (with menu_scroll set) with more than one screen-full of messages, go to the end, then go up one message, so that you are on the second to last line of the index. Suspend with ctrl-Z and resume. You should see that the index is scrolled so that the message you are on is now the last line of the index. Andrew ----- End forwarded message ----- I can confirm this for 1.5.14. Christoph -- cb@df7cb.de | http://www.df7cb.de/ >Fix: Unknown }}}" Christoph Berg 1138 mutt shouldn't ask for passphrases for keys that doesn't have a secret-key available crypto enhancement mutt-dev new 2002-03-29T23:35:46-08:00 2009-06-30T07:32:26-07:00 "[NOTE: this bug report has been submitted to the debian BTS as Bug!#140432. Please Cc all your replies to 140432@bugs.debian.org .] {{{ From: Gerfried Fuchs Date: Fri, 29 Mar 2002 10:28:25 +0100 }}} Hi! I sometimes get bounces for encrypted messages I sent and think it's quite annoying that mutt seems to ask for the passphrase for its decryption but can't do that for obviously I don't have the secret-key for that message. This is just one kind of situation when this happens, there can be other reasons, too. So it would be great if mutt would be able to check the availability of a secret-key for decryption *before* it asks for the passphrase so it doesn't ask bogus questions where every answer simply is wrong. If this is implemented I guess this would also quite easily close the other bugreport I just submitted`[1]` for displaying the keyid for which key it wants the passphrase for. If you check for the secret key you can extract the info you need in there. TIA, Alfie `[1] #140430` " Marco d'Itri 1317 wish $edit_charset charset 1.4i enhancement mutt-dev new 2002-08-16T22:22:09-07:00 2009-07-06T15:41:12-07:00 "{{{ Package: mutt Version: 1.4i Severity: wishlist -- Please type your report below this line It would be nice if the charset muttrc configuration variable could be split into charset and edit_charset. charset would apply to the display and built-in editor, and edit_charset would apply when an external editor is used. My terminal program supports ISO-8859-1 characters, so I have charset set to ISO-8859-1//TRANSLIT (I need //TRANSLIT on the end so I can see things like left and right double quotes.) My editor, vim, supports UTF-8. The way things currently stand, I can reasonably read messages, but certain information is lost (e.g. double left quotes and double right quotes both become ASCII double quotes.) If I could configure mutt to convert the message to UTF-8 before calling vim, I could reply with minimal loss of information (depending on how send_charset is set, but that's exactly what we'd want.) -Tony -- 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 cc cc: Error: no source, object or ucode file specified - CFLAGS -std1 -fast -O4 -tune host -arch host -D_XOPEN_SOURCE_EXTENDED -- Mutt Version Information Mutt 1.4i (2002-05-29) 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: OSF1 V4.0 (alpha) 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/local/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/spool/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please use the flea(1) utility. Received: (at submit) by bugs.guug.de; 18 Jan 2001 15:32:24 +0000 From nil@wh36-b507.stud.uni-karlsruhe.de Thu Jan 18 16:32:23 2001 Received: from mailgate.rz.uni-karlsruhe.de (exim@mailgate.rz.uni-karlsruhe.de [129.13.64.97]) by sigtrap.guug.de (8.9.3/8.9.3/Debian/GNU) with ESMTP id QAA28955 for ; Thu, 18 Jan 2001 16:32:23 +0100 Received: from wh36-b507.stud.uni-karlsruhe.de (root@wh36-b507.stud.uni-karlsruhe.de [172.20.230.117]) by mailgate.rz.uni-karlsruhe.de with esmtp (Exim 3.16 #1) id 14JH30-0007Kk-00; Thu, 18 Jan 2001 16:32:22 +0100 Received: (from nil@localhost) by wh36-b507.stud.uni-karlsruhe.de (8.11.1/8.11.1/Debian 8.11.0-6) id f0IFWMF03963; Thu, 18 Jan 2001 16:32:22 +0100 Date: Thu, 18 Jan 2001 16:32:22 +0100 Message-Id: <200101181532.f0IFWMF03963@wh36-b507.stud.uni-karlsruhe.de> From: dominique@unruh.de Subject: mutt-1.3.13i: There should be a variable editor_charset To: submit@bugs.guug.de Package: mutt Version: 1.3.12-2 Severity: wishlist -- Please type your report below this line This is a feature request. There should be a variable editor_charset, which determines the charset in which an external editor reads and writes files. At the moment it is always the same as the terminal encoding ($charset). This feature is e.g. motivated by the following situation: Many users may have an unicode-editor (as yudit or emacs+mule-ucs), but do not want to configure their mutt terminal for UTF-8 support (because this is a little tricky and requires recompilation of mutt in most cases). DniQ. -- Mutt Version Information Mutt 1.3.13i (2000-12-31) Copyright (C) 1996-2000 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.2.17 [using ncurses 5.0] 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=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" SHAREDIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" Tony Leneis 1369 change of file designated for attachement not always realized mutt enhancement mutt-dev new 2002-10-31T13:30:31-08:00 2005-08-02T03:45:02-07:00 "{{{ Package: mutt Version: 1.4i compose a message, attach a file, and postpone it. modify the attached file. recall the message and send it. as opposed to what normally happens, you are _not_ asked, whether the encoding of the attachement should be updated. >How-To-Repeat: >Fix: }}}" Oswald Buddenhagen 1378 compile with slang-ja mutt 1.4i enhancement mutt-dev new 2002-11-07T10:05:55-08:00 2005-09-04T11:51:05-07:00 "{{{ Package: mutt Version: 1.4i Severity: normal -- Please type your report below this line I can't compile Mutt with slang-ja library. Debian has ""slang1-ja"" package apart from ""slang1"" package. ""slang1-ja-dev"" package includes these files. % dpkg -L slang1-ja-dev | grep ""/usr/lib"" /usr/lib /usr/lib/libslang-ja.a /usr/lib/libslang-ja.so I changed configure.in. --- mutt-1.4/configure.in.orig Sat Nov 2 16:31:57 2002 +++ mutt-1.4/configure.in Sat Nov 2 16:46:37 2002 @@ -167,9 +167,13 @@ dnl --- now that we've found it, check the link + AC_CHECK_LIB(slang-ja, SLtt_get_terminfo, + [MUTTLIBS=""$MUTTLIBS -lslang-ja -lm""], + [ AC_CHECK_LIB(slang, SLtt_get_terminfo, [MUTTLIBS=""$MUTTLIBS -lslang -lm""], [AC_MSG_ERROR(unable to compile. check config.log)], -lm) + ]) ], -- 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 -g -O2 >How-To-Repeat: >Fix: }}}" mab@… 1421 Mutt generates base64 in Subject MIME 1.5.2i enhancement mutt-dev new 2002-12-13T05:38:33-08:00 2009-06-30T07:33:00-07:00 "{{{ Package: mutt Version: mutt-1.0.1i-6 Severity: normal -- Please type your report below this line Mutt generates base64 in the Subject header field: Subject: Re: [RA2002] Corrections =?iso-8859-1?Q?ap?= =?iso-8859-1?B?cuhz?= la relecture where the decoded subject is: Re: [RA2002] Corrections après la relecture Just for an accented character, this is not a good idea, in particular because some old mailers don't support base64 in headers. Some other mailers forward messages in the body with headers undecoded, and base64 makes things worse for the user who tries to read. When there isn't a big size difference between QP and base64 (which would always be the case in French, for instance), Mutt should use QP. -- System Information System Version: Linux greux.loria.fr 2.2.17 #13 SMP Tue Dec 12 15:26:51 MET 2000 i686 unknown RPM Packager: Red Hat, Inc. RedHat Release: Red Hat Linux release 6.2 (Zoot) -- 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 ccache gcc Reading specs from /users/spaces/logiciels/gcc-3.0/linux/lib/gcc-lib/i686-pc-linux-gnu/3.0/specs Configured with: ../gcc-3.0/configure --prefix=/users/spaces/logiciels/gcc-3.0 --exec-prefix=/users/spaces/logiciels/gcc-3.0/linux Thread model: single gcc version 3.0 - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.2i (2002-12-06) Copyright (C) 1996-2002 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.2.17 (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 -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_PGP +HAVE_SMIME -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=""/users/spaces/logiciels/ispell/linux/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""mailbox"" PKGDATADIR=""/users/spaces/lefevre/share/mutt"" SYSCONFDIR=""/users/spaces/lefevre/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.3.24.ats.parent_match.1 patch-1.5.1.vl.savehist.1 >How-To-Repeat: >Fix: }}}" vincent@… 1452 wish rename attachment in compose menu mutt enhancement mutt-dev reopened 2003-02-02T00:48:11-08:00 2005-08-16T16:16:19-07:00 "{{{ Package: mutt Version: 1.4i When attaching a file to an email it is useful to be able to change the name of the attachment. This is particularly true if the recepients system is likely to do something unwanted based on the attachments name. However the mutt facility which appears to to this 'R', seems to rename the actual file on the sending system, not rename the attachment itself. I can't ever see the current behaviour being desirable. I spotted this with mutt 1.2.5.1i (on netbsd), that version of the source doesn't seem to have any way of separating the attachment name from the filename. mutt 1.4i (latest on netbsd pkgsrc) exhibits the same behaviour. David -- David Laight: david@l8s.co.uk >How-To-Repeat: >Fix: }}}" David Laight 1576 no search on names with reverse_alias mutt 1.5.4i enhancement mutt-dev new 2003-06-21T00:25:57-07:00 2005-08-24T13:16:53-07:00 "{{{ Package: mutt Version: 1.5.4-1 Severity: normal -- Please type your report below this line When using the reverse_alias option some sender names, which otherwise don't appear in the emails, are shown in the index. If I search for them or try to limit the index, these names are not taken into consideration. This is very unintuitiv since you have no way (short of deactivating the reverse_alias feature) of knowing if the sender included her/his name somewhere in the message for search/limit to work. Thanks, Chris -- System Information Debian Release: testing/unstable Kernel Version: Linux anthony 2.4.12 #1 Fri Oct 19 11:40:33 PDT 2001 i686 GNU/Linux Versions of the packages mutt depends on: ii libc6 2.3.1-14 GNU C Library: Shared libraries and Timezone ii libdb4.0 4.0.14-1 Berkeley v4.0 Database Libraries [runtime] ii libidn9 0.1.11-1 GNU libidn library, implementation of IETF I ii libncurses5 5.3.20021109-1 Shared libraries for terminal handling ii libsasl7 1.5.27-2 Authentication abstraction library. exim Not installed or no info ii qmail 1.03-20 Secure, reliable, efficient, simple mail tra ^^^ (Provides virtual package mail-transport-agent) -- 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 cc Reading specs from /usr/lib/gcc-lib/i386-linux/3.3/specs Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-debug --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i386-linux Thread model: posix gcc version 3.3 (Debian) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.4i (2003-03-19) Copyright (C) 1996-2002 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.12 (i686) [using ncurses 5.3] [using libidn 0.1.11 (compiled with 0.1.11)] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +IMAP_EDIT_THREADS -USE_GSS -USE_SSL +USE_GNUTLS +USE_SASL -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO +USE_CACHE ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.5.3.Md.gpg_status_fd patch-1.3.23.1.ametzler.pgp_good_sign patch-1.4.Md.gpg-agent patch-1.5.1.cd.edit_threads.9.2 patch-1.5.3.Md.etc_mailname_gethostbyname patch-1.3.27.bse.xtitles.1 Md.muttbug Md.use_debian_editor patch-1.4.admcd.gnutlsdlopen.53d patch-1.5.4.Z.hcache.8 patch-1.4.admcd.gnutlsbuild.53d patch-1.4.admcd.gnutls.55d patch-1.5.3.rr.compressed.1 --- Begin /home/chs/.mutt/muttrc unset save_empty # remove empty mbox'es (maildirs are not deleted) set reverse_alias unset pager_stop # don't run over end of messages bind index ""^"" first-entry bind pager ""^"" top # is default bind index G last-entry # instead of `*' bind pager G bottom bind index b previous-page bind pager b previous-page bind index B bounce-message # needed to be redefined bind index "" "" next-page bind index parent-message bind pager parent-message bind index next-entry bind pager next-entry bind index next-subthread bind pager next-subthread bind index previous-subthread bind pager previous-subthread macro pager i ""!dict | less\eb\eb\Cb\Cb"" macro index i ""!dict | less\eb\eb\Cb\Cb"" macro index D ""s=spam\n"" macro pager D ""s=spam\n"" macro index M ""C~/Maildir\n"" macro pager M ""C~/Maildir\n"" macro index S ""C~/Maildir\ns"" macro pager S ""C~/Maildir\ns"" set pipe_decode=yes set postponed=""~/Mail.d/drafts"" set status_format=""-%r- %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---"" bind editor ""\e\t"" complete-query bind editor ""\Ct"" transpose-chars set hide_limited=no set hide_top_limited=no set hide_missing=no set hide_top_missing=no set thread_received=yes set history=30 set help=no set move=no set delete=yes macro pager A ""|/home/chs/.mutt/mail2muttalias.py ~/.mutt/aliases\n:source ~/.mutt/aliases\n"" ""Offer any email address as alias"" macro pager \ea ""!vim ~/.mutt/aliases\n:source ~/.mutt/aliases\n"" macro pager l """" ""Goto index and limit"" auto_view text/html text/enriched application/x-gunzip application/postscript application/x-tar-gz alternative_order text/enriched text/plain text application/postscript image/* set confirmappend=no set thorough_search set pgp_create_traditional=ask-no set pgp_strict_enc=yes #no # for phf set pgp_replyencrypt=yes set pgp_replysign=yes set pgp_replysignencrypted=yes set pgp_show_unusable=yes # just testing... remove later set pgp_timeout=600 # default 300 secs set encode_from=yes set pager_index_lines=5 push V # show version on start-up set locale=""en_US"" set charset=""iso-8859-1"" set allow_8bit set fast_reply set forward_format=""Fwd: %s"" set index_format=""%2C %Z %[%y-%m-%d %T] %Y|%-15.15F %s"" color index magenta black ~T # Tagged color index red black ~F # Flagged set folder=/home/chs/Mail.d set record=+Sent unset strict_threads set thread_received set default_hook=""~f %s !~P | (~P ~C %s)"" send-hook . ""unmy_hdr from"" folder-hook . 'set sort=threads; set sort_aux=last-date-received' folder-hook . 'set index_format=""%2C %Z %[%y-%m-%d %T] %Y%?M?(#%03M)&(%4l)?%-15.15F %s""' folder-hook . 'set from=cstork@ics.uci.edu' folder-hook . 'unmy_hdr to' folder-hook debian-devel-changes-list 'set sort=subject; set sort_aux=date-sent' folder-hook Box 'set index_format=""%2C %Z %[%y-%m-%d %T] %Y|%-15.15L %s""' source 'echo set hide_limited=yes > /home/chs/.mutt/test.output'| source /home/chs/.mutt/mutt.conf source /home/chs/.mutt/mutthooks macro index ""\ :unhook save-hook fcc-save-hook\n\ ! /home/chs/postgresql/muttreconf.py > /home/chs/.mutt/mutt.conf\n\ :source /home/chs/.mutt/mutt.conf\n"" \ ""Reread Hooks"" macro pager ""\ :unhook save-hook fcc-save-hook\n\ ! /home/chs/postgresql/muttreconf.py > /home/chs/.mutt/mutt.conf\n\ :source /home/chs/.mutt/mutt.conf\n"" \ ""Reread Hooks"" macro index ~ /~f ""Search Shortcut"" send-hook . ""set signature=~/.signature"" set reverse_name set use_from set from=cstork@ics.uci.edu set realname=""Christian H. Stork"" set alternates='cstork@((.+\.)?ics|ea.oac)\.)?uci.edu|cs(-.+)?@nil.ics.uci.edu|cstork@roentgeninstitut.de|c_stork@yahoo.com|(chs|mailtest)@deby.dyndns.org|cstork@tucu\.net|mailtest@localhost|chs(-.+)?@eichenlaub.de' set signature=~/.signature set hostname=ics.uci.edu set use_domain set editor=""vim -c 'set tw=72 ft=mail' -c 'syntax on'"" set askcc set abort_nosubject=ask-yes set abort_unmodified=ask-yes set fast_reply set mail_check=100 set timeout=0 # 600 is default set imap_user=mailtest set imap_pass=uwimap2k set imap_passive set imap_servernoise # get imap server error messages unset imap_peek # marks msgs as read as soon as fetched from imap server set spoolfile=""=Box"" #/var/spool/chs default on deby set mbox=""=Read"" # ~/Maildir"" default mbox-hook ~/Maildir2 ~/Maildir2.read set mbox_type=mbox #Maildir set check_new source ~/.mutt/aliases set alias_file=~/.mutt/aliases unset wait_key set followup_to hdr_order From: Reply-To: Subject: Date: To: Cc: ignore * unignore from: date subject to cc reply- resent-from mail- delivered-to bind editor ""\e"" kill-word bind editor ""\e"" kill-word bind editor delete-char set envelope_from set use_8bitmime unset bounce_delivered macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!zless /usr/share/doc/mutt/manual.txt.gz\n"" ""Show Mutt documentation"" macro index ""!zless /usr/share/doc/mutt/manual.txt.gz\n"" ""Show Mutt documentation"" macro pager ""!zless /usr/share/doc/mutt/manual.txt.gz\n"" ""Show Mutt documentation"" color normal white black color attachment brightyellow black color hdrdefault cyan black color indicator black cyan color markers brightred black color quoted green black color signature cyan black color status brightgreen blue color tilde blue black color tree white black color header brightgreen black ^From: color header brightgreen black ^Reply-To: color header brightcyan black ^To: color header brightcyan black ^Cc: color header brightred black ^Subject: color body brightwhite black (http|ftp)://[\-\.\,/%~_:?\#a-zA-Z0-9]+ color index brightwhite black ~O color index brightyellow black ~N set rfc2047_parameters charset-hook windows-1250 CP1250 charset-hook windows-1251 CP1251 charset-hook windows-1252 CP1252 charset-hook windows-1253 CP1253 charset-hook windows-1254 CP1254 charset-hook windows-1255 CP1255 charset-hook windows-1256 CP1256 charset-hook windows-1257 CP1257 charset-hook windows-1258 CP1258 set ispell=ispell set pgp_decode_command=""/usr/bin/gpg --status-fd=2 %?p?--passphrase-fd 0? --no-verbose --quiet --batch --output - %f"" set pgp_verify_command=""/usr/bin/gpg --status-fd=2 --no-verbose --quiet --batch --output - --verify %s %f"" set pgp_decrypt_command=""/usr/bin/gpg --status-fd=2 --passphrase-fd 0 --no-verbose --quiet --batch --output - %f"" set pgp_sign_command=""/usr/bin/gpg --no-verbose --batch --quiet --output - --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a? %f"" set pgp_clearsign_command=""/usr/bin/gpg --no-verbose --batch --quiet --output - --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f"" set pgp_encrypt_only_command=""/usr/lib/mutt/pgpewrap /usr/bin/gpg --batch --quiet --no-verbose --output - --encrypt --textmode --armor --always-trust -- -r %r -- %f"" set pgp_encrypt_sign_command=""/usr/lib/mutt/pgpewrap /usr/bin/gpg --passphrase-fd 0 --batch --quiet --no-verbose --textmode --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f"" set pgp_import_command=""/usr/bin/gpg --no-verbose --import -v %f"" set pgp_export_command=""/usr/bin/gpg --no-verbose --export --armor %r"" set pgp_verify_key_command=""/usr/bin/gpg --verbose --batch --fingerprint --check-sigs %r"" set pgp_list_pubring_command=""/usr/bin/gpg --no-verbose --batch --quiet --with-colons --list-keys %r"" set pgp_list_secring_command=""/usr/bin/gpg --no-verbose --batch --quiet --with-colons --list-secret-keys %r"" set pgp_good_sign=""^\\[GNUPG:\\] VALIDSIG"" --- End /home/chs/.mutt/muttrc --- Begin /etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines ignore date delivered-to precedence errors-to in-reply-to user-agent ignore x-loop x-sender x-mailer x-msmail-priority x-mimeole x-priority ignore x-accept-language x-authentication-warning thread- priority bind editor ""\e"" kill-word bind editor ""\e"" kill-word bind editor delete-char unset use_domain unset use_from set sort=threads unset write_bcc unset bounce_delivered macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' set pipe_decode macro generic ""!zcat /usr/share/doc/mutt/manual.txt.gz | sensible-pager\n"" ""Show Mutt documentation"" macro index ""!zcat /usr/share/doc/mutt/manual.txt.gz | sensible-pager\n"" ""Show Mutt documentation"" macro pager ""!zcat /usr/share/doc/mutt/manual.txt.gz | sensible-pager\n"" ""Show Mutt documentation"" open-hook \\.gz$ ""gzip -cd %f > %t"" close-hook \\.gz$ ""gzip -c %t > %f"" append-hook \\.gz$ ""gzip -c %t >> %f"" open-hook \\.bz2$ ""bzip2 -cd %f > %t"" close-hook \\.bz2$ ""bzip2 -c %t > %f"" append-hook \\.bz2$ ""bzip2 -c %t >> %f"" color normal white black color attachment brightyellow black color hdrdefault cyan black color indicator black cyan color markers brightred black color quoted green black color signature cyan black color status brightgreen blue color tilde blue black color tree red black set pgp_decode_command=""/usr/bin/gpg --charset utf-8 --status-fd=2 %?p?--passphrase-fd 0? --no-verbose --quiet --batch --output - %f"" set pgp_verify_command=""/usr/bin/gpg --status-fd=2 --no-verbose --quiet --batch --output - --verify %s %f"" set pgp_decrypt_command=""/usr/bin/gpg --status-fd=2 --passphrase-fd 0 --no-verbose --quiet --batch --output - %f"" set pgp_sign_command=""/usr/bin/gpg --no-verbose --batch --quiet --output - --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a? %f"" set pgp_clearsign_command=""/usr/bin/gpg --charset utf-8 --no-verbose --batch --quiet --output - --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f"" set pgp_encrypt_only_command=""/usr/lib/mutt/pgpewrap /usr/bin/gpg --charset utf-8 --batch --quiet --no-verbose --output - --encrypt --textmode --armor --always-trust -- -r %r -- %f"" set pgp_encrypt_sign_command=""/usr/lib/mutt/pgpewrap /usr/bin/gpg --charset utf-8 --passphrase-fd 0 --batch --quiet --no-verbose --textmode --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f"" set pgp_import_command=""/usr/bin/gpg --no-verbose --import -v %f"" set pgp_export_command=""/usr/bin/gpg --no-verbose --export --armor %r"" set pgp_verify_key_command=""/usr/bin/gpg --verbose --batch --fingerprint --check-sigs %r"" set pgp_list_pubring_command=""/usr/bin/gpg --no-verbose --batch --quiet --with-colons --list-keys %r"" set pgp_list_secring_command=""/usr/bin/gpg --no-verbose --batch --quiet --with-colons --list-secret-keys %r"" set pgp_good_sign=""^\\[GNUPG:\\] GOODSIG"" set smime_ca_location=""~/.smime/ca-bundle.crt"" set smime_certificates=""~/.smime/certificates"" set smime_keys=""~/.smime/keys"" set smime_pk7out_command=""openssl smime -verify -in %f -noverify -pk7out"" set smime_get_cert_command=""openssl pkcs7 -print_certs -in %f"" set smime_get_signer_cert_command=""openssl smime -verify -in %f -noverify -signer %c -out /dev/null"" set smime_get_cert_email_command=""openssl x509 -in %f -noout -email"" set smime_import_cert_command=""/usr/lib/mutt/smime_keys add_cert %f"" set smime_encrypt_command=""openssl smime -encrypt -%a -outform DER -in %f %c"" set smime_sign_command=""openssl smime -sign -signer %c -inkey %k -passin stdin -in %f -certfile %i -outform DER"" set smime_decrypt_command=""openssl smime -decrypt -passin stdin -inform DER -in %f -inkey %k -recip %c"" set smime_verify_command=""openssl smime -verify -inform DER -in %s %C -content %f"" set smime_verify_opaque_command=""openssl smime -verify -inform DER -in %s %C"" --- End /etc/Muttrc >How-To-Repeat: >Fix: }}}" cs-muttbug@… 1605 MIME header copied into mail reply with 1.5.4i MIME 1.5.4i enhancement mutt-dev new 2003-08-02T03:51:09-07:00 2009-06-30T07:32:48-07:00 "{{{ Package: mutt Version: 1.5.4i Severity: normal -- Please type your report below this line I noticed that when replying to some PGP-signed messages from Kmail, I get a ""Content-Description: signed data"" at the top of the reply. Attached is a mail that can duplicate this. Just load the message and try to reply to it. I'm not sure if this is a mutt issue or a Kmail issue. -- System Information System Version: Linux claude.jabberwocky.com 2.4.18-3 #1 Thu Apr 18 07:37:53 EDT 2002 i686 unknown RedHat Release: Red Hat Linux release 7.3 (Valhalla) -- 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-redhat-linux/2.96/specs gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-112) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.4i (2003-03-19) Copyright (C) 1996-2002 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.18-3 (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 -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. }}}" David Shaw 1863 mutt: ispell should check Subject a.o. header fields, too mutt enhancement mutt-dev new 2004-04-20T20:36:34-07:00 2005-08-06T23:08:49-07:00 "{{{ Package: mutt Version: 1.3.28-2.2 Severity: normal [NOTE: this bug report has been submitted to the debian BTS as Bug#244812. Please Cc all your replies to 244812@bugs.debian.org .] From: Jan Minar Subject: mutt: ispell should check Subject a.o. header fields, too Date: Tue, 20 Apr 2004 05:28:43 +0200 Hi. The spell command (bound to `i' in the message composition screen) should check Subject, as well as other header fields where it is reasonable: Keywords, Organization, Comments, and the free-form parts in the other RFC 2822 fields (anything apart from the <>-delimited things, it seems to me). There are many other extensions to the standard, and some of those fields should be spellchecked, some not. Maybe some of them should be checked against special dictionaries or patterns, that would e.g. unveil likely incorrect syntax. Cheers, Jan. -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux kontryhel 2.4.26-jan #3 SMP Mon Apr 19 05:00:00 CEST 2004 i686 Locale: LANG=C, LC_CTYPE=cs_CZ.ISO-8859-2 Versions of packages mutt depends on: ii libc6 2.2.5-11.5 GNU C Library: Shared libraries an ii libncurses5 5.2.20020112a-7 Shared libraries for terminal hand ii libsasl7 1.5.27-3 Authentication abstraction library ii postfix [mail-transport- 1.1.11-0.woody3 A high-performance mail transport -- ""To me, clowns aren't funny. In fact, they're kind of scary. I've wondered where this started and I think it goes back to the time I went to the circus, and a clown killed my dad."" >How-To-Repeat: >Fix: }}}" Marco d'Itri 1874 pipe-tagged does not always include From_ lines mutt 1.5.5.1i enhancement mutt-dev new 2004-05-14T01:17:56-07:00 2005-10-26T04:53:53-07:00 "{{{ Package: mutt Version: mutt-1.5.5.1i (CVS) Severity: normal -- Please type your report below this line Hi, piping multiple tagged articles into one command does not necessarily include From_ lines. What I have figured so far: piping multiple messages from a mbox folder includes the From_ lines. Piping multiple messages from a maildir folder or from the web.de IMAP server does NOT include the From_ line. I would appreciate an option to make mutt either run the command or-each-tagged mail or, alternatively, separate the individual messages by a (possibly made up) From_ line. Background: I like to tag messages from my ""=unsure"" folder and then pipe all tagged into ""bogofilter -M -s -v"" or ""bogofilter -M -n -v"", this appears to work with mbox only at this time. -- System Information System Version: Linux merlin 2.6.6 #49 Tue May 11 01:53:19 CEST 2004 i686 unknown unknown GNU/Linux -- 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/i586-suse-linux/3.3.1/specs Konfiguriert mit: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --enable-languages=c,c++,f77,objc,java,ada --disable-checking --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit i586-suse-linux Thread model: posix gcc-Version 3.3.1 (SuSE Linux) - CFLAGS -Wall -pedantic -pipe -g -march=pentium -mcpu=i686 -Os -Wall -W -- Mutt Version Information Mutt 1.5.5.1i (2004-02-01) Copyright (C) 1996-2002 Michael R. Elkins und andere. Mutt übernimmt KEINERLEI GEWÄHRLEISTUNG. Starten Sie `mutt -vv', um weitere Details darüber zu erfahren. Mutt ist freie Software. Sie können es unter bestimmten Bedingungen weitergeben; starten Sie `mutt -vv' für weitere Details. System: Linux 2.6.6 (i686) [using ncurses 5.3] [using libidn 0.1.14 (compiled with 0.1.14)] Einstellungen bei der Compilierung: -DOMAIN +DEBUG +HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP -USE_GSS +USE_SSL -USE_SASL -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""Maildir/"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER Um die Entwickler zu kontaktieren, schicken Sie bitte eine Nachricht (in englisch) an . Um einen Bug zu melden, verwenden Sie bitte das Programm flea(1). >How-To-Repeat: >Fix: }}}" Matthias Andree 1880 wish: rebind to generic mutt 1.4.2.1i enhancement mutt-dev assigned 2004-05-19T04:29:57-07:00 2009-07-25T00:28:10-07:00 "{{{ Package: mutt Version: 1.4.2.1i Severity: normal -- Please type your report below this line Quite easy to test. Have the following key bindings defined: # bind index ' ' noop bind generic ' ' next-page # Start mutt, go to index and try hitting space. Unbound key error message is displayed. It will go away if one adds ""bind index ' ' next-page"" at the bottom, however, doc says next-page is generic specific, and is not even mentioned in 'index' space. -- 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/local/lib/gcc-lib/sparc-sun-solaris2.8/3.2/specs Configured with: ../configure --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --disable-nls Thread model: posix gcc version 3.2 - CFLAGS -Wall -pedantic -isystem/static/include -isystem/usr/local/include -- Mutt Version Information Mutt 1.4.2.1i (2004-02-12) Copyright (C) 1996-2002 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: SunOS 5.8 (sun4u) [using ncurses 5.3] 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 SENDMAIL=""/usr/lib/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/static/stow/mutt-1.4.2.1/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. --- Begin /export/home/vps/.muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /static/stow/mutt-1.4.2.1/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /static/stow/mutt-1.4.2.1/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /static/stow/mutt-1.4.2.1/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" set abort_unmodified=ask-yes set alias_file=""~/.mutt/aliases"" source ~/.mutt/aliases set allow_ansi=yes set askcc=yes set beep_new=yes set edit_headers=yes set encode_from=yes set fast_reply=yes set header=yes set include=yes set indent_string="">"" set keep_flagged=yes set markers=no set menu_scroll=yes set move=no set rfc2047_parameters=yes set send_charset=""us-ascii:koi8-r:utf-8"" set smart_wrap=no set tilde=yes set use_ipv6=no source ~/.mutt/keys --- End /export/home/vps/.muttrc >How-To-Repeat: >Fix: }}}" """Pawel S. Veselov"" " 1887 delete-pattern fail to delete all messages in thread when collapsed mutt 1.5.6i enhancement mutt-dev new 2004-05-24T21:29:46-07:00 2005-09-04T13:31:00-07:00 "{{{ Package: mutt Version: 1.5.6i Severity: normal -- Please type your report below this line When delete-pattern command is used with pattern "".*"" and one has collapsed threads Mutt deletes only first message of such thread. If one has uncollapsed thread all messages will be deleted. In general, with "".*"" pattern Mutt deletes only messages that are visible in main menu. -- System Information System Version: FreeBSD 5.2.1-RELEASE i386 -- 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 cc -I/usr/local/include Using built-in specs. Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 3.3.3 [FreeBSD] 20031106 - CFLAGS -Wall -O -pipe -mcpu=pentiumpro -- Mutt Version Information Mutt 1.5.6i (2004-02-01) Copyright (C) 1996-2002 Michael R. Elkins É ÄÒÕÇÉÅ. Mutt ÒÁÓÐÒÏÓÔÒÁÎÑÅÔÓÑ âåú ëáëéè-ìéâï çáòáîôéê; ÄÌÑ ÐÏÌÕÞÅÎÉÑ ÂÏÌÅÅ ÐÏÄÒÏÂÎÏÊ ÉÎÆÏÒÍÁÃÉÉ ××ÅÄÉÔÅ `mutt -vv'. Mutt Ñ×ÌÑÅÔÓÑ Ó×ÏÂÏÄÎÙÍ ÐÒÏÇÒÁÍÍÎÙÍ ÏÂÅÓÐÅÞÅÎÉÅÍ. ÷Ù ÍÏÖÅÔÅ ÒÁÓÐÒÏÓÔÒÁÎÑÔØ ÅÇÏ ÐÒÉ ÓÏÂÌÀÄÅÎÉÉ ÏÐÒÅÄÅÌÅÎÎÙÈ ÕÓÌÏ×ÉÊ; ÄÌÑ ÐÏÌÕÞÅÎÉÑ ÂÏÌÅÅ ÐÏÄÒÏÂÎÏÊ ÉÎÆÏÒÍÁÃÉÉ ××ÅÄÉÔÅ `mutt -vv'. System: FreeBSD 5.2.1-RELEASE (i386) [using ncurses 5.2] [using libiconv 1.9] ðÁÒÁÍÅÔÒÙ ËÏÍÐÉÌÑÃÉÉ: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK +USE_POP +USE_IMAP -USE_GSS +USE_SSL -USE_SASL -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +COMPRESSED +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/local/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER þÔÏÂÙ Ó×ÑÚÁÔØÓÑ Ó ÒÁÚÒÁÂÏÔÞÉËÁÍÉ, ÉÓÐÏÌØÚÕÊÔÅ ÁÄÒÅÓ . þÔÏÂÙ ÓÏÏÂÝÉÔØ Ï ÏÛÉÂËÅ, ÉÓÐÏÌØÚÕÊÔÅ ÐÒÏÇÒÁÍÍÕ flea(1). patch-1.5.6.dw.multiple-crypt-hook.2 patch-1.5.6.dw.confirm-crypt-hook.1 patch-1.5.6.dw.crypt-autoselectkey.1 patch-1.5.6.dw.pgp-menu-traditional.2 vvv.quote 1.3.28.nr.threadcomplete vvv.initials rr.compressed >How-To-Repeat: >Fix: }}}" rea@… 1927 need format string for last name mutt 1.5.6i enhancement mutt-dev new 2004-10-24T17:56:26-07:00 2005-08-01T15:33:00-07:00 "{{{ Package: mutt Version: 1.5.6-20040907 Severity: normal -- Please type your report below this line Request: Mutt should provide an additional ""last name"" format string for use in the values of index_format and attribution. Similar to %v but for showing just an author's last name instead of firs name. Rationale: In many parts of the world -- for example, in Japan -- it is customary to address people by their family names instead of their personal names. A ""last name"" format string, would make it possible to easily generate attributions based on author last name. Workaround?: Question: Is there any way to work around this in the current Mutt? (I thought about making a backtick pipe to a simple shall command to split %n and just return that last part, but then I realized I'd just be passing a literal ""%n"" to the shell.) Thanks, --Michael Smith -- 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/i486-linux/3.3.4/specs Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-debug --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i486-linux Thread model: posix gcc version 3.3.4 (Debian 1:3.3.4-13) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.6i (2004-02-01) Copyright (C) 1996-2002 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.26-bytemark-uml-20040706-1 (i686) [using slang 10409] 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 -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR -HAVE_START_COLOR -HAVE_TYPEAHEAD -HAVE_BKGDSET -HAVE_CURS_SET -HAVE_META -HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK -HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.5.6.tt.ja.1 >How-To-Repeat: >Fix: }}}" smith@… 2035 Feature Request: Show Subject at bottom of index mutt enhancement mutt-dev new 2005-08-12T13:21:01-07:00 2007-03-27T16:43:52-07:00 Like '@' shows the From field at the bottom of the index, it would be nice to have something to show the Subject, when there are emails in the index with subjects that are so long that they get cut off to the point of being illegible, so you don't have to open the email just to see the Subject. bofh@… 2054 wish $signature %expandos mutt enhancement mutt-dev new 2005-09-03T22:24:15-07:00 2007-04-01T20:29:42-07:00 "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 in my opnion. Can this be done in the new release? Thanks! -ldshou" Lidan Shou 2061 wish: mail composition crash recovery mutt enhancement mutt-dev new 2005-09-08T07:10:30-07:00 2007-04-07T07:26:19-07:00 "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, but most reasonable ones have. >Fix: when starting to compose a mail, create a state file with the name of the file passed to the editor (and all headers if edit_headers is unset). when sending, postponing or discarding the mail, delete the file. if mutt starts up and the file is still there, resume the mail composition (after a confirmation)." ossi@… 2067 mutt handling of deep threads could be improved mutt enhancement mutt-dev new 2005-09-14T09:31:03-07:00 1969-12-31T16:00:00-08:00 "{{{ When having a threaded view of a long conversation, threads can sometimes get so long that they are pushed off the right-side of the terminal. This can be improved somewhat by setting $narrow_tree, but even here, if the thread is deep enough, it can get pushed off the side of the terminal. Pine has a reasonable solution to this, which is that if a thread's subject (and thread tree markers) gets pushed off the terminal, it puts a marker in that says how deep off the side of the screen it is. That would be a nice feature in mutt. >How-To-Repeat: View the attached maildir (consists of slightly modified messages from the mutt-dev mailing list). >Fix: Unknown }}}" kyle-mutt-dev@… 2092 pattern date format is ambiguous mutt 1.5.10 enhancement mutt-dev new 2005-09-25T20:03:18-07:00 2007-03-31T15:18:15-07:00 "{{{ Pattern matching currently uses a date format of DD/MM/YYYY which is prone to confusion with MM/DD/YYYY in english speaking countries. >How-To-Repeat: >Fix: ISO-8601 recommends YYYY-MM-DD to be used, but this would require current ""date1 - date2"" syntax to be changed. }}}" thomasz@… 2101 Configurable umask mutt Mutt 1.5.10i (2005-08-11) enhancement mutt-dev new 2005-10-05T06:37:48-07:00 2009-06-13T15:16:15-07:00 "As already said in the synopsis: it would be very nice if we could configure the umask value in muttrc ... " swimmer@… 2109 Add %h{Header} mutt enhancement mutt-dev new 2005-10-10T05:31:22-07:00 1969-12-31T16:00:00-08:00 "{{{ The attached patch create a %h{Header} that can be used like that: save-hook '~h ""X-Stuff: ([0-9]+)""' ~/Mail/Thing-%h{X-Stuff} Quite usefull :-) The patch works against 1.5.11 (the one in Debian/Unstable), and used to work against 1.5.10 (same, from Debian). The only difference being 1.5.10-""read_rfc822_line"" have been renamed to 1.5.11-""mutt_read_rfc822_line"". Any comments are of course welcome! >How-To-Repeat: >Fix: Unknown }}}" bayartb@… 2132 Encrypting local copy of message crypto enhancement mutt-dev new 2005-11-09T10:53:06-08:00 2009-06-30T07:36:13-07:00 "{{{ I would like to request a feature that it would be possible to save a local copy of a message encrypted by only sender key. That (not) encrypting the outgoing message would not influence this (and that it would not be only a copy of final outgoing message). Maybe with setting a variable similar to ""fcc_clear"". For example ""fcc_crypt"" and ""fcc_crypt_pgp_command"". >How-To-Repeat: >Fix: }}}" mmitar@… 2134 Mutt does not use different exit-codes depending on whatever mutt 1.4.1i enhancement mutt-dev new 2005-11-10T08:56:59-08:00 1969-12-31T16:00:00-08:00 "{{{ Hi, I'm using mutt inside a script where glimpse selects messages from various mailboxes and assembles them all in a temporary mailbox. However, sometimes glimpse doesn't get it quite right, and mutt will report: /tmp/glimpse.21144/mboxfind.results is not a mailbox. Which, indeed, it isn't. However, my script will never know about this, since mutt returns 0 as its exit code anyway, and happily delete the file instead of doing something useful. So, in short, I would really ask for different exit codes for mutt, at least for the above case, but quite possibly for some other cases too (everytime mutt exits even though I didn't ask it to exit, I guess...) Help very much appreciated Sven >How-To-Repeat: >Fix: Unknown }}}" utcke+mutt@… 2141 wishlist: possible storing of attachments as separate files mutt enhancement mutt-dev assigned 2005-11-22T02:23:25-08:00 2008-05-29T01:46:39-07:00 "{{{ As a mail agent called The Bat!, I'd like mutt to have an option to store [some] attachments not in a mailbox, but in a directory as separate files. So that, mailboxes could shrink considerably, having only text and [several] references to other contents. The programm sould be tuned on what types of attachments to leave in mailbox and what types to extract. If anyone could propose a patch as a 3rd party, this would be fine too. >How-To-Repeat: >Fix: Unknown }}}" ildar@… 2145 Mutt needs directive to widen reverse-name's scope mutt 1.5-series, current enhancement mutt-dev new 2005-12-06T08:30:53-08:00 1969-12-31T16:00:00-08:00 "{{{ reverse-name only looks at a small number, possibly 1 field. It would be much more useful if a 'reverse-fields' directive could be added so that the user could specify an ordered list of fields that should be checked for addresses than match an alternate and could be used for bulding the from that reverse-name enables. Presumably the current list is ""To, Cc"", whereas I would very much like ""Envelope-to:"" as the sole list (I use tokenised email with an MTA that adds the envelope-to header) >How-To-Repeat: >Fix: See description. }}}" pack-muttbugs@… 2160 make hostname part of Message-IDs configurable mutt 1.5.11 enhancement mutt-dev new 2006-01-06T01:16:20-08:00 2007-03-01T11:26:04-08:00 "{{{ mutt is lacking a configuration option for the structure of the Message-IDs. It insists on generating the Message-IDs on its own. Therefore I have Message-IDs like <20060106083603.GA7391@danisch.de> when sending with mutt. Unfortunately, there are plenty of spammers which search through mailing list archives for e-mail-address patterns. They collect these message-ids and put them in their address lists. For some special reason I have to accept any mail to my domain (catchall recipient), therefore I get millions of spam to these message-id-addresses. Mutt should have an option where to configure the domain part of the Message ID to allow giving it some subdomain of the domain which is not reachable by e-mail. >How-To-Repeat: >Fix: Allow a configuration option to configure the domain part of the message ID. Or better: Allow an sprintf-like String to freely configure it. }}}" hadmut@… 2169 Four suggested changes mutt 1.5.10 enhancement mutt-dev new 2006-01-27T18:43:54-08:00 2006-09-25T05:25:02-07:00 "{{{ (Moved from headline: [1]Addresses handling [2]Remove copiousoutput test [3]Make $implicit_autoview a quadoption [4]Add ""mono"" and xterm examples (See attachment for patch for various 1.5.10 problems.) ) Dear friends, attached is a ""patch(1)"" file to repair several problems that I recently found in Mutt Version 1.5.10, which you might like to incorporate in a future release. This note describes the changes. By way of introduction and a general explanation, let me say that after more than 20 years of satisfactorily reading my E-mail (including MIME content) on an HP-UX system, using a slightly modified Berkeley ""mailx(1)"" with a much-repaired port of ""metamail(1)"" Version 2.7, I recently changed jobs and needed to run a MUA on Linux that could speak IMAP to an Outlook Exchange mail server, so I became a new Mutt user. But after thoroughly perusing its documentation and extensively customizing my ""Muttrc"" file, and despite Mutt's aspiration to be ""the premier text-mode MIME MUA"" (Michael Elkins, ""The Mutt E-Mail Client"", sec. 5), I found some of its behavior to be extremely irritating, so I changed the code. Here are my issues and changes: I first found that if I enable the ""edit_headers"" option and edit a message's ""[b]cc:"" or ""to:"" headers to specify a list of local recipients, separated by white space (a common UNIX idiom), like: cc: foo bar baz then either Mutt or my site's Outlook Exchange server--I'm not sure which--badly mangles the line and makes message copies undeliverable. The mangling seemed to be worse if the list line contained leading- or trailing white space, and I found through experiment that a Comma-separated list, such as: cc: foo,bar,baz works fine. But remembering to type Commas is tedious, so I changed the ""parse.c"" file so as to: 1. In ""mutt_parse_adrlist()"", automatically insert Commas if none are present, and handle leading-, trailing-, and intervening white space more rigorously before calling ""rfc822_parse_adrlist()"". 2. In ""mutt_parse_rfc822_line()"", call ""mutt_parse_adrlist()"" instead of ""rfc822_parse_adrlist()"" in order to re-canonicalize any ""[apparently-]to:"" or ""[b]cc:"" header that a user might have edited. My other issues concern ""autoview"" of MIME attachments to received messages. To begin, the ""rfc1524_mailcap_parse()"" subroutine in file ""rfc1524.c"" refuses to allow this unless one's ""mailcap"" entry for a given MIME type/subtype specifies ""copiousoutput"". I think that this behavior represents a misreading of RFC 1524, which also differs from the behavior of ""metamail(1)"". Since Nathaniel Borenstein wrote both ""metamail(1)"" and the RFC, I think that his interpretation of the intended semantics should be considered authoritative; namely, a display command that intends to dump enough output to the user's console (window) to warrant a pager should specify ""copiousoutput"", but a display command that will pop up its own, new window (or use an audio player, etc.) need not--and should not--specify ""copiousoutput"". And in neither case should Mutt forbid such content from being ""autoview""ed! (Grrr!) So, I removed the ""copiousoutput"" test from this subroutine. Next, I basically don't like Mutt's default, menu-based strategy for displaying attachments; I much prefer the ""metamail(1)"" automatic-display strategy, in which it shows everything that one's ""mailcap"" file allows and successively asks a user's permission for each attachment. I therefore implemented this strategy as an option in Mutt: 1. In ""init.h"", change ""implicit_autoview"" from a boolean option to a quadoption, whose default value is ""no"" for backward compatibility. 2. In the ""mutt_is_autoview()"" subroutine of file ""attach.c"", solicit a user's input to a ""Display it?"" query if the ""$MM_NOASK"" environment variable doesn't provide an answer and the ""implicit_autoview"" option is either ""ask-yes"" or ""ask-no"". Incidentally, some peoples' enhanced versions of ""metamail(1)"" allow a third possible response, which I like very much but don't know how to easily implement in Mutt: One can interactively bail out of displaying a list of attachments by responding to a query in the form: Display it? q[uit] (or ""x"", for ""exit"") Finally, let me close with a plea for some FAQ documentation on another subject: I happen to be an older worker with a slight visual impairment, and I loathe applications that use color Curses because I find the colors rather hard to distinguish; I need old-fashioned black-and-white. In one's ""Muttrc"" file it is certainly possible to establish appropriate, non-default color mappings, but the mechanism is complicated and not altogether obvious from the documentation; moreover, I discovered that an ""xterm(1)"" window under RedHat Linux shows some rather strange default colors (I don't understand why, or whether I could change that in my X Windows ""app-defaults"" file): white when I would have expected black, and ""vice versa"". Could you please augment Mutt's documentation with an *example*, showing how to replace color with either a black-on-white or white-on-black palette? All in all, I find that Mutt's not a bad MUA, but I think that a few little changes like these could make it even more appealing. -- Scott Marovich VMware, Inc. E-mail: marovich@vmware.com 3145 Porter Drive Tel. (650)475-5000 x522/FAX (650)475-5005 Palo Alto, California 94304 U.S.A. >How-To-Repeat: >Fix: Suggested patch is in attachment. -- [1] Convert ""cc: foo bar baz"" to ""cc: foo,bar,baz"" [2] Bypass ""copiousoutput"" test and autoview anything anyway. [3] Make $implicit_autoview a quadoption to handle attachments as metamail does. [4] Add ""mono"" examples to the manual. }}}" marovich@… 2179 better scoring support - regexp matching mutt enhancement mutt-dev new 2006-02-09T05:58:36-08:00 2009-06-12T16:33:27-07:00 "{{{ muttng devs improved the matching support in scoring: http://mutt-ng.supersized.org/archives/35-Scoring-in-mutt-ng.html#extended http://svn.berlios.de/wsvn/mutt-ng/trunk/score.c?op=diff&rev=0&sc=0 It would be great if that was added to mutt too. It makes scoring more useful. >How-To-Repeat: >Fix: }}}" name@… 2202 support for environment changes mutt enhancement mutt-dev new 2006-04-03T05:57:58-07:00 1969-12-31T16:00:00-08:00 "{{{ Mutt can be executed in ""screen"" and several things may change when the session is reattached from a different machine (e.g. via ssh): * The DISPLAY and some other similar environment variables (so that the editor window is displayed on the right screen, ditto for the attachments viewed with an external program). * The encoding used by the user-side terminal. So, Mutt should have a way to take these changes into account. Concerning the DISPLAY, this can be done with wrappers, which do not require special support in Mutt (see ). However support in Mutt would be a plus. Concerning the encoding, I don't think this is possible without special support in Mutt. What should be done: * Have a way to tell Mutt not to use characters outside some charset (e.g. ISO-8859-1 with UTF-8 encoding). This is useful to have transliteration (BTW not only with ""screen"", but also when the user doesn't have some fonts). * Have a way to tell Mutt that the user-side terminal has changed (the pseudo-terminal provided by screen is still the same, of course), for instance when SIGUSR1 is received, Mutt could read some rc file $sigusr1_file. >How-To-Repeat: >Fix: Unknown }}}" vincent@… 2219 extend mailing-list recognition to Resent:- headers mutt 1.5.6 (confirmed by CVS user) enhancement mutt-dev new 2006-05-02T07:48:51-07:00 2008-04-08T12:20:01-07:00 "When eMails get ""bounce""d to mailing-lists, mailing-list checks fail when they are limited to regular headers but ignore ""Resent-"" headers. >Fix: extend checks to ""Resent-"" headers " rado 2256 Feature Request: folder_format add count old messages mutt enhancement mutt-dev new 2006-05-31T02:38:49-07:00 2008-10-31T12:30:34-07:00 "{{{ I have maildir running here with mark_old=yes. It would be nice to have in the Mailbox Browser also a Possibility to show how many old-marked mails are in the folders (like the new count). Thanks >How-To-Repeat: >Fix: Unknown }}}" philipp@… 2465 [PATCH] Use Delivered-to header in set_reverse_name() mutt cvs enhancement mutt-dev new 2006-09-03T13:30:45-07:00 2006-09-06T22:35:02-07:00 "{{{ This patch makes use of the Delivered-to: header when building the From: address in set_reverse_name(). This is needed so that alternate addresses can be found in emails sent from mailing lists where the alternate address isn't in the normal To: or Cc: headers. >How-To-Repeat: >Fix: Included }}}" nate-mutt@… 2476 Handling of 'N' flag with Maildir store maildir/mh Mutt 1.4.1i enhancement mutt-dev new 2006-09-08T04:11:49-07:00 2009-06-30T07:36:22-07:00 "Mutt offers r and ! flags that seem to correspond to the Maildir R and F flags. Mutt also allows one to set or unset the N flag. Messages flagged N are moved to the mailfolder/new/ directory. If the message was additionally flagged r or !, the appropriate :2,FR (or whatever) Maildir flags are left appended to the filename when moved (back) into new/. It seems that filenames of messages in new/ are not allowed to contain a : (because the : info is allowed only in cur/ and tmp/). So Mutt seems to be violating the Maildir format by moving N-flagged messages into new/ while preserving other flags. >Fix: It would seem that a more appropriate behavior would be to leave N-flagged messages in cur/ and instead remove the S Maildir flag when the user flags the message N. If one manually removes the S Maildir flag from a message filename, Mutt seems to recognize this and display the message as N. This solution seems to preserve flag information, preserve the meaning of the new/ directory, and not confuse servers and MUAs expecting files in new/ to not have :s." tait+muttpr@… 2477 display of header lines before each multipart/mixed part is disturbing display 1.5.9i (2005-03-13) enhancement mutt-dev new 2006-09-08T05:52:31-07:00 2009-06-30T07:36:35-07:00 "{{{ The Gnus v5.10.8 mailer may send mails consisting of multipart/mixed parts, one in UTF-8, one in EUC-JP, one in UTF-8, one in EUC-JP, etc. Mailers like kmail-1.9.1 displays the mail without interruptions; likewise the mailing list archive (at http://lists.gnu.org/archive/html/bug-gnulib/2006-09/msg00089.html) does not display boundaries between parts. However, mutt displays the boundaries, and it is disturbing because it interrupts the flow of reading. >How-To-Repeat: In an UTF-8 xterm: $ mutt -f multipart-mixed.mail Press Return. Press Page-Down. >Fix: Unknown }}}" bruno@… 2566 assigning function to a key does not 'unbind' all other bindings for this function mutt 1.5.16 enhancement mutt-dev reopened 2006-11-23T10:05:15-08:00 2007-08-19T08:37:44-07:00 "{{{ After spending considerable time creating a list of ""maps"" for menus and various functions I found that some key combinations can not be bound or 'unbound' successfully. For example. In the attached 'keybindings' file I have attempted to remap print-message to '%' but the key 'p' still persists as being bound to print-message. This is also true for create-alias. I attempted to map create-alias to '@', but it also persists in being bound to key 'a'. In this map the key 'c' should be mapped to mail, but the key 'm' also persists in being bound to the mail function. Some functions should be renamed. ie capitalize-word should be called initalcap-word, or should be dropped from the configuration for simplicity and replaced with toggel-letter-case (like tilde does in vi[m]). I suggest a simplistic approach to key mapping in which mutt uses no built-in maps but uses a default file which can be edited as needed and use other keyboard maps based only on hooks >How-To-Repeat: define a new keybinding for a function, the old _default_ key will still point to the same function. >Fix: Redefine all keys to your use, undefine all others to ""noop"" manually. }}}" oxenreid@… 2599 abort change folder dialog reparses mailcap processing mutt 1.5.13 enhancement mutt-dev new 2006-12-07T05:43:36-08:00 2008-04-08T12:18:27-07:00 "A recent patch allows to stay in pager mode when aborting a change folder dialog, which is a good thing. :) But, instead if the message has to be parsed by mailcap, then such an abort causes a reparse of the message. Depending on the nature of the attachment this can be quite time consuming.Rather the already parsed data should be reused to simply continue the browsing where one initiated the mistaken change folder request. >How-To-Repeat: use heavy duty mailcap'ed attachment processing in pager mode, change folder but abort it. >Fix: Unknown, maybe the pager data should not be discarded before the change folder request is completed." rado 2711 Will not tag/delete duplicates (~=) when emails are not sorted by thread. mutt 1.5.18 enhancement mutt-dev reopened 2007-01-26T11:44:29-08:00 2009-05-30T16:20:22-07:00 "If I try to, for example, tag all duplicate emails and I am not viewing my emails in thread mode, ""T~="" will not tag all of the duplicate emails. However, if I sort my emails by thread and then run that command again, all duplicate emails are tagged." schmmd@… 2743 new status_format items to show quota (used/max) in IMAP server IMAP enhancement mutt-dev new 2007-02-06T11:53:26-08:00 2008-04-08T12:17:31-07:00 "Some IMAP servers advertize QUOTA ability, mutt could display that value in status_format with %q used of %Q limit. " rado 2754 [wish] add capability to jump back to last read with 1 keystroke mutt mutt 1.5.13 (2007-02-07) enhancement mutt-dev new 2007-02-12T00:55:33-08:00 1969-12-31T16:00:00-08:00 "{{{ Add feature to jump back to any last read message with one keystroke. Some newsreaders have this (eg. Slrn, bound to ""l"" by default). This would be an improvement to a mail _reader_. ATM also can't be worked around with macros. >How-To-Repeat: >Fix: Unknown }}}" blacktrash@… 2829 Bug#160678: $wrap variable (chop long lines instead of wrapping) display enhancement mutt-dev new 2007-03-07T04:25:01-08:00 2009-06-30T07:36:45-07:00 "{{{ The following is Debian wishlist bug #160678: ----- Forwarded message from Marcin Owsiany ----- Date: Thu, 12 Sep 2002 20:27:36 +0200 From: Marcin Owsiany Reply-To: Marcin Owsiany , 160678@bugs.debian.org To: Debian Bug Tracking System Subject: Bug#160678: Please add $wrap variable Package: mutt Version: 1.4.0-3 Severity: wishlist It would be nice if mutt's internal pager didn't wrap the text if asked for by a variable. (The effect I'm talking about would be similar to the one caused by ""-S"" flag to ""less""). Of course then it would be even nicer to have sideways scrolling of the message, but just disabling wrapping would be useful anyway. Marcin ----- End forwarded message ----- Christoph -- cb@df7cb.de | http://www.df7cb.de/ >Fix: Unknown }}}" Christoph Berg 1200 mbox From_ line format over-strict expectations mutt 1.5.17 defect me accepted 2002-05-20T05:47:46-07:00 2013-01-14T20:45:42-08:00 "{{{ Package: mutt Version: 1.3.27i Severity: normal -- Please type your report below this line Mutt does not read all messages in the to following mailboxes. It only found 21 messages over hundreds in the first one and he doesn't found any message in the other one. ftp://ftp.cac.washington.edu/imap/c-client_archive_gz/ Bug reported on the newgroup: fr.comp.mail -- 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 cc -I/usr/local/include Using builtin specs. gcc version 2.95.3 20010315 (release) [FreeBSD] - CFLAGS -Wall -pedantic -O -pipe -- Mutt Version Information Mutt 1.3.27i (2002-01-22) Copyright (C) 1996-2001 Michael R. Elkins et autres. Mutt ne fournit ABSOLUMENT AUCUNE GARANTIE ; pour les détails tapez `mutt -vv'. Mutt est un logiciel libre, et vous êtes libre de le redistribuer sous certaines conditions ; tapez `mutt -vv' pour les détails. System: FreeBSD 4.4-RELEASE-p9 (i386) [using slang 10404] Options de compilation : -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/local/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER Pour contacter les développeurs, veuillez écrire à . Pour signaler un bug, veuillez utiliser l'utilitaire flea(1). --- Begin /usr/local/etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /usr/local/share/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /usr/local/share/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /usr/local/share/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" --- End /usr/local/etc/Muttrc Received: (at submit) by bugs.guug.de; 5 Dec 2002 15:18:16 +0000 From alefav@bsdshell.dyndns.org Thu Dec 05 16:18:16 2002 Received: from [208.247.65.237] (helo=bsdshell.dyndns.org ident=root) by trithemius.gnupg.org with esmtp (Exim 3.35 #1 (Debian)) id 18JxlW-0003Bx-00 for ; Thu, 05 Dec 2002 16:18:15 +0100 Received: from bsdshell.dyndns.org (alefav@localhost [127.0.0.1]) by bsdshell.dyndns.org (8.12.5/8.12.5) with ESMTP id gB5FIfKe090507 for ; Thu, 5 Dec 2002 10:18:41 -0500 (EST) (envelope-from alefav@bsdshell.dyndns.org) Received: (from alefav@localhost) by bsdshell.dyndns.org (8.12.5/8.12.5/Submit) id gB5FIS7D090506 for submit@bugs.guug.de; Thu, 5 Dec 2002 15:18:28 GMT Message-Id: <200212051518.gB5FIS7D090506@bsdshell.dyndns.org> Date: 5 Dec 2002 15:13:59 -0000 From: nv017001@sneakemail.com Subject: mutt-1.5.1i: strange behavior when email address contains 0xA0 's To: submit@bugs.guug.de Personality: fake Package: mutt Version: 1.5.1i Severity: normal -- Please type your report below this line I recently had problems with mutt reading a news article (saved to a file). It turned out that the poster uses an email address \xA0@\xA0.\xA0 and mutt seems to ignore the mailbox delimiter line From \xA0@\xA0.\xA0 ... Is this a bug? I have appended a zipped and uuencoded copy of a mailbox that can be used to reproduce the error. -- Mutt Version Information Mutt 1.5.1i (2002-05-02) System: Linux 2.4.18 (i686) [using slang 10401] -- Sample mailbox begin 644 mbox.gz M'XL(""+=L[ST``VUB;W@`C9-=;]LV%(;O]2M8;!<;&K&2+,N6UJW^3OPEV['J M.""F*@I8HBS%%RB1EV?DU^:FCW/4B`SH,$""""`?,^+E\\Y9R1X#EX[`+Z""*""O! M`,<`-('M!FXK<#S@6)9CA&&T-)=<*L+VY@`I'-3:&V`UK_I:`RPG:/A!LPE, MR[,L(\25W`M>%C(`.8D%ESQ5L""AWE,2P(BSAE3P7,,.T^(98\DV61<&%NHEY M7D`N(26L/-\@JGZ(_?;;.Y@3&=_\A_4.21)+8UWNGG&L`G""O4S]D),[`$@E% M%.$,?``]SA68(X;V6``BP0Y+]>F3,=)4`HWE%;X:""[%'C+R@ND*?&2-.*:_* MPHQX`.J$*44Y-G[&Q0H:7F`[FDM;<]F:-1F!48*%SD/8)@06]'UH.PGXDB?R M*_CMW/9`P]D1]7LMYV97Q!DY:?,+EL8]3K'`+,8:[,=&TU=EZ::8Y?'^X/O' M?)_LTI9']C+/D6^U1<=%9ZC!_04^8M3*5^XO>?^N""QW7ZPVMBWG7\;&?#P?FALLY)6?#2VCSYG""3)G1I:B1X;/ZL*2(L#]`G""$AL?KS M\]KLKOOCL3''4NK>F..!?B[URIBM^I-):])[WD[WV^@A;JPZLL#H@)&\7/,8 M,\)J.([W=F[O]#\`G@MMZ$#;KUL1""13K`/+4,)>5""!%W&+X\Q&&?2D27(QP/ M#[VNE;TSI6&5%D;OT<;Z1+Z?N>OINC""[G5O7<*]O'I^.Y1W7TOMZ%&IF2W\=P M5TK\%H06#>;][O]3=NM34R_B]YHQ2[5T2;4""ZY4`LA08*`Y2+BHD$H!`S(L+ MX""GHSF8@NTZS_)G-0F585$0[5?HCE-:.)4,[>O748Z6'68(++P6(?X2MCPLL EZ$6[UAU,""57UQMC0-HPO0*HR34&""*58X`5^-OP%Y.0[,Q@0````` ` end Received: (at submit) by bugs.guug.de; 16 Dec 2002 02:52:29 +0000 From yusufg@outblaze.com Mon Dec 16 03:52:29 2002 Received: from 202-77-223-51.outblaze.com ([202.77.223.51] helo=corpmail.outblaze.com) by trithemius.gnupg.org with esmtp (Exim 3.35 #1 (Debian)) id 18NlMq-0004uo-00 for ; Mon, 16 Dec 2002 03:52:29 +0100 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by corpmail.outblaze.com (Postfix) with ESMTP id F10E77D4B for ; Mon, 16 Dec 2002 02:58:44 +0000 (GMT) Received: from yusufg.portal2.com (202-77-223-125.outblaze.com [202.77.223.125]) by corpmail.outblaze.com (Postfix) with SMTP id AB918520D2 for ; Mon, 16 Dec 2002 02:58:44 +0000 (GMT) Received: (qmail 18858 invoked by uid 500); 16 Dec 2002 02:52:50 -0000 Date: 16 Dec 2002 02:52:50 -0000 Message-ID: <20021216025250.18857.qmail@yusufg.portal2.com> From: ""Yusuf Goolamabbas"" Subject: mutt-1.4i: Unable to read any of the psyche-list archives mailboxes To: submit@bugs.guug.de X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.6; VAE: 6.17.0.2; VDF: 6.17.0.6; host: corpmail.outblaze.com) Package: mutt Version: 1.4i Severity: normal -- Please type your report below this line Hi, When I download and gunzip the archives of the psyche-list https://listman.redhat.com/pipermail/psyche-list/ mutt 1.4i on Redhat 7.0/7.3/8.0 does not show any messages, the 'mail' command on redhat 7.0/7.3/8.0 is able to read the mailboxes. Anybody else seeing similar behaviour and can explain why this is so Regards, Yusuf yusufg@outblaze.com -- Mutt Version Information Mutt 1.4i (2002-05-29) 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.20 (i686) [using slang 10401] Compile options: DOMAIN=""outblaze.com"" -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=""/usr/sbin/sendmail"" MAILPATH=""Mailbox"" PKGDATADIR=""/usr/local/site/mutt/share/mutt"" SYSCONFDIR=""/usr/local/site/mutt/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. Received: (at submit) by bugs.guug.de; 4 Jan 2004 11:00:39 +0000 From jhawk@MIT.EDU Sun Jan 04 12:00:36 2004 Received: from biscayne-one-station.mit.edu ([18.7.7.80]) by trithemius.gnupg.org with esmtp (Exim 3.35 #1 (Debian)) id 1Ad5zn-0006b7-00 for ; Sun, 04 Jan 2004 12:00:35 +0100 Received: from manawatu-mail-centre.mit.edu (MANAWATU-MAIL-CENTRE.MIT.EDU [18.7.7.71]) by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id i04B3FFp016252; Sun, 4 Jan 2004 06:03:15 -0500 (EST) Received: from coleco-sidewinder.mit.edu (COLECO-SIDEWINDER.MIT.EDU [18.187.2.149]) (authenticated bits=56) (User authenticated as jhawk@ATHENA.MIT.EDU) by manawatu-mail-centre.mit.edu (8.12.4/8.12.4) with ESMTP id i04B3D8e008964; Sun, 4 Jan 2004 06:03:14 -0500 (EST) Received: (from jhawk@localhost) by coleco-sidewinder.mit.edu (8.12.9) id i04B3DlP008485; Sun, 4 Jan 2004 06:03:13 -0500 (EST) Date: Sun, 4 Jan 2004 06:03:13 -0500 (EST) From: jhawk@MIT.EDU Message-Id: <200401041103.i04B3DlP008485@coleco-sidewinder.mit.edu> Subject: mutt-1.4.1i: Mutt doesn't like some ^From mailbox seperators (esp. with ""at"") To: submit@bugs.guug.de X-Spam-Status: No, hits=-3.6 required=4.0 tests=BAYES_10,NO_REAL_NAME version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Package: mutt Version: 1.4.1i Severity: normal -- Please type your report below this line (This is also seen with 1.5.4). Mutt fails to properly read mbox-format files with From lines like: From dtucker at zip.com.au Thu Jan 1 11:19:33 2004 This sort of mbox-file can be found, e.g., at http://www.mindrot.org/pipermail/openssh-unix-dev/2004-January.txt With debugging, mutt spews: is_from(): parsing: dtucker at zip.com.au Thu Jan 1 11:19:33 2004 is_from(): got return path: dtucker is_from(): expected weekday, got: at zip.com.au Thu Jan 1 11:19:33 2004 mutt then shows a mailbox with none or one or two messages, instead of the correct number. I'm not sure what the best way to make the parser more flexible is. In http://www.imc.org/ietf-smtp/old-archive/msg02087.html, jgm notes: | Mark Crispin's c-client has code to parse at least 20 different | variants of this format--10 different possible date formats, each with | or without a "" remote from XXX"" after it. So maybe that code should be hunted down and copied/emulated? is_from()'s parser looks relatively fragile. I'm loathe to try to craft a patch that's specific to this one type, and I don't know what a good authoritative reference is. If you'd find it useful for me to do so, please let me know and I shall. --jhawk -- 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/gcc/lib/gcc-lib/sparc-sun-solaris2.9/3.2.1/specs Configured with: ../src/configure --prefix=/usr/gcc --disable-shared Thread model: posix gcc version 3.2.1 - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.4.1i (2003-03-19) Copyright (C) 1996-2002 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: SunOS 5.9 (sun4u) [using slang 10310] 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/athena/bin/ispell"" SENDMAIL=""/usr/lib/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/mit/sipb/share/mutt"" SYSCONFDIR=""/mit/sipb/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" Nicolas Le Scouarnec 1751 "fetch_mail splits body at ""From """ POP 1.4.1i defect infoneeded_new 2004-01-09T00:23:30-08:00 2011-04-13T04:22:44-07:00 "{{{ Package: mutt Version: 1.4.1i Severity: important -- Please type your report below this line Fetching mail from a POP3 server unsing mutt's fetch_mail splits one message into several. It splits at lines in the body starting with ""From "". In contrast, software package fetchmail changes ""From "" to "">From "" when storing into /var/spool/mail/username so that mutt can read correctly. -- 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/i586-suse-linux/3.3.1/specs Konfiguriert mit: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --enable-languages=c,c++,f77,objc,java,ada --disable-checking --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit i586-suse-linux Thread model: posix gcc-Version 3.3.1 (SuSE Linux) - CFLAGS -Wall -pedantic -Wall -O2 -march=i586 -mcpu=i686 -fmessage-length=0 -I. -D_GNU_SOURCE -- Mutt Version Information Mutt 1.4.1i (2003-03-19) Copyright (C) 1996-2002 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.21-99-athlon (i686) [using ncurses 5.3] Einstellungen bei der Compilierung: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP -USE_GSS +USE_SSL +USE_SASL +USE_SASL2 +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 +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO -ISPELL SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER Um die Entwickler zu kontaktieren, schicken Sie bitte eine Nachricht (in englisch) an . Um einen Bug zu melden, verwenden Sie bitte das Programm flea(1). SuSE 9.0, mutt-1.4.1i-109, which includes the patches Signature_conversion mutt-1.4.1i-authsasl.diff mutt-1.4.1i-configure.diff mutt-1.4.1i-longlines.patch mutt-1.4.1i-muttbug.sh-head.diff mutt-1.4.1i-patch-iconv.diff mutt-1.4.1i-pgpewrap.diff mutt-1.4.1i-sasl2.patch mutt-1.4.1i-sendgroupreplyto.diff mutt-1.4.1i-stdlib.diff mutt-1.4.1i-type_punning.diff mutt-1.4.1i.diff patch-1.4.1.rr.compressed.1.bz2 -- Using my data or passing them on for advertising, market research or opinion research purposes is forbidden. }}}" Julian Ladisch 2304 reply / group reply behavior broken WRT $reply_to and $reply_self mutt 1.5.11 (and all others, including current CVS) defect mutt-dev new 2006-06-23T09:17:10-07:00 2010-08-06T14:31:37-07:00 "{{{ There seems to be a problem with how mutt handles $reply_to and $reply_self. In particular, it seems to behave badly replying to some combinations of e-mails which are sent by oneself, and contain a Reply-to header. This is a bit complicated, as the interactions of these two variables forms a 3-dimensional decision matrix. I apologize for the complexity of this bug report, but there's no way around it; it's a complex issue. The essential problem is that when $reply_to is set (and there is a Reply-to header), but $reply_self is unset, Mutt does the wrong thing. It ignores the Reply-to header completely, whether the user is REPLYing or GROUPREPLYing. This apparently is true of all versions of Mutt including and prior to the current CVS. >How-To-Repeat: >Fix: Unknown }}}" code@… 2575 """bind index z noop"" makes mutt ignore ""bind generic z current-middle""" mutt 1.5.16 defect mutt-dev new 2006-11-30T09:28:29-08:00 2011-01-03T07:18:51-08:00 "I want to bind some keys to generic functions, but default bindings for menus ovverride generic bindings defined by me. When I ""bind index z noop"" then the default binding is gone, the generic binding is listed in '?', but the key us not recognized. >How-To-Repeat: {{{ bind index noop bind generic z current-middle }}} press z in index == unknown key" rado 2881 pager: syntax highlight bug with multiple quotes display 1.5.15 defect mutt-dev new 2007-04-23T08:43:04-07:00 2007-04-23T08:43:04-07:00 "Mutt-1.5.15 without any patches, linked against ncursesw. Default global config, plus these three lines in my own .muttrc: {{{ color quoted green black color quoted1 yellow black bind pager next-line }}} Create a message where (after some unquoted lines) a more deeply quoted text appears, and later appear texts with lower nested level. Example: {{{ foo foo foo > > > q3 > > q2 > q1 bar }}} Switch from the previous mail to this one in a window that has a small height so that only some unqoted ""foo""s appear. Start scrolling to the bottom line-by-line by pressing Space, or enlarging the window. When ""> > > q3"" appears, it is fully green. When ""> > q2"" appears, it gets fully green, and the triple-quoted line is repainted so that ""> > "" remains in green but ""> q3"" turns to yellow. When ""> q1"" is scrolled in, both previous lines change their color again, ""q3"" goes back to green and ""q2"" gets yellow. Even when only a small part of a message is shown, mutt should scan the whole message to see possible quotation symbols so that it can already highlight the syntax correctly. It's quite irritating when it starts to repaint already displayed texts with different color. " egmont 2883 mutt gets confused when a message disappears from a maildir maildir/mh defect mutt-dev infoneeded_new 2007-04-24T04:01:35-07:00 2009-06-30T07:26:00-07:00 "{{{ ----- Forwarded message from Mike O'Connor ----- Date: Wed, 18 Apr 2007 18:30:12 -0400 From: Mike O'Connor Reply-To: Mike O'Connor , 419946@bugs.debian.org To: Debian Bug Tracking System Subject: Bug#419946: mutt gets confused when a message dissapears from a maildir Package: mutt Version: 1.5.13-3 Severity: normal I use offlineimap to keep multiple computers in sync with a remote imap server. If offline imap deletes a file from a new directory in a Maildir that mutt is currently viewing, mutt gets an error trying to move the file from new to cur when running . The only recourse is to quit mutt and restart. Here are the steps I can use to reproduce this: Machine A and Machine B run the same offlineimap config and the same mutt config. I start offlineimap on both, which re-syncs with the server every 5 minutes. I start mutt on both, and switch both machines to be viewing some maildir which is synced by offlineimap which has new messages (which equates to messages in that maildir's new directory). On machine A i delete one of the messages which was new, then change to a different folder (causing the message to actually be deleted). The next time machine A's offlineimap syncs to the server, it deletes the message on the server. The next time machine B's offlineimap syncs to the server, it deletes the message that machine A delted from the new directory of the folder that machine B's mutt is viewing. Then if i try to change folders or run :sync-mailbox on machine B, i get an error in the status area: rename: No such file or directory (errno = 2) stracing the running process reveals that it is, in fact trying to rename a no-longer-existant file from the new directory to the cur directory. At this point, I can never change folders on Machine B without quitting mutt and restarting it. Thanks, stew }}}" myon 2889 version date is incorrect when ChangeLog is not up-to-date build defect mutt-dev new 2007-05-16T04:55:28-07:00 2009-05-14T17:52:09-07:00 "When the changelog file is not up-to-date, the version date (as output by ""mutt -v"") is incorrect. In practice, this is the case when one has a Mercurial working copy. So, a solution is to try ""hg tip --template '{date|shortdate}'""." vinc17 2904 recursive pgp_check_traditional() will crash on complicated multipart messages crypto defect mutt-dev new 2007-06-02T06:11:57-07:00 2009-06-30T07:25:47-07:00 "pgp_check_traditional() is implemented recursively, so deeply nested multipart messages will cause a stack overflow, which can be annoying on systems with limited stack space. Reproduce: $ bash mime.sh > crash $ mutt -F /dev/null -f crash -e 'set pgp_auto_decode' Segmentation fault " taviso 2909 Display problems for spams with strange chars display 1.5.15 defect mutt-dev new 2007-06-13T03:43:31-07:00 2007-06-15T04:57:47-07:00 "For many spams, I have display problems for summary line (in index window). Columns after subject are shifted and unreadable. See attached screenshot and mailbox sample: mail from freshmeat is ok, and second is a spam with display problems. My index_format: set index_format = ""%5C %Z %-70.70s %-27.27L %{%d/%m/%y %H:%M} (%5c)"" Version tested is 1.5.16" FlashCode 2952 should use terminal settings mutt defect mutt-dev new 2007-09-07T10:24:40-07:00 2007-09-13T10:49:46-07:00 "When is used in a macro or key binding, the expected result is that pressing the backspace key will trigger that macro or key binding. However, since is considered an alias for {{{^H}}} and not all terminals emit {{{^H}}} when the backspace key is pressed, this can lead to unexpected behavior. Mutt *should* attempt to detect what the BackSpace key is by fetching the ""erase"" key from current environment (the same way stty does)." memoryhole 2953 "A source ""command|"" in /etc/Muttrc prevents screen's altscreen from working" mutt defect mutt-dev new 2007-09-07T12:36:24-07:00 2007-12-04T10:40:09-08:00 "Okay, I don't know who is at fault here, and if there's a fix possible within mutt, but having a source ""command|"" statement in /etc/Muttrc makes screen's altscreen feature not work. Note that having such source command in ~/.muttrc does not exhibit the problem. To reproduce: {{{ % echo altscreen on >screenrc % echo 'source ""/bin/echo|""' >>/etc/Muttrc % screen -c screenrc % clear % mutt q }}} When quitting mutt, the prompt will be at the bottom of the window, instead of the top." adeodato 3030 hook patterns don't match against full header addresses mutt 1.5.17 defect mutt-dev new 2008-02-13T19:32:32-08:00 2008-02-13T19:32:32-08:00 "Patterns in hooks do not match against the full header addresses. They ignore the ""personal"" part of the address. For example, if the header contains ""To: Joe User "", hook patterns only match against ""juser@example.com"". A save-hook of ""~C joe"" doesn't match against this message. This differs from the behavior of patterns when used when performing limiting, searching, and coloring. (For example, ""color index black white '~C joe'"" does match against the above message.) This can be easily fixed by changing the two calls to mutt_pattern_exec() in hook.c to use the M_MATCH_FULL_ADDRESS flag. (However, this would change the behavior and possibly break configuration files if there are any users who actually expect the current behavior. If necessary, a new configuration variable could be added to turn on the M_MATCH_FULL_ADDRESS flag in hooks.)" simpkins 3036 reply to tagged does not untag mutt defect mutt-dev new 2008-02-25T13:10:10-08:00 2008-02-25T13:50:06-08:00 "mark multiple messages in the index, hit ""reply"". so far, everything is fine. however, after returning to the index, the messages are still tagged. this highly unexpected, if not even dangerous (deleting messages afterwards isn't exactly exceptional). " ossi 3040 charset difference between index browser and pager charset 1.5.21 defect mutt-dev new 2008-03-18T13:42:11-07:00 2011-10-20T21:38:12-07:00 "I'm using the following setting in muttrc: set assumed_charset=UTF-8 set charset=UTF-8//TRANSLIT My index_format is: index_format=""%4C %Z %(%b %d (%H:%M)) %-18.18n [%10.10B] (%3.3c) %?H? [%H] ? %.60s"" Suppose my name (Miek Gieben) would contain some high unicode codepoint character at the second position. In the index browser it would be displayed as M?ek Gieben While in the pager (when viewing the mail) the correct presentation is used and the correct character is displayed. 2 Questions: 1) What could explain for this difference and displaying 2) How can this be fixed? :)" miekg 3053 tag-save does not allow to change name of first saved file mutt defect mutt-dev new 2008-05-08T01:24:46-07:00 2008-05-08T01:24:46-07:00 "tag-save followed by a folder allows to save several attachments to the same folder. All but the first file names can be changed/adjusted before saving. It's a defect that the first name cannot be changed. version 1.5.11 " ulrich_scholz 3063 Messages read marked as unread IMAP 1.5.17 defect mutt-dev infoneeded_new 2008-05-29T00:31:56-07:00 2009-06-28T19:31:22-07:00 "Sometimes messages that I read are marked as unread.. I read a message, then I sync-mailbox ($), then I open ! mailbox and message is unread again.. This happens only ocasionally.. I am using mutt with IMAPs on Ubuntu Hardy." mehturt 3081 [PATCH] Fix use of drafts folder for git imap-send mutt 1.5.21 defect mutt-dev new 2008-06-19T12:22:29-07:00 2012-06-16T02:13:29-07:00 "I mail out a git patch series by sending it to a mailbox, moving the messages into my postponed folder, and then recovering them to edit and send. git-format-patch generates a thread by setting Message-ID on the first message and References & In-Reply-To on the subsequent message. Unfortunately, mutt strips Message-ID when retrieving postponed messages, so the thread ends up broken. Please change mutt_prepare_template() so that the set of stripped headers can be customised. " benh 3093 query_command forgets full name mutt 1.5.18 defect mutt-dev infoneeded_new 2008-07-17T09:02:17-07:00 2009-01-04T12:44:11-08:00 "I'm using mutt's external query command. I recently switched from version 1.5.13 (where everything related to the external query command worked fine) to version 1.5.18. With this version, mailing to an address obtained through the external query command does not longer include the full name of that person. For example, suppose the external query command prints (the 8 spaces in the 2nd line are in fact a tab) {{{ 114 entries in /home/wehr/PIM/data/addressbook ... 1 matching: john@example.com John Doe }}} Then, in version 1.5.13, the mail address used is ""John Doe "". But with 1.5.18, the address is simply ""john@example.com"". This bug should be fixed." StefanWehr 3168 $sendmail option unconditionally and wrongly uses -- mutt 1.5.19 defect mutt-dev new 2009-01-26T13:40:39-08:00 2009-04-06T09:02:07-07:00 "Forwarded from http://bugs.debian.org --- The $sendmail option is described as follows: # Name: sendmail # Type: path # Default: ""/usr/sbin/sendmail -oem -oi"" # Specifies the program and arguments used to deliver mail sent by Mutt. # Mutt expects that the specified program interprets additional # arguments as recipient addresses. I need to add an ""always-bcc"" address, so I tried set sendmail=""/usr/sbin/sendmail -oem -oi madduck+spool@madduck.net"" and also set sendmail=""/usr/sbin/sendmail -oem -oi -- madduck+spool@madduck.net"" It turns out, however, that mutt appends not only additional arguments (recipients), but also unconditionally a '--'. In the above cases, this yields: /usr/sbin/sendmail -oem -oi madduck+spool@madduck.net -- foo@bar.com /usr/sbin/sendmail -oem -oi -- madduck+spool@madduck.net -- foo@bar.com Both are wrong. mutt should probably not append -- if it's already contained in $sendmail. PS: is there a better way to make mutt always BCC another address, other than actually using my_hdr, which is simply too brittle? " antonio@… 3169 mutt -H ignores Content-Type: mutt 1.5.18 defect mutt-dev new 2009-01-26T13:55:11-08:00 2009-01-26T13:55:11-08:00 "Forwarding from http://bugs.debian.org/434235 --- Hi, I prepared with a script a few mail templates containing attachments. I tried to send these using option -H of mutt. Nevertheless I noticed that mutt ignores Content-Type: multipart/mixed; boundary=""1yeeQ81UyVL57Vl7"" and displays all attachments as part of the mail body. Even using E to edit the message inclusing headers fails because it doesn't contain a Content-Type: I could change. I use the following workaround: I send the mail with all attachments as part of the body to me@localhost. Once I recieved the mail I'm able to edit the header including the wrong Content-Type:. I also have to recode the file from latin1 back to UTF-8 (by :set file-encoding=utf-8|:wq) since the encoding was destroyed during the first send (encoding base64 was used initially). Now I can bounce it to the wanted address. This works really well ... I attached a sample email template. " antonio@… 3174 screen garbled after failed S/MIME passphrase display 1.5.18 defect mutt-dev new 2009-01-27T01:33:55-08:00 2009-06-30T07:30:09-07:00 "Hi, I received a signed message with Content-Type multipart/signed; boundary=Apple-Mail-1--816831872; micalg=sha1;protocol=""application/pkcs7-signature"" Replying to this mail sets the S/MIME field to ""Sign"" and ""sign as"" to """". When trying to send the reply, mutt asks for an S/MIME passphrase in the bottom line: ""Enter S/MIME passphrase:"" Pressing Return leads to error messages, since I haven't set up s/mime. However, these error messages mess up the screen such that it becomes difficult to recover. Expected behaviour: more graceful recovery, redisplaying the main menu. Best regards, Gernot The error message that disrupts the screen: Warning: Intermediate certificate not found.sh: -c: line 0: syntax error near unexpected token `(' sh: -c: line 0: `openssl smime -sign -signer /home/staff/salzer/.smime/certificates/(null) -inkey /home/staff/salzer/.smime/keys/(null) -passin stdin -in /tmp/mutt-polaris-1000-27007-2 -certfile /home/staff/salzer/.smime/certificates/(null) -outform DER' Press any key to continue... Pressing ""Return"" shifts the screen by one line, and the bottom line says: ""No output from OpenSSL..."" Pressing another key apparently returns the user to the main menu, but which is not displayed properly." salzer 3186 SIGSTOP/SIGCONT sequence during pipe-message aborts macro mutt 1.5.19 defect mutt-dev new 2009-02-07T08:04:22-08:00 2009-02-07T08:04:22-08:00 "Forwarding from http://bugs.debian.org/514430 --- With this is .muttrc macro index,pager """" ""sleep 5=FOO"" if one presses F5 on a message, then presses CTRL-Z to interrupt mutt (and sleep), then issues the ""fg"" command to the shell to resume mutt, the rest of the macro (the ) is not executed. But if one replaces pipe-message by shell-escape or one does not interrupt the sleep, then it is executed OK. " antonio@… 3187 misleading error when macro uses invalid command mutt 1.5.19 defect mutt-dev new 2009-02-08T06:12:17-08:00 2009-02-20T10:38:57-08:00 "Forwarding from http://bugs.debian.org/497273 --- I have a macro macro index \Co ' and previously, I had index,pager instead of just index in the above. The result was that when I entered \Co in the pager, I was told that ""Key is not bound. Press '?' for help."". The macro works fine in the index. It took me a while to figure out that this was due to being an invalid command in the pager. mutt should either just ignore it in the pager, or provide a better error message. " antonio@… 3197 annoying error when is used in an empty mailbox mutt 1.5.18 defect new 2009-03-01T14:06:40-08:00 2011-04-13T04:23:23-07:00 "When the (or ) function is used in an empty mailbox (or a mailbox where all messages are hidden by limiting), mutt beeps and prints the error message ""No entries"". This is VERY annoying for users who prefer to begin viewing the last entry of each newly-opened mailbox. For example, if a user has the following folder hook folder-hook . 'push ' and their inbox happens to be empty, then mutt will beep at them every time the inbox is opened, every time the mailbox is synced to remove hidden messages that are marked for deletion, and so on..." mszudzik 3224 "in ""screen"", mutt doesn't always have the correct size" display 1.5.19 defect mutt-dev new 2009-04-27T15:24:30-07:00 2009-04-27T15:24:30-07:00 "When I run Mutt in ""screen"" and resize the terminal, Mutt doesn't always have the correct size. In case this is the same problem as with ""less"": http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525830#15 Note: a Ctrl-L seems to always solve the problem." vinc17 3230 decode-copy/save clobbers all headers when $weed=yes mutt 1.5.19 defect mutt-dev new 2009-05-18T15:55:36-07:00 2010-06-14T01:40:59-07:00 "Forwarding from http://bugs.debian.org/521405 --- {{{ The command decode-save/decode-copy honour $weed. If $weed is set to yes, then the decoded copies of the message will have lost all but the most basic set of headers. This is very unexpected, as the copy/save commands do not clobber the message. I tried to work around this, but it seems it's not possible to run commands in a macro after : set my_weed=""$weed""set noweedset weed=""$my_weed"" This macro makes mutt prompt me: Create /home/madduck/mail/storeenter-command>setweed=""$my_weed""? ([yes]/no): which clearly means that the macro is processed without waiting for user input. Please do not clobber a message's headers with decode-copy/decode-save. }}}" antonio@… 3232 deleting attachement changes sort order of message when using 'date-received' display 1.5.20 defect mutt-dev new 2009-05-19T15:31:22-07:00 2009-09-07T22:09:57-07:00 "Forwarding from: http://bugs.debian.org/529250 {{{ 1. sort mailbox with sort=date-received 2. delete attachement from an old message 3. sync mailbox ($) 4. watch that message jump to the front of the mailbox (5. profit?) }}}" antonio@… 3241 doesn't work in pager for an attached message mutt 1.5.19 defect mutt-dev new 2009-06-02T04:34:04-07:00 2009-06-02T04:34:04-07:00 "When I view an attached message, I can't edit it with (though this function is always available in the pager, even for attached messages). has just the effect to return to the attachment menu. should either work or output an error message, and Mutt's manual should be updated accordingly. The latter case (error message) would be less satisfying, but the enhancement would be covered by #1635." vinc17 3323 Sending postponed messages doesn't save a copy in $record mutt 1.5.20 defect mutt-dev new 2009-09-02T14:24:29-07:00 2012-08-14T15:20:48-07:00 "Fowarding from http://bugs.debian.org/540540 {{{ It appears that when sending postponed messages, mutt doesn't save a copy in $record. Twice recently I used ""git imap-send"" to put a Git patch in my =Drafts folder, and then used mutt to send it ('m', yes use postponed, edit, send). These messages did not end up in my $record folder (=Sent). All other messages I send end up in $record as expected. }}}" antonio@… 3334 mail-client/mutt-1.5.20: UTF-8 locale -> character classes do no match mutt 1.5.20 defect mutt-dev new 2009-09-10T23:29:06-07:00 2009-09-10T23:29:06-07:00 "forwarding from http://bugs.gentoo.org/show_bug.cgi?id=284542 After an upgrade to mail-client/mutt-1.5.20-r4, I noticed problems in regex matching when using UTF-8. Specifically, most named character classes (e.g. [[:alpha:]]) fail to match when mutt is started with `LC_ALL=en_US.utf8 mutt`, but match correctly when mutt is started with `LC_ALL=C mutt`. I have noticed this failure to match in the mail reader's search search function and in attempting to match email with the save-hook command in configuration files. The problem also exists in mail-client/mutt-1.5.20-r5, but does not exist with mail-client/mutt-1.5.16 or mail-client/mutt-1.5.19-r1. " grobian 3360 Overrides manually set Mail-Followup-To with generated one mutt 1.5.20 defect mutt-dev new 2009-12-08T13:32:03-08:00 2009-12-08T13:32:03-08:00 "Hi I'm running Mutt 1.5.20-4ubuntu1 from current Ubuntu lucid and I reported a corresponding Ubuntu to track this issue; https://bugs.launchpad.net/ubuntu/+source/mutt/+bug/494207. I had to send an email to two mailing-lists I'm subscribed to, which are listed as ""lists"" in my Mutt config. I wasn't aware of the followup_to config, which was not set in my config (so defaults to yes) when I typed a Mail-Followup-To: header manually, pointing at only one of the lists. I postponed and re-edited the email multiple times with my manual header, which was preserved until I hit sent where it was overwritten with a M-F-T pointing at the two lists. I think Mutt should honor a manually set M-F-T. Thanks," lool 3363 Compose Menu: Can't add attachments with space characters in their path mutt defect mutt-dev new 2009-12-19T01:04:57-08:00 2009-12-21T13:14:43-08:00 "When I enter the path of attachments in the compose menu, mutt won't let me enter space characters, they are simply ignored. If I want to attach a file that has a space in its path, I thus usually need to copy it first somewhere else, e.g. into my tmp folder. I agree that spaces in file / directory names should be generally avoided, but sometimes third party software generates directory structures with such names and then it is a nuisance if you can't refer to the files in those hierarchies from mutt. Here are my mutt compile time settings: {{{ Mutt 1.5.20 (2009-06-14) Copyright (C) 1996-2009 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: Darwin 9.8.0 (i386) ncurses: ncurses 5.7.20081102 (compiled with 5.7) libiconv: 1.13 libidn: 1.15 (compiled with 1.15) hcache backend: GDBM version 1.8.3. 10/15/2002 (built Dec 6 2009 20:00:34) Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS +USE_SASL -USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/opt/local/share/mutt"" SYSCONFDIR=""/opt/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. patch-1.5.8.dgc.deepif.1 patch-1.5.8.ats.date_conditional.1 }}}" cludwig 3368 Message-hook paired w/ pipe-message display 1.5.18 defect mutt-dev infoneeded_new 2010-01-12T16:31:21-08:00 2010-04-03T17:04:14-07:00 "Hello, I would like every message that im displaying to be filtered (with procmail, to add the addresses contained with it to my address book). To achieve this I've already added this line to my .muttrc : message-hook . ""push procmail"" This results in the command being run repeatedly until I quit with Control-C. It seems just like to pipe the message, we have to access it which fires another message-hook so we gonna pipe it again, and so on. I havent found any posts on the net with the same subject, besides from this one: http://www.mail-archive.com/mutt-users@mutt.org/msg22103.html But the guy wasn't helped, unfortunately. Can you tell if my guess with the pipe command firing another message hook command is right? Is it a ""Bug we have accept for design reasons"" or could this be changed?" yeahns 3403 soft-fill doesn't count threads' tree lines mutt 1.5.20 defect me assigned 2010-04-09T13:01:26-07:00 2010-04-27T04:41:59-07:00 "I'm using an index_format like this: {{{ set index_format='%3C[%e] %Z %-15.15F %s%* (%4.4c) %{%y.%m.%d %H:%M}' }}} When getting a message with a very long subject, the soft-fill (%*) takes care that the date and the message size is always shown. However, when looking at threads, soft-fill fails to count in the tree branches of the threads in the index, and pushes the characters on the right side out of the window space. eg.: {{{ 1[1] N. L. Re: [munin-users] U when fetching plugin values from master, but re (4,9K) 10.04.09 13:29 2[2] G. P. └─>[munin-users] Maintenance of Munins SELinux policies (was: Re: U when (4,2K) 10.04.09 }}} You can see that the ""time"" string has disappeared in the second message, while with the first message soft-fill was succesful displaying everything that was meant to be displayed." daniell 3430 Mutt doesn't honor more than 16 color specifications mutt 1.4 defect mutt-dev new 2010-07-21T14:35:37-07:00 2010-07-21T16:34:45-07:00 "I have 256 colors enabled on my urxvt with up to 32767 pairs. If I define more than 16 color combinations for mutt, then the 1tth and following are not correct. This appears to me to be some sort of table overflow. Attached is a dot.muttrc file that demonstrates the problem. The indicator should be a light red on dark red, but instead it ends up being a bright yellow on default. Some other colors are messed up as well." SterlingCamden 3433 expired never updated after initial parse mutt defect mutt-dev new 2010-07-26T19:46:49-07:00 2010-07-26T19:46:49-07:00 "If you have a long-running mutt or use hcache, the expired flags (~E) are never updated as Expires dates pass unless the message is reparsed for some reason. (I have a fix for this in the context of an improved version of Omen Wild's patch which explicitly stores expires headers in the envelope, but short of that or time_t expires in HEADER, I don't have any better suggestions.)" dylex 3450 screen is not cleared when switching between emails display 1.5.20 defect mutt-dev new 2010-09-14T16:31:43-07:00 2012-07-06T22:49:56-07:00 "When I am reading email I sometimes move up and down my email list using j and k. However, the header information from the previous email is not cleared. This is most easily seen by making the header colored: color header magenta default ""^"" To prove it, redraw the screen using control-L. The material that should not be there goes away. I have marked this as critical because it gets in the way of reading email. I tried to upgrade: % mutt -v Mutt 1.5.20hg (2010-08-04) ... % mutt Error in .../.mutt/muttrc, line 407: smtp_url: unknown variable source: errors in .../.mutt/muttrc Hunh?? I need that variable! Google didn't help. What's the deal here?" toms 3468 Unable to open mailbox sent in append-mode maildir/mh 1.5.20 defect mutt-dev new 2010-11-04T07:35:32-07:00 2010-11-04T07:35:32-07:00 "I have an automated program that sends emails out automatically from our MRP system using the mutt command line. Occasionally we were getting Exit Code 1 and couldn't figure out why it was aborting. I downloaded 1.5.21 and compiled it with the debug option. I'm not sure why this is happening as the sent file exists. I have noticed that there is a sent.lock file in the sub directory with the sent folder, perhaps it isn't releasing the file lock? I'm stumped and critical emails aren't going out . . . help! [2010-11-04 08:41:10] Mutt/1.5.21 (2010-09-15) debugging at level 5 [2010-11-04 08:41:10] Reading configuration file '/usr/local/etc/Muttrc'. [2010-11-04 08:41:10] parse_attach_list: ldata = 0x80cdf64, *ldata = (nil) [2010-11-04 08:41:10] parse_attach_list: added */.* [9] [2010-11-04 08:41:10] parse_attach_list: ldata = 0x80cdf60, *ldata = (nil) [2010-11-04 08:41:10] parse_attach_list: added text/x-vcard [7] [2010-11-04 08:41:10] parse_attach_list: added application/pgp.* [2] [2010-11-04 08:41:10] parse_attach_list: ldata = 0x80cdf60, *ldata = 0x87e30b8 [2010-11-04 08:41:10] parse_attach_list: skipping text/x-vcard [2010-11-04 08:41:10] parse_attach_list: skipping application/pgp.* [2010-11-04 08:41:10] parse_attach_list: added application/x-pkcs7-.* [2] [2010-11-04 08:41:10] parse_attach_list: ldata = 0x80cdf5c, *ldata = (nil) [2010-11-04 08:41:10] parse_attach_list: added text/plain [7] [2010-11-04 08:41:10] parse_attach_list: ldata = 0x80cdf60, *ldata = 0x87e30b8 [2010-11-04 08:41:10] parse_attach_list: skipping text/x-vcard [2010-11-04 08:41:10] parse_attach_list: skipping application/pgp.* [2010-11-04 08:41:10] parse_attach_list: skipping application/x-pkcs7-.* [2010-11-04 08:41:10] parse_attach_list: added message/external-body [4] [2010-11-04 08:41:10] parse_attach_list: ldata = 0x80cdf58, *ldata = (nil) [2010-11-04 08:41:10] parse_attach_list: added message/external-body [4] [2010-11-04 08:41:10] Reading configuration file '/tmp/do_not_reply_muttrc'. [2010-11-04 08:41:10] send.c:1214: mutt_mktemp returns ""/tmp/mutt-d3-0-27625-655840911616609679"". ''[2010-11-04 08:41:15] mutt_write_fcc(): unable to open mailbox /home/rbiggs/sent in append-mode, aborting. ''[2010-11-04 08:41:15] mutt_free_body: unlinking /tmp/mutt-d3-0-27625-655840911616609679. " dkramer 3470 "Mutt asks ""Reply to ? ([yes]/no):"" for each tagged message when group replying" mutt defect mutt-dev new 2010-11-10T11:59:01-08:00 2010-11-14T10:05:02-08:00 "When group replying to a large number of tagged emails with reply-to headers, Mutt asks {{{ Reply to ? ([yes]/no): }}} for each message. If I'm group replying to 50 messages that all have a reply-to: header (don't ask, it happens sometimes) then I have to answer 50 times. It took me a long time to figure out that Mutt wasn't simply looping forever. This happens even if the reply-to header is identical for all messages. The cleanest work around from a user perspective might be to create a list of unique reply-to addresses and ask in a single prompt. Or maybe just ask once and let the user cleanup the to: when editing. Thanks, Omen" Omen 3480 IPv6 literal email-address fails mutt HEAD defect mutt-dev new 2010-12-18T20:39:34-08:00 2011-01-06T00:45:22-08:00 "Sending to a literal IPv6 address (test@[2001:470:ffff:aaaa::1], as an example) will fail. How to reproduce: 1) Make a new email To: anything@[2001:470:ffff:aaaa::1]"", as an example. 2) It gets transformed into the editor as ""To: anything@[2001: 470: ffff: aaaa: ;"" - Even if the user corrects the malformed literal IP in their editor, mutt will say ""No recipients are specified!"" when trying to send. Remco Rijnders informed me that it should be ""anything@[IPv6:2001:470:ffff:aaaa::1]"", but even then it has the same error (it malforms when mutt puts it into any editor). It would be nice if someone could look into this bug if they have time. Thanks." Harry 3481 Mutt mangles multiline links mutt defect mutt-dev new 2010-12-19T23:44:41-08:00 2010-12-20T01:29:31-08:00 "Even after getting rid of the ""+"" at the end of lines, multiline links still don't work in gnome-terminal (ie. clicking it only opens the link as it would be only on the first line). Piping to less works, so the gnome-terminal isn't at fault. Even irssi works, so ncurses in general should be ok. Seems like mutt is somehow handling the linewrap itself instead of letting ncurses take care of it, and that additional linebreak confuses the link recognition of terminals." hukka 3500 Text search does not work on long lines in the pager user interface 1.5.18 defect mutt-dev new 2011-02-07T03:30:01-08:00 2011-02-07T03:32:10-08:00 "When an email contains very long lines, then a search in the pager (using '/') only searches the first 1000 or so characters of each line. Any matches on the longer part of a line are silently ignored. With normal text email, this should not be an issue. However, it also occurs when viewing a mail part or attachment as text using the {{{view-text}}} command. In my particular case, I was looking at the HTML generated by Outlook, which is just a single line. Ugly, but well. Note that using ~b in a filter does look through the entire line, so this bug is limited to the pager search function. I suspect that there is a fixed 1024 byte or so buffer used in the searching. Not sure what the performance impact of fixing this would be, though." matthijs 3503 subject character encoding inconsistency mutt 1.5.21 defect mutt-dev infoneeded_new 2011-02-17T06:57:14-08:00 2011-06-20T16:40:30-07:00 "When displaying a message with isolatin characters in it, in the index list it contains question marks, but in the pager, it is displayed alright: Index:[[BR]] Fwd: [suncustomers_hu] Febru?ri h?rlev?l[[BR]] Pager:[[BR]] Fwd: [suncustomers_hu] Februári hírlevél My .muttrc's relevant lines: {{{ set assumed_charset='us-ascii:iso-8859-1:iso-8859-2:utf-8' set locale='hu_HU.ISO8859-2' set send_charset='us-ascii:iso-8859-1:iso-8859-2:utf-8' }}}" daniell 3505 Pressing 'c' in index doesn't cicle through folders with old email? mutt defect mutt-dev new 2011-03-07T04:54:39-08:00 2011-03-12T09:40:22-08:00 I'm not sure if this is a bug or not, but when pressing 'c' in index, Mutt cycles through folders with new email only. I think it should go to folders with old (unread) email after there isn't any new mail in any folder. ama 3515 Remove deprecated _set_priority GnuTLS functions (patch available) crypto 1.5.21 defect mutt-dev new 2011-05-03T11:18:20-07:00 2012-07-08T17:31:52-07:00 "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" antonio@… 3517 unable to append a message to a folder on a buggy imap server IMAP defect brendan new 2011-05-20T03:34:06-07:00 2011-06-25T19:47:40-07:00 "I just encoutered a problem using mutt to copy a message to a folder on a buggy imap server. The imap server in question, imap.163.com, is part of the free email service offered by one of the portal websites in China. The imap server does not support imap command pipeline, so I have to add ""set imap_pipeline_depth=0"" to .muttrc in order to access my mail account. But still, copying a local message to a folder in my imap account does not work, unless I specify my username in the imap URL. In another word, C imap://imap.163.com/ doesn't work[[BR]] C imap://wenzhuoz@163.com@imap.com/ works[[BR]] " zwz 3527 mutt: separation of host and CA SSL certificates mutt defect mutt-dev new 2011-06-27T03:48:22-07:00 2011-06-27T03:48:22-07:00 "mutt currently does not ensure that an SSL certificate accepted for one host is never used to verify SSL certificate of some other host. If user is willing to accept some host SSL certificates, the server may be able to SSL-MITM their connections to other mail servers. Self-signed certificate scenario:[[BR]] - Self-signed certificates usually have X509v3 Basic Constraint CA:TRUE. [[BR]] - If user accepts a self-signed certificate for e.g. imap.my-home-server.domain, it can later be used as a CA when verifying other certificates.[[BR]] - Anyone in possession of the server key/cert (my-home-server admin that went evil, a bad guy who managed to break into my-home-server) can now issue certificates for arbitrary hostnames and have them accepted by mutt as valid. subjectAltNames scenario:[[BR]] - mutt does not show subjectAltNames in the dialog prompting whether some SSL certificate should be accepted. It does not restrict accepted host certificate to only specific host. Any accepted certificate is hence valid for any of the ""hidden"" subjectAltNames the user was not notified about.[[BR]] - If accepting host certificate for a hostname that does not match any name in the certificate, ""#H"" header is added, but it currently only seems to serve as a hint mapping name to the not-matching certificate, rather than being a ""use-only-for"" hostname restriction. The ""#H"" header is not added when there is a matching name in the certificate.[[BR]] - This case is less interesting than the previous, as there's a malicious certificate to begin with, and the scope is limited to what's in subjectAltName. Proper fix would probably require using storage that tracks which certificates are host and which are CA, and ensure host certs are only accepted for a specific host. mutt currently allows accepting intermediate CA certs from cert chain provided by server. Not sure if any restrictions should be applied to such certificates, or it should be assumed that users have to know what they are doing when accepting that. Workaround: use separate certificate_file and ssl_ca_certificates_file for each mail account, or at least for account with different ""trust"" (such as home vs. work). Tested with mutt-20110627 nightly with gnutls." thoger 3536 patterns truncated at 1024 characters mutt 1.5.20 defect mutt-dev new 2011-08-22T12:04:42-07:00 2011-08-22T12:04:42-07:00 "Mutt seems to truncate patterns to 1024 characters. This makes it difficult to filter on very long patterns. To reproduce: 1) Send yourself 2 emails with these subjects: Axxxxxxxxxxxxxxxxxxxxxx1 AyyyyyyyyyyyyyyyyyyyyyyB2 2) to see all emails type: l~A you should see both the emails 3) Use a long (>1024 char) limit pattern which should make the first email visible and the second invisible: l~s^A~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA.....................~sB Notice that both emails are still visible. The ~sB at the end of the pattern got truncated. 4) use l~A to see all emails again 5) use a similar pattern that is long but less than 1024 characters: l~s^A~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA.....................~sB Now only the 2nd email is visible. (Unimportant Note: the above patterns match any subject that starts with A (~s^A) and contains A (~sA) and contains B (~sB). The subjects must also be at least 22 characters long (~sA.....................). The reason I used a pattern with .... is so that the truncation results in a valid pattern (truncation is in the middle of the dots). If you use a long pattern that gets truncated in a strange location you will instead see a ""missing parameter"" error. Here is an example: l~s^A~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sA~sB Thanks! -Acorn" acorn 3541 Search command should honour tag-prefix mutt defect mutt-dev new 2011-10-06T03:54:33-07:00 2011-10-10T06:56:17-07:00 "Today I wanted to only search messages that met certain other criteria. I started with a ""T"" to tag the messages and then tried "";/"" to search only the tagged messages. This doesn't work as expected - it searches all messages instead of just the tagged ones. When the search is expensive (body pattern match over IMAP, in my case) this can be a problem. "";/"" should just search tagged messages, like "";s"" and "";d"" do for saving and deleting." lukeross 3553 Apply reply_regexp as often as possible mutt 1.5.21 defect mutt-dev new 2011-12-01T01:45:36-08:00 2011-12-01T01:45:36-08:00 "By default, we set reply_regexp as follows: {{{ ""^(re([\[0-9\]+])*|aw):[ \t]*"" }}} Now if you receive an email that has a subject that starts with something like ""Re: Re: Re:"", added by broken mail clients, Mutt will only trim the first Re: tag when replying or showing it in the index. There are a lot of people that work around this by setting reply_regexp to something like this: {{{ ""^((re([\[0-9\]+])*|aw):[ \t]*)+"" }}} In my opinion this behaviour should be the default. Alternatively, we could solve this internally by changing the code to apply ReplyRegexp as often as possible. Attached is a patch that implements this." EdSchouten 3559 smime_keys.pl considers only first certificate of a chain crypto 1.5.21 defect mutt-dev new 2012-01-12T07:57:20-08:00 2012-01-12T07:57:20-08:00 "When smime_keys.pl is used as smime_import_cert_command to add keys via the extract-keys function (Ctrl-K), it gets the whole certificate chain from the pkcs7 data (via smime_pk7out_command and smime_get_cert_command). Before 1.5.21, smime_keys.pl split the certificates and handled them as separate user certificates, which was wrong. Now it takes the chain as a whole, which is better (best would be automatically splitting it into leaf certificate and intermediate chain certificates, but that would be asking too much), but since it now calls openssl to extract information from the whole chain (e.g. ""$opensslbin x509 -email"" in line 469), it gets information for the first certificate in the chain, which may or may not be the user's certificate - mutt appends the intermediate certificates to the user certificate, other MUAs start the chain with the root CA, the user's certificate being last. This results in (at least) no .index entry if the root CA certificate has no associated email address, or even a wrong .index entry. A solution would require to split up the chain of certificates, to reconstruct the correct order and to apply the single-certificate-commands to the user's certificate - well, then we're almost at the aforementioned automatic handling of intermediate chain certificates. If you see this as a valid point, but are in need of someone to code it, I'd volunteer to give it a try..." andy 3575 smime_keys.pl fails on filenames with spaces crypto defect mutt-dev infoneeded_new 2012-04-22T07:23:25-07:00 2012-12-31T21:03:58-08:00 "Forwarding from http://bugs.debian.org/658324 : {{{ Dear Maintainer, I recently needed to update by smime-keyring with a new version of my own certificate to a new one, and saved it to a file named ""cacert kandre@ak-online.be renewed.p12"". Unfortunately 'smime_keys add_p12 ""cacert kandre@ak-online.be renewed.p12""' failed with the return code 256 from openssl and a dump of it's commandline options. I looked into smime_keys and found that the perl-script builds the command in line 156 directly from $ARGV[1]: >>>> snip <<<< 156: my $cmd = ""$opensslbin pkcs12 -in $ARGV[1] -out $pem_file""; 157: system $cmd and die ""'$cmd' returned $?""; >>>> snip <<<< The error-message also contained the exact commandline it tried to execute which was: >>>> snip <<<< '/usr/bin/openssl pkcs12 -in cacert kandre@ak-online.be renewed.p12 -out cacert kandre@ak-online.be renewed.p12.pem' returned 256 at /usr/bin/smime_keys line 157. >>>> snip <<<< As there were no quotation marks around the filename I tried it with a symlink to the same file, but without any space in the filename and it worked like a charm. I therefore think that there is some kind of escaping of $ARGV[1] neccesary to stop smime_keys from passing the spaces directly to the shell that executes openssl. Kind regards, Andre }}}" Y_Plentyn 3578 arbitrary MAILDIR outside HOME impossible mutt 1.5.21 defect mutt-dev infoneeded_new 2012-04-26T12:29:25-07:00 2012-12-01T15:04:25-08:00 "There is no way to use mutt with an arbitrary MAILDIR $ MAILDIR=/tmp/Mail/backup/ mutt In all cases it is assumed these reside within the users home directory, even if he does # su - nobody HOME=/tmp etc. etc." jidanni 3581 Folder-history ignores -f folder from CLI mutt HEAD defect mutt-dev new 2012-05-18T05:07:29-07:00 2012-05-18T10:40:29-07:00 "When you start mutt giving -f folder on the command line, that folder is not included among the suggestions (already seen folders) which appear when (later in the session) you press 'c' to change folder and use at the prompt. For a fix, it may be enough to add something of the sense if (explicit_folder) mutt_history_add (HC_MBOX, folder, 1); in main.c e.g. somewhere around line 994, only in this form it is not possible because of variable scope. A hack with a wrapper in history.c worked for me." Wastl 3595 problems suspending mutt when called from shell script mutt 1.5.21 defect mutt-dev new 2012-10-11T08:34:36-07:00 2013-04-15T01:57:45-07:00 "Things seem to go wrong when I invoke mutt from a shell script (in a terminal session on Linux) and then press control-Z to (try to) suspend both mutt and the script. The ""suspend"" part works fine and takes me back to the shell prompt, but when I type""fg"" to try to resume mutt, strange things happen: I have to type ""fg"" more than once to resume at all, and then mutt is in some strange mode in which it doesn't respond correctly to keyboard input (e.g., 'j' and 'k' are echoed but otherwise seem to have no effect). I can exit by typing 'q' or 'x' *twice*, or by pressing control-C. I have access to several different versions of mutt on different systems; 1.4.2 does *not* have this behavior, but mutt 1.5.20 and 1.5.21 do. Sample shell script: #!/bin/sh echo ""hello"" mutt echo ""goodbye"" Not a showstopper but quite annoying. " blmassingill 3596 "Incorrect progress message ""(-2147483648%)""" user interface 1.5.21 defect mutt-dev infoneeded_new 2012-10-15T14:13:30-07:00 2012-12-01T14:50:46-08:00 "When mutt is fetching message headers from my IMAP account on startup, I observe incorrect progress message such as: ""Fetching message headers... 196/2377 (-2147483648%)"" where ""474"" keeps changing but other numbers (196, -2147483648) remain the same. This is with the binary that came with Ubuntu 12.04.1 LTS. When I built my own binary from the latest source code (v1.5.21) and ran it on the same IMAP account, I didn't observe the erroneous behaviour. Therefore, I believe it may be hard for others to reproduce, and analyzing the source code may be the only way to find when the percentage value can be -2147483648. 'mutt -dX' doesn't seem to produce any information that helps understand why the calculation is incorrect (even when X=5); the only messages regarding the progress update are like the following: [2012-10-15 13:58:36] updating progress: 196 [2012-10-15 13:58:36] Fetching message headers... 196/2377 (-2147483648%) Please let me know if there's more information or help I can give." musiphil 3618 incorrect background display display HEAD defect mutt-dev new 2012-12-31T20:46:09-08:00 2013-01-01T17:15:25-08:00 "Background display is sometimes incorrect, e.g. on the following mailbox: {{{ From a@b.c Sun Dec 16 18:45:58 2012 Subject: FREE() and safe_free() From e@f.g Sun Dec 16 22:01:06 2012 Subject: Re: FREE() and safe_free() }}} and muttrc: {{{ color header brightwhite blue ^subject: }}} If messages 1 and 2 are viewed alternatively without going back to the index (e.g. with the left and right arrow keys), the length of the blue background decreases by 3 to 4 characters each time message 1 is viewed." vinc17 1441 can't of a message/rfc822 attachment ed in compose display enhancement me accepted 2003-01-20T19:32:13-08:00 2010-08-13T13:19:13-07:00 "{{{ Package: mutt Version: 1.5.3-1 Severity: normal [NOTE: this bug report has been submitted to the debian BTS as Bug#177504. Please Cc all your replies to 177504@bugs.debian.org .] From: Allan Wind Subject: Subject:view-header (v) does not work in forwarded message Date: Mon, 20 Jan 2003 00:19:42 -0500 (EST) To reproduce: 0. Create $HOME/.muttrc2 with the following content: set forward_edit = no set mime_forward = yes 1. Start mutt with this configuration file: `mutt -F $HOME/.muttrc2` 2. Send message to self with at least one attachment. 3. Find message and forward (f) it to self (but do not send it). 4. In compose screen, now select original message (down arrow, enter). 5. View attachments (v) and observe that you are returned to Compose screen instead of being able to view the attachements. -- System Information Debian Release: testing/unstable Kernel Version: Linux pawan.dyndns.org 2.4.19 #5 Sun Oct 6 02:29:18 EDT 2002 i686 unknown unknown GNU/Linux Versions of the packages mutt depends on: ii libc6 2.3.1-9 GNU C Library: Shared libraries and Timezone ii libncurses5 5.3.20021109-2 Shared libraries for terminal handling ii libsasl7 1.5.27-3.3 Authentication abstraction library. exim Not installed or no info ii postfix 2.0.2-1 A high-performance mail transport agent ^^^ (Provides virtual package mail-transport-agent) >How-To-Repeat: >Fix: }}}" Marco d'Itri 2060 cannot send multipart/alternative from the command-line mutt 1.5.10 enhancement mutt-dev new 2005-09-07T18:12:56-07:00 2010-08-08T15:58:04-07:00 "{{{ $ mutt -e ""set content_type=multipart/alternative"" -s test kyle@commsecure.com.au < /tmp/kkk No boundary parameter found! [report this error] No boundary parameter found! [report this error] Could not send the message. $ cat /tmp/kkk MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=""===============1195369947=="" --===============1195369947== MIME-Version: 1.0 Content-Type: text/plain text message --===============1195369947== MIME-Version: 1.0 Content-Type: text/html html message --===============1195369947==-- >How-To-Repeat: >Fix: Unknown }}}" kyle@… 2073 mutt should have a CA certs directory option mutt enhancement mutt-dev new 2005-09-18T16:06:24-07:00 2010-08-24T10:41:41-07:00 "{{{ mutt has the ssl_ca_certificates_file option, but an option like ""ssl_ca_certificates_dir"" to pick up all the CA certs in a directory would be useful. >How-To-Repeat: >Fix: Unknown }}}" dave@… 2895 mutt should keep a deletion log mutt enhancement mutt-dev new 2007-05-26T17:34:45-07:00 2008-10-12T06:27:00-07:00 "After spending the past hour or so deleting piles of old email, and then watching mutt crash because of some sort of bizarre server-side IMAP bug, and losing track of all my deletions, I am somewhat frustrated. It would be nice if mutt could keep a deletion log of messages deleted, such that, when this case happens, it would be possible to restore the log in a new mutt and not have to painstakingly find those deleted messages and delete them again. Of course it would be nice to fix all the bugs that could cause mutt to crash and people to lose work. In this case, it is a difficult-to-debug IMAP interaction that I think is really a server-side problem (but of course mutt shouldn't crash in any case)... So this enhancement request is really a band-aid. Still, I think it would be a very helpful band-aid to have." jhawk 2898 mutt-1.5.14: mutt's pager should strip spurrious ^M, most of the time display 1.5.15 enhancement new 2007-05-28T20:34:07-07:00 2011-04-13T04:23:00-07:00 "Some domains seem to manage to send e-mail where every linebreak is a `\r\n`. I'm not sure why they do this. The only one I've encountered with great regularity is DOLBY.COM, though there was one other I got last week that I seem to've misplaced, but it caused me to put this on my queue. They only seem to arrive in quoted-printable... Anyhow, mutt's pager displays these messages with a `^M` at the end of each line, which really looks awkward and hard to read, e.g.: {{{ Lorem ipsum dolor sit amet, consectetaur adipisicing elit, sed do^M eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad^M minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip^M ex ea commodo consequat. Duis aute irure dolor in reprehenderit in^M voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur^M sint occaecat cupidatat non proident, sunt in culpa qui officia^M }}} (Okay, it's worse when you're actually reading the language across the line break.) Attached is a patch such that mutt throws away `^M`s unless OPTWEED is set, so that if you turn on full headers ('h'), these `^M`s are displayed. If you'd prefer to handle it a different way, let me know and I will re-spin the patch. Previously, mutt unconditionally escaped all `\r` chars as ""`^M`"". I realize this is the sender's fault, but I don't think I should have to put up with it. (I could fix this with a display_filter, but then it would be harder to toggle, I'd pay a fork penalty, and other mutt users wouldn't get the benefit). (I realize the patch uses a goto -- I do think it's clearer to add an elsif stanza for the `\r` case and use a goto to the control-character label, rather either duplicating the control-char printing code in `\r` stanza, or adding {{{ || wc=='\r' && !option(OPTWEED) }}} to the control characer case (line 1184, `wc < 0x20`...). If you'd prefer a goto-less version, I can do that too...) {{{ --- /afs/sipb.mit.edu/project/sipb/src/mutt/mutt-1.5.15/pager.c Sun Apr 1 17:58:56 2007 +++ mutt-1.5.15/pager.c Mon May 28 22:59:28 2007 @@ -1175,8 +1175,15 @@ else col = t; } + else if (wc == '\r') + { + if (!option(OPTWEED)) { + goto controlchar; + } + } else if (wc < 0x20 || wc == 0x7f) { + controlchar: if (col + 2 > wrap_cols) break; col += 2; 2007-05-28 22:59 -0400 John Hawkinson * pager.c: Hide ^Ms in messages when OPTWEED ('h': suppress full headers) is set. For those rare people who get email with linebreaks ending in \r\n. }}} Thanks. --jhawk@mit.edu John Hawkinson" John Hawkinson 2916 Message Age in $index_format; %g display enhancement mutt-dev new 2007-06-20T14:15:01-07:00 2007-06-20T21:25:20-07:00 "Some are interested to see the age of a message instead of its absolute date in $index_format. I propose to add `%g` and `%G` sequences to $index_format format strings. I've attached a patch that implements this feature. %g = the age of the message (uses time sent) %G = the age of the message (uses time received) The patch uses this format: ||Notation||The message was received|| ||2m||two minutes ago|| ||5h 34m||5 hours and 34 minutes ago|| ||1D 21h||1 day and 21 hours ago|| ||2M 12D||2 months 12 days ago|| ||3Y 11M||3 years 11 months ago|| " aligrudi 2925 directory browser: use destination's time + size rather than symlink's browser enhancement mutt-dev new 2007-06-27T13:07:26-07:00 2009-06-30T07:37:34-07:00 "When have symlinks in directory, only interesting property is the type being symlink. Time + size of the link is uninteresting 99% because they rarely change, no benefit when the directory is sorted by time/ size, while the symlink's destination properties change whenever the file/ dir changes (by saving to or deleting from it)." rado 2963 optimization: link() can be used in e.g. mbox-hook for maildirs maildir/mh enhancement mutt-dev new 2007-09-22T15:39:23-07:00 2009-06-30T07:37:48-07:00 "if source and destination mailboxes are maildirs and the both are on the same filesystem, link() (and unlink() for source email if link() succeeds) can be used instead of read() and write() as an optimization, if there have been no modifications in the source email (e.g., deleted attachments). maildir_flags needs to be made extern instead of static. it can be used in constructing the destination filename for link(). I'd also recommend that you update maildir format to newer one. http://cr.yp.to/proto/maildir.html I have made these changes this way: 1) add function mutt_move_message into copy.c 2) in mx.c, before mutt_append_message, try to call mutt_move_message. this is pretty simple. I have been testing a bit and it seems to work... " Safari 2973 configurable encrypt-to-self with gpgme crypto 1.5.16 enhancement mutt-dev new 2007-10-26T07:51:23-07:00 2008-05-17T18:42:12-07:00 According to a thread [http://marc.info/?l=mutt-users&m=119262851607365&w=2 (1)] on mutt-users mailing list I propose a config option for encrypt-to-self with gpgme. My opinion is this should be no global option of GnuPG but a per application thing as Thunderbird/Enigmail handles this too. LeSpocky 2998 change_folder_next has vanished mutt 1.5.17 enhancement mutt-dev reopened 2007-12-05T20:46:21-08:00 2007-12-06T15:19:19-08:00 When upgrading from 1.4.something to 1.5.17, I noticed that the setting change_folder_next appears to have vanished, and not been replaced with equivalant functionality. Can we have it back? cjs 3019 Wish: auto-delete certain incoming attachments mutt enhancement mutt-dev new 2008-01-23T19:39:40-08:00 2008-01-24T03:02:42-08:00 "I get a lot of emails that routinely include an image attachment as a signature (e.g. corporate logo that wastes 43K in every message). The filenames of the images may vary (e.g. pic15146.jpg, every time it's a different number in the filename), but these files' contents always match something in a small set of images that I don't want to keep seeing/storing. I'd like, either when I retrieve messages via POP, or when I view the message, for Mutt to automatically compare the attachments' checksums against a list of known values, and if an attachment happens to match something in my list, automatically delete that attachment, without any direct action needed on my part. On a related note, as various people reply to a message that had attachments, the same attached files will often reappear in each reply. I'd like for Mutt to recognize that some of the attached files are copes of other attachments that I've recently received in other messages, or that I've sent out. In this case, I'd want Mutt to ask me before deleting the attachment from the newly-received message." kscott 3051 get patchlist.sh input from mqueue when mq is in use build 1.5.17 enhancement mutt-dev new 2008-04-28T15:59:58-07:00 2009-06-30T07:37:58-07:00 "PATCHES is easy to bungle without mq, and easier yet with. But if mq is in use, why not ""require"" mq for managing all patches at the local site, and draw the patchlist from mq? This works nicely, and doesn't mess with PATCHES if it's present." dgc 3052 [PATCH] Customisable description for MIME cryptographic signatures crypto enhancement mutt-dev new 2008-05-04T22:01:33-07:00 2009-02-23T20:18:24-08:00 "When using PGP with GPGME to sign messages, an application/pgp-signature part is added to the message, containing the GPG-signed hash of the text part. This attachment does not have a description, which tends to confuse non tech-savy recipients (depending on their MUA) who try to manually open the signature and, of course, fail. Adding a default description when signing (with PGP, but maybe also using other schemes?) a message would help preventing this type of situation. Additionally, a user-configurable variable could be supplied (say, `pgp_signature_description`)." shtrom 3062 Add folder_format code so users can display both RECENT and UNSEEN when using IMAP IMAP enhancement brendan new 2008-05-27T12:34:58-07:00 2010-06-29T02:32:05-07:00 "I recently upgraded from 1.5.11 to 1.5.18, and to my surprise the %N code in folder_format suddenly shows the amount of UNSEEN messages instead of RECENT. I really liked the old behavior, which I successfully restored with http://dev.mutt.org/trac/attachment/ticket/2897/mutt-imap_recent.patch. But how about allowing both? They cover different use cases, both of which I feel would be useful for me. During my regular mail reading I'm interested in the number of RECENT messages, but when I have some extra time and want to catch up on some of the UNSEEN ones, I'd like a quick way to spot the relevant mailboxes without having to open them all and look. How about having %N count RECENT messages, and %O count UNSEEN? I believe this would be the most intuitive naming, since the characters then match the output of %Z in index_format and the ~N and ~O regex escapes. Please let me know what you think :-)" knuta 3065 new pattern modifiers ~a and %a to search all address fields of the envelope mutt enhancement mutt-dev new 2008-05-30T08:29:58-07:00 2010-02-08T11:07:10-08:00 "The attached patch adds new pattern modifiers ~a and %a to match messages which contain EXPR (or a member of GROUP) in some envelope address field, i.e. one of: {{{ ADDRESS *return_path; ADDRESS *from; ADDRESS *to; ADDRESS *cc; ADDRESS *bcc; ADDRESS *sender; ADDRESS *reply_to; ADDRESS *mail_followup_to; }}}" vinc17 3067 "PGP/MIME signatures incorrectly assigned ""Content-Disposition: inline""" crypto enhancement me started 2008-05-31T10:45:31-07:00 2010-08-24T12:51:40-07:00 "I believe that mutt is incorrectly assigning the Content-Disposition of PGP/MIME signature attachments as ""inline"". This causes some MUAs (eg. gmail) to feel the need to display the attached signature inline, instead of as an attachment. I believe that the Content-Disposition should instead be set to ""attachment"", since that is in fact what it is. I notice, though, that the Content-Disposition is specifically hard coded in the mutt pgp.c source to be ""DISPINLINE"" instead of ""DISPATTACH"". I wonder why this is, since it appears to be a deliberate choice. This seems wrong to me, but I would be curious to hear a justification. The patch is very very simple. It involves changing [source:pgp.c@5410:73a180edce53#L1111] from: {{{ t->disposition = DISPINLINE; }}} to {{{ t->disposition = DISPATTACH; }}} I applied this patch to the Debian Lenny version 1.5.17 of mutt and it worked perfectly. I haven't checked it with the current head of your repo, but I have no reason to suspect it wouldn't work. If there is reasonable justification for keeping the default to be DISPINLINE, then maybe we could make a patch where the value of the Content-Disposition is set by a mutt variable, herefore allowing users to easily change it if need be. I think that it should we set DISPATTACH, though, as PGP/MIME signatures should be attachments, not inline. Thanks for maintaining such a great MUA." jrollins 3073 next-flagged function, for selecting next message which is flagged mutt enhancement mutt-dev new 2008-06-08T08:17:18-07:00 2008-06-10T10:59:05-07:00 "It would be fine to have function ""next-flagged"" which allows to select next message in current dir which is flagged. This is particularly important feature for peoples (like me :-) which heavily use flagging. Working patch for hg tip (changeset: 5417:5ab92dd44ce2) is attached (but it's something like POC implementation)" anydot 3076 Enhancement of pseudo Attach: header mutt 1.5.18 enhancement mutt-dev new 2008-06-13T06:17:14-07:00 2008-06-19T15:34:42-07:00 "Hi, this is my first bug report, so please be gentle ;) As you know, you can attach files when editing messages, using the pseudo Attach: header. Unfortunally this header is not displayed, whenever you re-edit a message (e.g. when you edit a postponed a message). Therefor I have written the following patch, which will insert pseudo Attach: headers for each file, that is attached. My C Skills are actually very limited since I have not used C for years, so I apologize for my code ;) regards, Christian" chrisbra 3078 RFE: a way to abort a long operation (e.g. Ctrl-C / ^C / SIGINT) mutt enhancement mutt-dev new 2008-06-16T06:33:09-07:00 2009-02-20T10:38:37-08:00 "Mutt should have a way to immediately abort an operation because it can take a very long time, e.g. like opening a very large mailbox or doing a limit on the body contents of a very large mailbox. This should probably be done when receiving the SIGINT signal (usually, triggered by Ctrl-C). If the operation was executed from a macro, the whole macro should terminate. Now, I don't like that very much, as it could prevent some clean-up (like restoring settings). A solution could be a post-interrupt key-sequence for macros... Note: Ctrl-\ (SIGQUIT) aborts the operation, but also Mutt itself. So, this is a bit too strong." vinc17 3144 Parent and child match pattern modifier mutt enhancement mutt-dev new 2009-01-02T03:37:42-08:00 2009-03-19T17:41:08-07:00 "This patch implements the < and > pattern modifiers, to match against the following pattern against the parent message and the child messages respectively, instead of the current message itself. For example, all messages that have at least one duplicate that has been read: >(~= !~N) All replies to one of your mails (whose parent message has been issued by you): <~P" jlh 3160 support for more mailing list headers to detect list mail mutt 1.5.18 enhancement mutt-dev new 2009-01-25T14:51:26-08:00 2009-01-27T06:58:58-08:00 "Forwarding from http://bugs.debian.org/463637 --- I have the following two lines in my ~/.muttrc: subscribe www-tag@w3.org color index yellow default ~l This should be enought to highlight any mail addressed to the www-tag@w3.org mailing list as yellow but it fails to recognise certain headers of which a non-exhaustive list follows: X-Mailing-List X-Loop X-Original-To List-Id Resent-From Any one of these can be used to determine the mailing list when the actual To address is obscured because of a BCC. I have attached a sample mbox with a message which is missed by the config sample I have included above. " antonio@… 3167 [patch] Provide SSL cipher selection option for imap/smtp/pop crypto 1.5.21 enhancement mutt-dev new 2009-01-26T13:25:33-08:00 2012-06-28T12:51:02-07:00 "Enh request to provide cipher options for imap/smtp SSL. Currently it seems to pick the first cipher advertised by the server, which can be quite weak - for example imaps://imap.gmail.com:993 uses RC4-MD5 even when specifying ssl_use_sslv2=no and ssl_use_sslv3=no. (as seen on 1.5.18) (maybe this could be a wishlist item for 1.6...)" cowbert 3177 "mutt wish: send_charset default ""us-ascii:utf-8""" charset 1.5.19 enhancement mutt-dev new 2009-01-28T13:26:50-08:00 2009-06-30T07:38:09-07:00 "Forwarded from http://bugs.debian.org/441950 --- Currently the send_charset default compiled into mutt is ""us-ascii:iso-8859-1:utf-8"". In the third millenium, with virtually all software supporting UTF-8 and most users using UTF-8 locales, it would be nice if this could be changed to ""us-ascii:utf-8"". This would e.g. make the sent-mail folder containing only UTF-8 and not a mixture of two incompatible charsets. " antonio@… 3190 option to disable replacing deleted attachments with a note about their deletion mutt 1.5.19 enhancement mutt-dev new 2009-02-19T10:53:52-08:00 2009-02-19T10:53:52-08:00 "{{{ Forwarding from: http://bugs.debian.org/516189 --- If I delete an attachment with mutt, it replaces it with a pseudo-attachment, such as: Content-Type: message/external-body; access-type=x-mutt-deleted; expiration=""Thu, 19 Feb 2009 19:09:30 +0100""; length=2077 Content-Type: text/html; charset=""utf-8"" Content-Transfer-Encoding: quoted-printable This makes sense in many cases, but some times this is not wanted. It would be nice if mutt had an option that would control the behaviour. }}}" antonio@… 3193 mutt: debug file location should be configurable mutt 1.5.19 enhancement mutt-dev new 2009-02-20T14:08:22-08:00 2009-02-20T14:08:22-08:00 "Forwarding a request from http://bugs.debian.org/516364 {{{ Hi, this change request is about the location of .muttdebugN files, at the moment they are written into $HOME, we'd like to have the place where the files are written configurable by an option in .muttrc Cheers Antonio }}}" antonio@… 3203 Print Newsgroup header mutt enhancement mutt-dev new 2009-03-11T11:06:52-07:00 2009-03-11T11:06:52-07:00 "Consider you use tin as newsreader. The default behaviour of tin is to store posted messages in the ""posted"" mailbox file in the user's mail folder. If you use the same folder to store outgoing mail (set record=) you might want to set the $index_format for this folder to something along the lines of folder-hook posted ""set index_format='%Z %D %-18.18t (%?M?#%2M&%3l?) %s'"" That's what I do, at least. However, if you look into that file in mutt, all the newsgroup postings supposedly have no recipient because the %t from the $index_format prints nothing. There's just no ""To"" field. I created the attached patch to define a new field specifier %G which allows to print the Newsgroup header. It also adds the ability to conditionalize %t output. So what you can do now is to specify %?t?%24.24t&%24.24G? to get either the ""To:"" field, if it's available, or the ""Newsgroup:"" field if not. The patch is preliminary, but it works nicely. I'm using it locally for three weks now. It's missing comments and documentation so far. Apart from adding the documentation I guess it would also be a good idea to add newsgroup munging if the field width is smaller than the length of the newsgroup name. For instance, assuming the field width is 18 chars, then Ng de.alt.rec.digitalfotografie becomes Ng de.alt.rec.digi It should better be tweaked into Ng d.a.r.digitalfot However, before I put more time into this little project, I'd like to know if that has any chance of inclusion into mutt at all. If so, I'd be quite happy to implement the missing stuff as outlined above. Thanks, Corinna" vinschen@… 3207 Conform to XDG Base Directory Specification mutt enhancement mutt-dev new 2009-03-23T07:56:02-07:00 2009-03-23T10:12:48-07:00 "http://standards.freedesktop.org/basedir-spec/basedir-spec-0.5.html It'd be nice if mutt conformed to freedesktop's XDG Base Directory Specification. If all applications conformed to this, it'd make backing up important config files, while ignoring large directories such as ~/.mozilla, fast and easy." wraichia 3225 new mail notifications are lost too easily mutt 1.5.19 enhancement mutt-dev new 2009-05-13T14:17:28-07:00 2009-05-13T15:36:44-07:00 "A ""new mail"" notification may appear when typing something, but will disappear as soon as a second key is typed. For instance, if one wants to move the cursor to some message by typing the up-arrow key several times, the notification disappears almost instantly. IMHO, the notification should be kept on screen until something else appears in the command line." vinc17 3236 mutt: should use /var/tmp for mail drafts by default mutt enhancement mutt-dev new 2009-05-26T15:50:58-07:00 2012-09-27T06:21:28-07:00 "Forwarding from http://bugs.debian.org/530584 {{{ By default, mutt stores drafts in /tmp/mutt-$HOSTNAME-$UID-$PID-$REV. /tmp is designed to hold data that isn't guaranteed to be preserved between different invocations of programmes. For practical purposes, and on Debian at least, this translates to files being deleted on every boot, unless TMPTIME is amended in /etc/default/rcS and /tmp is not a tmpfs. This behaviour can cause loss of data, e.g. when the laptop dies or turns itself off due to low power; the user might not have a chance to commit the temporary mail draft s/he was working on to non-volatile storage. I suggest that mutt should use /var/tmp by default for its mail drafts, as that directory is also temporary in nature, but cleaned less frequently than /tmp. More specifically, the FHS dictates that ""files and directories located in /var/tmp must not be deleted when the system is booted."" Attached are two patches, one for the code and what looks like the source of the documentation (init.h), and another patching the docs, which look like auto-generated content. Thanks for your consideration, }}} " antonio@… 3245 mutt: aliases for mailboxes mutt enhancement mutt-dev new 2009-06-12T16:15:36-07:00 2009-06-18T06:01:41-07:00 "Forwarding from http://bugs.debian.org/291798 {{{ I would like to see a feature for aliasing mailboxes. Especially when using remote mailboxes with IMAP it is very inconvenient to type imap://mylongusername@myevenlongerhostname.com/ So a feature to give such mailboxes additional shorter names would be great. Regards Marco }}} In the original debian bug there was a discussion about the usage of folder hooks but there are mutt users who have many IMAP mailboxes on many IMAP servers and having a folder-hook for each account could be a nightmare" antonio@… 3247 mutt: should provide options for cipher selections crypto enhancement mutt-dev new 2009-06-12T16:26:48-07:00 2009-06-12T16:26:48-07:00 "Forwarding from http://bugs.debian.org/481500 {{{ When authenticating against a dovecot IMAP server, mutt now uses AES128, not AES256. There is no reason that mutt should use a weaker cipher. This problem has occurred before and upstream provided the rationale that other parts of the cryptosystem are weaker than the 256-bit symmetric cipher, so there is no real gain in security. However, that is no reason to deliberately cripple one part of the cryptosystem, and 256-bit AES is only slightly slower than 128-bit AES (I know, I've implemented both). }}} " antonio@… 3249 mutt: Should have option to set editor position past headers mutt 1.5.19 enhancement mutt-dev new 2009-06-12T16:32:20-07:00 2009-06-17T04:06:26-07:00 "Forwarding from http://bugs.debian.org/504462 {{{ With edit_headers=yes, Mutt will include the mail headers in the mail when starting the editor. I'd like Mutt to also pass the editor option that skips past those headers to the first line of the actual message. Many editors support the syntax ""$EDITOR +$LINE $FILENAME"", including vim, emacs, nano, and gedit. Mutt simply needs to pass the appropriate line number. }}}" antonio@… 3250 thread-link/-delink messages even when threading is not enabled mutt 1.5.19 enhancement mutt-dev new 2009-06-12T16:33:37-07:00 2009-06-12T16:33:37-07:00 "Forwarding from http://bugs.debian.org/508423 {{{ When thread-sorting is disabled, linking and delinking messages with link-thread and break-threads does not work but instead produces the error ""Threading is not enabled"". Yet, sometimes it would be useful to be able to thread-link when messages are sorted e.g. by sender or recipient, not arranged in threads. I can't see how threading is required to create/break threads, it's really only a display option, or well, it should only be. It would be nice if I could use link-thread and break-threads even when $sort!=threads. }}}" antonio@… 3251 mutt: would be nice to have a pattern for inline-encrypted mail (send2-hook) mutt 1.5.19 enhancement mutt-dev new 2009-06-13T01:52:14-07:00 2009-06-13T01:56:19-07:00 "Forwarding from http://bugs.debian.org/302010 {{{ It would be nice to have a pattern (like ~g and ~G) that matches mail that is encrypted ""inline"". As an example of how it could be very useful... Some of the people I send mail to use pine and as such can only decrypt inline pgp messages. I would like to be able to make sure that when I send messages to them, I send the messages encrypted/signed inline. This generally works by using a pattern of '~C pineusingfriend@wherever.com', but I would like this to also trigger when adding them to the sending list in the compose menu (i.e. from a send2-hook). Within a send2-hook, changing the encryption settings (which requires the use of ""push"") triggers the send2-hooks again. Therefore, I can't just use '~C pineusingfriend' as the pattern to match, because that would cause an infinite loop (every time, the command to change the encryption settings causes the send2-hooks to be triggered again). Thus, something like this: send2-hook '~C pineusingfriend' 'push pfpbpi' causes an infinite loop. If, however, there was something like ~I that matched ""pgp inline messages"", I could use: send2-hook '~C pineusingfriend ! ~I' 'push pfpbpi' and it would work properly. }}}" antonio@… 3253 "mutt: Please make ""myself not in M-F-T to posts in subscribed lists"" optional" mutt enhancement mutt-dev new 2009-06-13T02:15:13-07:00 2009-06-13T02:15:13-07:00 "Forwarding from http://bugs.debian.org/426142 {{{ I like to get CCs of replies to posts I make to mailing lists. Mutt hardcodes that I will not, in the Mail-Followup-To header it will add. Here's the patch I use to change that. Use of ""list"" instead of ""subscribe"" is not adequate for that because ""lists"" does not have the effect of ""subscribe"" on %L and %T in index_format, nor on ~u in a search/tag/limit pattern. It is desirable to keep that effect (because I _am_ subscribed to the said mailing lists), but I just _do_ want CCs in subthreads I participate in. For general consumption, it should be changed to make it an option. Or even better, have ""subscribe"", ""list"" and ""subscribe-cc"" so that the choice is per-list. }}}" antonio@… 3254 please make postponed searcheable mutt enhancement mutt-dev new 2009-06-13T02:36:56-07:00 2009-06-13T02:36:56-07:00 "Fowarding from http://bugs.debian.org/492278 {{{ Hello, I'd like to be able to sort and search messages in the postponed folder like every other folder. Unfortunately, this does not seem to be possible. It would make mutt even better if this feature could be added. }}} Obviously the user can use c? =postponed but it seems that he wants to have the folder searcheable when he recall a message." antonio@… 3255 mutt: Notification support without polling mutt enhancement mutt-dev new 2009-06-13T03:05:56-07:00 2009-06-13T03:05:56-07:00 "Forwarding from http://bugs.debian.org/323195 {{{ It would be nice to allow notifications when new mail arrives, so mutt doesn't need to poll for it. When running mutt on the machine where mail arrives, a program like procmail could be used to send a SIGUSR1 to mutt whenever there is new mail, for example. However, mutt doesn't support any notification to trigger new mail checking. If this would be implemented, mutt can completely go to sleep and optionally be swapped out if there is no activity. Without it this is impossible, because it's checking for new mail every so often. }}}" antonio@… 3257 should update header cache for target folder header cache enhancement mutt-dev new 2009-06-13T03:14:09-07:00 2009-06-30T07:38:23-07:00 "Forwarding from http://bugs.debian.org/436226 {{{ When I a message to another folder, mutt does not update the header cache of the destination folder. This means that when I open the destination folder, mutt notices a change and has to reindex the Maildir. At the time of , mutt knows exactly what change is being made and could update the destination's header cache with much less effort than when opening the mailbox and having to figure out what needs updating. It would thus be nice if mutt updated the destination's header_cache after successfully saving a message to another folder. }}}" antonio@… 3258 add an option to write a header summary and exit mutt enhancement mutt-dev new 2009-06-13T03:21:56-07:00 2009-06-13T03:21:56-07:00 "Forwarding from http://bugs.debian.org/456492 {{{ Add this feature from mail(1) -H, --headers Write a header summary and exit }}} It is useful when checking things when one only has TERM=dumb over an ssh session on a emacs shell window. Sorry, I should have sent the bugs to upstream directly. " antonio@… 3259 should be able to delete certain attachments in crypted mail mutt enhancement mutt-dev new 2009-06-13T03:30:24-07:00 2012-10-29T04:11:26-07:00 "Forwarding from http://bugs.debian.org/439308 {{{ I understand perfectly that in mutt, deleting an attachment might mean: Deletion of attachments from encrypted messages is unsupported. (although this is a signed message). If the attachment is included in the portion of the body, which was signed, this is how it is. However, if the attachment is outside the [-- XXXXX PGP SIGNED MESSAGE --] limits, there is no reason why mutt shouldn't be able to remove it. It would be nice if it could. }}} {{{ Furthermore, it would be nice if mutt could just remove all traces of the signature. I have one client who always attached s/mime signatures *and* certificates to each message, and the two files are 70k in size. Since we correspond quite a bit over email, the mailbox is growing at immense speeds. }}}" antonio@… 3260 mutt: please add command to verify a signed message in the index or pager mutt enhancement mutt-dev new 2009-06-13T03:33:00-07:00 2009-06-13T03:33:00-07:00 "Forwarding from http://bugs.debian.org/456212 {{{ I would like to be able to invoke a command to verify the signature of the current message in the index or pager. I know it's possible to do this with a macro that temporarily resets crypt_verify_sig to yes, redisplays the message, and then sets it back, but that's an ugly hack. }}}" antonio@… 3261 mutt should open attachment as read-only file for external viewer mutt enhancement mutt-dev new 2009-06-13T03:36:45-07:00 2010-04-02T09:37:19-07:00 "Forwarding from http://bugs.debian.org/528233 {{{ Hi, I have encountered a little bit awkward behavior when mutt opens attachment in external viewer (according to mailcap). The problem is caused by mutt creating read-write temp file for the attachment which can be misinterpreted by viewer to enable editing as well. I do understand that viewer is not supposed to enable editing, but this is happening. Just as one example consider OpenOffice and doc/odt attachment. I ended up with lost changes (2h of work) because I thought that mutt would keep the file if it had been changed after opening. If the tmp file was read-only from the beginning then even editor wouldn't allow me to edit it. I have hacked my use case by the following simple patch: --- mutt-1.5.18.orig/attach.c 2009-05-11 17:22:38.000000000 +0200 +++ mutt-1.5.18/attach.c 2009-05-11 17:24:24.000000000 +0200 @@ -494,6 +494,11 @@ int mutt_view_attachment (FILE *fp, BODY goto return_error; } + /* chmod tmp file to read-only because we don't want to enable + * viewers which are editors as well to change the content which + * will be thrown away after we close it. + */ + chmod(tempfile, 0400); use_pipe = rfc1524_expand_command (a, tempfile, type, command, sizeof (command)); use_pager = entry->copiousoutput; I don't consider it to be the real fix, but maybe it can help with resolution. Thanks in advance. }}} " antonio@… 3285 [patch] Issues with smime encrypted emails from thunderbird crypto 1.5.19 enhancement mutt-dev new 2009-06-29T16:56:52-07:00 2009-06-30T04:12:56-07:00 "I noticed that I had some problems decrypting emails that I received from people sending smime encrypted emails using thunderbird 2.0.0.19 and 2.0.0.21. I do not know if this is an issue with other versions, but I would suspect there would be. Digging around, it looks like Thunderbird wasn't identify the email as encrypted so it was failing. Here is the Content fields that Thunderbird generated in the email: Content-Language: en-US Content-Type: application/x-pkcs7-mime; name=""smime.p7m"" Content-Disposition: attachment; filename=""smime.p7m"" Content-Transfer-Encoding: base64 I was able to successfully decrypt email sent from mutt that contained the following: Content-Type: application/x-pkcs7-mime; smime-type=enveloped-data; name=""smime.p7m"" Content-Disposition: attachment; filename=""smime.p7m"" Or AppleMail: Content-Type: application/pkcs7-mime; name=""smime.p7m""; smime-type=enveloped-data Content-Disposition: attachment; filename=""smime.p7m"" Content-Transfer-Encoding: base64 To me, the problem really seems to be with thunderbird because it does not identify as enveloped-data, like the other clients do, but reading the mutt source code, it looks like there is some code to to work around Netscape 4.7, so I've done a similiar thing for thunderbird. The attached patch works to resolve the issue that I and others at my site with encrypted email from thunderbird. I tested the patch with 1.5.19 and mutt-20090629.tar.gz" dschan 3291 "~C should support searching BCC as well as ""CC"" and ""To""" mutt enhancement mutt-dev new 2009-07-06T16:17:11-07:00 2010-02-08T11:03:14-08:00 "I think it would be useful if the '~C' simple pattern searched the 'Bcc:' header as well. Of course, in most cases, messages won't have a Bcc header at all, but when searching one's sent messages, it would be a very useful feature to have (in fact, I remembered / assumed mutt already worked this way, but it seems as if it doesn't)." william 3294 mark a mailbox/maildir as read from the directory listing mutt 1.5.20 enhancement mutt-dev new 2009-07-14T11:05:40-07:00 2009-07-14T11:05:40-07:00 "Forwarding from http://bugs.debian.org/535502 {{{ Hi, it would be useful (at least for me) to mark a maildir/mbox as read (binding that to N for example) from the directory view (i.e. after you press c ?) basic use case: I know a maildir/mbox does contain only uninteresting new messages }}} Cheers Antonio" antonio@… 3309 allow *configurable* $stuff_all_quoted or similar option for quoting flowed text mutt enhancement mutt-dev new 2009-07-29T11:16:59-07:00 2009-07-29T11:18:12-07:00 "See comments in #3001 I would like to see an option to support quoting a message with the extra space, rather than just displaying it this way. There was an old patch (stuff_all_quoted) which did this, though I don't know if it will play nice with the new code for displaying / quoting flowed text. Currently, even if the body of a flowed message looks like this when viewing in the editor: {{{ >> blahblah blah blah blah blah blah blah blah > > blargh asdfb basdfadsf > here is some text }}} mutt will quote it like: {{{ > >>blahblah blah blah blah blah blah blah blah > > > >blargh asdfb basdfadsf > > > > here is some text }}} At least for the stuff that mutt can tell for sure *is* quoted material (based on the message being format-flowed and the quote markers being formatted properly), I think it makes sense to quote this more neatly and at least add a space to the outer edge, so that the previous example would become: {{{ > >> blahblah blah blah blah blah blah blah blah > > > > blargh asdfb basdfadsf > > > > here is some text }}} In my reading of 2346 (which may be flawed), I think that should be perfectly Ok, and that (assuming the flowed message is formatted correctly), it should be possible for mutt to know which text is quoted and which text isn't. I'll attach Gary's patch to this." william 3348 "pgp ""sign as"" display" user interface 1.4 enhancement mutt-dev new 2009-10-29T09:53:41-07:00 2009-10-29T09:53:41-07:00 "Please consider allowing a configurable(?) display for the ""sign as"" value when sending an email. Neither """" nor some key id are terribly informative. It would be nice to see (for example) {{{ From: Some Person ... PGP: Sign, Encrypt sign as: (example@example.com) }}} i.e. the id of the key that will be used, and something meaningful to read for the human being using mutt. Things get very confusing very quickly when one has multiple keys, when the only indication on screen is a key id." gdj 3349 user configuration of default subject string when replying to emails without subjects mutt 1.5.21 enhancement mutt-dev new 2009-11-02T09:17:24-08:00 2013-01-09T05:57:52-08:00 "mutt uses the subject ""Re: your mail"" as the subject of emails composed in reply to emails without subjects. To me this comes across as a little passive aggressive, and I edit it every time to something like ""Re: (no subject)"". And of course it is a hard-coded English string, which will make no sense to a non-English speaking recipient of email from a mutt user. This string should therefoure be configurable by the user in their muttrc (i.e. without editing send.c and rebuilding mutt). " mikewilliams 3354 Please support downloading fewer headers via IMAP mutt enhancement mutt-dev new 2009-11-20T21:22:36-08:00 2009-12-07T23:18:27-08:00 "mutt currently downloads a fixed set of headers via IMAP, plus any additional headers specified in the imap_headers configuration variable. However, the fixed set of headers includes several that seem potentially unnecessary, and reducing the set of downloaded headers would improve performance with large folders. mutt currently downloads these headers: DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES LIST-POST X-LABEL Obviously mutt needs Date, From, Subject, To, and Cc in order to display mails properly. (In theory mutt doesn't need To and Cc, if not displaying some indication of how you received a mail, but I don't want to argue for that here.) Similarly, mutt needs Message-Id, References, and In-Reply-To to thread messages properly. On the other hand, X-Label doesn't need downloading unless a user wants to use labels themselves, and mutt doesn't support labels by default, so it seems reasonable to allow omitting it or even to do so by default. mutt doesn't need List-Post and Reply-To until replying to a mail, and it needs the entire message for quoting at that point anyway. Content-Type and Content-Description relate to MIME, and mutt shouldn't need those until it goes to decode the mail, so it seems unnecessary to download them in advance. And finally, Lines looks like a deprecated field, used for news only, and standards specifically say that user agents should ignore it; it doesn't seem useful to download at all." josh 3384 No $index_format sequence for recipients address mutt enhancement mutt-dev new 2010-02-19T01:45:35-08:00 2010-02-19T01:45:35-08:00 "I just tried to build a new index_format and found out, that there is no sequence like %f for the To: header. I would have liked a %t that outputs the recipients name+address just as %f does (and without the ""To"" in front of it) " mlo 3396 Spam command is unpredictable mutt 1.5.20 enhancement mutt-dev new 2010-03-29T13:42:42-07:00 2010-03-29T13:42:42-07:00 "It took me a while to find this one out. I have a pretty complex spam header matching setup, since I want nice aligned output (and thus have different matching rules for negative spamscores, spamscores with > 1 digit and rules without any spamscore at all), but I can't do that reliably currently. Here goes. The manual says ""If the $spam_separator variable is unset, then each spam pattern match supersedes the previous one. Instead of getting joined format strings, you'll get only the last one to match."" I've always interpreted this as ""You'll get the result of the last pattern that matches any header in the message"". However, after reading the source, I've understood this means ""You'll get the result of the last _header_ in the message that matches any pattern"". Furthermore, if multiple patterns match a single header, you'll get the first one to match, not the last one. In other words, this means the order of headers in the messages greatly influences the match result and you can't affect that by reordering the spam commands. Thinking about this, it seems that, given a header occurs twice in a message, it's better to use the last one that matches. This ensures that you always use the email scanner that is ""closest"" to you, e.g., your own scanner overrides the one of your ISP. However, when you apply this to two different headers, stuff gets confusing. So the current situation is: Use the last header that matches a pattern and use the first pattern in case there are multiple patterns that match that last header. I would propose the following: Use the first pattern that matches any header. If it matches multiple headers, use the last header that matches. This will change nothing in the common case of a single pattern. When multiple patterns matching _different_ headers are used, one can now prioritize them using the order of the patterns. For multiple patterns matching the same header nothing will change either, they will still use the first pattern that matches the last header. This is only in the case spam_separator is unset. If spam_separator is set, I would leave the behaviour completely unchanged. It might make sense to change the ordering of matches, so it is more obvious to say ""If spam_separator is unset, it simply takes the last (or first) part of the value that you get when spam_separator is set"". However, this would require significantly changing the implementation by keeping all the (matching) header lines in memory, whereas the current implementation just processes them line by line. Note that the implementation needs only minor changes for my proposal in the spam_separator is unset case: In addition to keeping the matching spam tag, you also keep track of the pattern (index) that it resulted from. Now, when you find a new match in a subsequent header, only overwrite your previous match when the pattern index of the match is lower than the pattern index of the previous match. AFAICS, this should implement above proposal with minimal changes. If you think this is a good idea, let me know and I'll prepare a patch for this. If not, please add some clarification about how it works now and close this ticket :-)" matthijs 3404 Search in address book is case sensitive mutt 1.5.20 enhancement mutt-dev new 2010-04-12T14:45:40-07:00 2010-04-12T14:45:40-07:00 "Hello, could you please make the search in the address book (aliases in muttrc) case insensitive? A new config option would be fine, too. Detailed report: Steps to reproduce: * Create new alias: Alias as: John_Doe Address: john.doe@example.net Personal name: John Doe [John_Doe = John Doe ] Accept? ([yes]/no): yes Save to file: /home/wulf/.muttrc Alias added. * write an E-Mail To: john Problem: And there is the problem; the whole address book / all aliases are shown, because I typed `john' with a lower case 'j', but the alias in muttrc starts with an upper case 'J'. cheers, Joern Heissler" Wulf 3425 tag-pattern in Attachments view mutt 1.5.20 enhancement mutt-dev new 2010-06-29T02:02:56-07:00 2012-05-20T22:03:32-07:00 I really miss the tag-pattern function in the Attachments view. When I got a mail with many attachments, it would be convenient to select them (eg.: for saving) by a pattern. daniell 3437 separate sorting settings for folder, mailbox, and IMAP browsers browser enhancement mutt-dev new 2010-08-04T03:12:23-07:00 2010-08-04T03:12:23-07:00 "Currently mutt only supports only a single sorting option for the folder, mailbox, and IMAP browsers, I would find it useful to have three separate sort settings for each of them. Specifically, I'd like to be able to have filenames in the folder browser sorted alphabetically while leaving the mailboxes in the mailbox browser unsorted, that is in the order specified in the configuration file which is also the order used by the change-folder function to traverse those mailboxes with new mail. " gber 3444 provide an option to disable all colors display 1.5.20 enhancement mutt-dev new 2010-08-11T05:30:46-07:00 2010-08-11T05:30:46-07:00 "Hi, I would like to have an option to disable all colors from mutt and use the standard one, I can work around this by setting the terminal to vt100 or something else that does not support colors or by writing a very long conf file to disable all colors on all parts of mutt. It would be great to have an option to disable all colors with a single line change on .muttrc Cheers Antonio" antonio@… 3454 New mail notification via receive-hook mutt enhancement mutt-dev new 2010-09-22T01:39:23-07:00 2010-11-22T07:21:28-08:00 "I wrote a patch that enables one to execute arbitrary system command upon new mail reception. The command to execute is configurable. I have tested it against 1.5.20 and 1.5.21. Example of configuration in .muttrc: receive-hook . ""system notify-send 'New mail'""" mehturt 3461 Mailboxes list not remembering state mutt 1.5.20 enhancement mutt-dev new 2010-10-09T05:07:40-07:00 2010-10-10T10:46:26-07:00 "I used to use 1.5.18 on Debian and am running vanilla 1.5.20 now. On the Debian 1.5.18 version, pressing ""y"" in the index to see the list of mailboxes had the following effect: If the currently open folder (the one where I pressed y) is one of the mailboxes, then this mailbox would be the one initially having the indicator in the list of mailboxes. Otherwise, it would always be the first mailbox that has the indicator. Now, no matter which folder I'm accessing the mailbox list from, it is always the first mailbox that has the indicator immediately after displaying the mailbox list. That is, mutt does not recognize that the currently open folder is one of the mailboxes." nzeh 3467 Current default $folder folder is ignored after connecting to remote folder mutt 1.5.20 enhancement mutt-dev new 2010-10-31T02:51:14-07:00 2012-07-07T06:26:12-07:00 "Reproducible: Always. With default bindings: set folder=""imaps://"" c? q set folder="""" c? " ManDay 3520 TLS OpenPGP mutt enhancement mutt-dev new 2011-05-27T11:21:01-07:00 2011-05-27T11:21:01-07:00 "Currently mutt only support X.509 though gnutls also support OpenPGP (RFC 6091). I suggest to add OpenPGP as an alternative to X.509." ott 3565 Use last used folder as default suggestion when using save-message mutt enhancement mutt-dev new 2012-02-09T13:55:18-08:00 2012-02-09T13:55:18-08:00 "See $Summary. At least in *my* case I can say that using the last folder used for save-message was in almost all cases more useful than the current one. I guess others may think the same." idl0r 3573 Run Script When New Mail Arrives mutt enhancement dgc assigned 2012-04-19T08:33:52-07:00 2012-04-19T08:46:02-07:00 "It would be very useful to be able to run a script when new mail arrives. One use for this is to play a sound when you have new mail. I know screen or tmux can be set to beep or flash when something happens in another window, but a lot of blind users would not be able to notice the flash, and the beep thing does not always work, like on my computer for example. I had thought about just asking for the ability to play sound, but being able to execute a script has so much more potential and would solve more than just one kind of problem." stormdragon2976 3576 Makes new connection to the SMTP server for every mail, even when sending several in one action SMTP enhancement brendan new 2012-04-22T07:51:04-07:00 2012-12-30T19:58:26-08:00 "Forwarding from http://bugs.debian.org/633993 : {{{ I selected an entire thread, and used ;b to bounce it to someone. mutt made a new connection to the SMTP server for each mail it bounced, incurring the full latency of a connection to my SMTP server each time. mutt should have made a single connection to the SMTP server to send all the mails. - Josh Triplett }}}" Y_Plentyn 3577 send-hook should not be executed if the mail is not going to be sent mutt enhancement mutt-dev new 2012-04-22T08:21:30-07:00 2012-04-23T04:24:42-07:00 "Forwarding from http://bugs.debian.org/641457 : {{{ I have a hook like this: send-hook '~s keyword' ""push 'Thank you'"" The idea is that I want the subject to be automatically modified if it contains a specific keyword. This works well when you actually reply to the mail (or write a new mail). But if you exit the text editor without having done any change, the confirmation screen is not displayed but the ""push"" is still executed and the various letters end up executing multiple commands that should not have been executed because they were intended for the ""Compose menu"" and not the ""Index menu"". So the send-hook/send2-hook should really only be executed if the mail is going to be sent... And ideally if a reply is cancelled, a push recorded in a reply-hook should also be cancelled. Because my first try was to use a reply-hook for my need. :-) Cheers, }}}" Y_Plentyn 3591 ESS: Security Labels (RFC2634 - 3) mutt enhancement mutt-dev new 2012-07-31T05:28:22-07:00 2012-07-31T07:35:59-07:00 "This feature is used to add security information in a message which will be used to handle authorizations and access rights. It implements the security service ""security labels"" defined in RFC 2634 Enhanced Security Services for S/MIME http://tools.ietf.org/html/rfc2634 . A security label is a set of security information regarding the sensitivity of the content that is protected by S/MIME encapsulation. A security label is composed of: Security Policy Identifier Security Classification (optional) Privacy Mark (optional) Security Categories (optional) Additional resources: Technical Documentation RFC 2634 - section 3 - Enhanced Security Services for S/MIME RFC 3114 - Implementing Company Classification Policy with the S/MIME Security Label http://tools.ietf.org/html/rfc3114 RFC 4134 - Examples of S/MIME Messages http://tools.ietf.org/html/rfc4134 Screencast http://milimail.adullact.net/media/Security_Labels_-_Usage.swf Mozilla bug #598282 https://bugzilla.mozilla.org/show_bug.cgi?id=598282" akochkov 3593 Support for custom UTF-8 symbols in varios places mutt enhancement mutt-dev new 2012-07-31T05:52:52-07:00 2012-07-31T07:39:14-07:00 "To use something like Powerline plugin for Vim https://github.com/Lokaltog/vim-powerline/ It will need patched fonts, though, but can be useful for various marks, attachments show, status line, menus, etc." akochkov 3594 Content-Disposition fails with Android 2.* MUA mutt 1.5.21 enhancement me accepted 2012-09-26T11:44:37-07:00 2012-12-01T15:12:26-08:00 "When trying to read mails composed with Mutt, users of Android 2.* default MUA will see nothing but an ""Unknown.txt"" attachment, which is indeed the body of the mail. The content is still readable, but it is confusing for Android users (and not very convenient). The issue comes from Android misbehaving with the Content-Disposition line in the header of the mail, whatever the value is. Mutt is one of the few MUA that automatically adds this line to every mail header. I quickly patched mutt_write_mime_header@sendmail.c to remove the line and it works. As far as I know, there is no way to toggle off this line directly from muttrc. Would be nice to add this feature." Ambrevar 3622 feature: auto-subscribe to lists based on List-Post header [patch] mutt 1.5.21 enhancement mutt-dev new 2013-01-09T06:14:48-08:00 2013-01-09T06:14:48-08:00 "When a mail has a ""List-Post"" header, it's probably a list, which the user is subscribed to. We discussed this on mutt-users back in 2010: http://marc.info/?l=mutt-users&m=127076105423565 Michael Elkins wrote a patch for it: > Attached is a patch which implement an auto-subscribe feature. When you load a mailbox, Mutt will parse the List-Post header field and add it to the 'subscribe' list automatically, unless it matches something on the 'unlists' or 'unsubscribe' list. Please include this feature in the source." ilf 3631 Support 256 colors output from autoview in the pager display 1.5.21 enhancement mutt-dev new 2013-01-30T04:11:01-08:00 2013-01-30T04:11:01-08:00 "The pager currently supports the display of traditional 16-color ANSI output from autoview but does not support xterm-256color codes, neither with ncurses nor slang. This was previously shortly discussed on mutt-users: http://marc.info/?l=mutt-users&m=135869598705446&w=2" ptaff 3107 Traditional PGP checking isn't robust enough crypto 1.5.18 1.6 defect mutt-dev new 2008-08-20T08:58:32-07:00 2009-04-19T06:53:53-07:00 "When viewing messages with $pgp_auto_decode set or using check-traditional-pgp, messages like http://marc.info/?l=mutt-users&m=121916523318263&w=2 look completely broken in mutt: {{{ -----BEGIN PGP SIGNATURE----- [-- BEGIN PGP SIGNED MESSAGE --] [-- END PGP SIGNED MESSAGE --] }}} ...which may be quite misleading. Sure, it's and an edge-case with plain text that has parts looking like PGP, but displaying an empty message is wrong in this case." pdmef 3283 browser excludes current folder in check-new browser 1.5.20 1.6 defect pdmef new 2009-06-29T08:21:58-07:00 2009-06-30T07:28:51-07:00 `` eventually calls `mutt_buffy_check(0)` to update the new mail flags, but the latter excludes the current folder. Thus, if you fire up the browser from some folder, new mail isn't reported for it. pdmef 3554 mark_old fails silently if IMAP server doesn't support custom PERMANENTFLAGS IMAP 1.5.21 1.6 defect brendan new 2011-12-09T09:31:59-08:00 2011-12-09T09:31:59-08:00 Mutt relies on being able to add an 'Old' flag to mark IMAP messages as old. If the server doesn't support the * PERMANENTFLAG, mutt simply gives up. It should have a fallback strategy, perhaps using hcache or even trying to use RECENT. brendan 3580 mutt -H $draft ignores recipient arguments on CLI mutt 1.5.21 1.6 defect mutt-dev new 2012-05-17T15:16:58-07:00 2012-05-17T15:16:58-07:00 "When using the -H option to compose using a draft message, mutt ignores any recipients specified at the end of the CLI arguments in favour of the contents of the To: header in the supplied draft. IOW, the subsequent interactive prompt for recipients will be populated with the contents of the To: header. Furthermore, if the To: header is empty or non-existent, the subsequent interactive prompt will not be populated with anything. I suggest that a better behaviour would be to merge the contents of the draft's To: header (if any) with the recipients provided at the end of the CLI command (if any), and use that union to populate the interactive prompt." adam.spiers 3589 prompts for PGP / SMIME passphrase when searching mutt 1.6 defect mutt-dev new 2012-07-23T14:33:11-07:00 2012-09-20T12:55:56-07:00 "If I try to limit for messages (via limit-command) or otherwise search through a mailbox, Mutt seems to require me to enter my passphrase over and over, even within a short span of time (I am not using gpg-agent, but mutt usually will cache the agent passphrase within a short period of time -- for example, normally, if I've entered my passphrase, I can view other encrypted messages that are encrypted to a key I've used very recently, or view the same message over and over again). There also doesn't appear to be an option to not search encrypted messages at all, and hitting ^G won't abort the entire search, just the current one, so once you've tried to search a large mailbox with a lot of encrypted messages, there's no easy way to break out of the cycle without killing mutt. This is not the end of the world, but I'm wondering if there's some more graceful approach to this situation for before 1.6. {{{ Mutt 1.5.21 (2010-09-15) Copyright (C) 1996-2009 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: Darwin 11.4.0 (x86_64) ncurses: ncurses 5.7.20081102 (compiled with 5.5) libiconv: 1.11 hcache backend: Berkeley DB 4.8.30: (April 9, 2010) Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP +USE_IMAP -USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -USE_GSS +HAVE_GETADDRINFO -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS +LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. patch-1.5.5.1.gj.stuff_all_quoted.2 patch-1.5.13.cd.trash_folder.3.4 }}} " william 3590 Apparently valid email address not accepted in mutt > 1.5.21 mutt 1.6 defect me accepted 2012-07-23T14:42:35-07:00 2012-12-18T19:09:55-08:00 "I noticed a weird quirk recently between two different mutt installs (both fairly recent) that I have. Sorry for the noise if this is from something odd I did. If I enter in an address which is technically RFC compliant as quoted, though uncommon, such as: ""bogus@example.com""@example.com mutt 1.5.20 from 6/2009 allows me to put that in an address field (like ""To"") when composing a new message. Mutt 1.5.21, from 9/2010 silently removes the address from that field if editing the headers in the editor (or, if composing a new message, doesn't open the editor, again, without error). I don't think MTA settings are involved, since it removes the address before actually attempting to send anything. Is this the expected behavior? I don't think any of the patches I've applied should affect this particular type of behavior, and I'm not sure how ""smart"" mutt should be in regards to address standards compliance. Accepts the address: {{{ % mutt -v Mutt 1.5.20 (2009-06-14) Copyright (C) 1996-2009 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: OpenBSD 4.0 (sparc64) ncurses: ncurses 5.2.20010224 (compiled with 5.2) [...] patch-1.5.13.cd.trash_folder.3.4 }}} Doesn't: {{{ % mutt -v Mutt 1.5.21 (2010-09-15) Copyright (C) 1996-2009 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: Darwin 11.3.0 (x86_64) ncurses: ncurses 5.7.20081102 (compiled with 5.5) [...] patch-1.5.5.1.gj.stuff_all_quoted.2 patch-1.5.13.cd.trash_folder.3.4 }}}" william 3639 Handling of inconsistent smime signed messages. crypto 1.5.21 1.6 defect mutt-dev new 2013-03-05T10:54:38-08:00 2013-03-05T10:54:38-08:00 "Some email clients generate s/mime multipart/signed emails with inconsistent Content-Type headers. The Content-Type of such messages have a protocol of ""application/x-pkcs7-signature"" whereas the Content-type of the individual smime.p7s part is listed as ""application/pkcs7-signature"" (without the ""x-""). This discrepancy does not affect the validity of the signature which can be manually verified with openssl. However, mutt wont even attempt verification of the signature because the mismatched Content-Type of the message and the smime.p7s part causes an ""Inconsistent multipart/signed structure!"" error before verification can occur. This issue is present in both 1.5.21 and tip. In this situation, it is more important to determine the validity of the email's signature rather than reject it out-of-hand due to an idiosyncrasy of the sender's client. I've attached a patch that should do just that without sacrificing too much in the way of consistency checking." chris 681 rc of mutt_display_message differs between builtin and external pager display 1.3.19i 2.0 defect mutt-dev new 2001-07-05T18:35:14-07:00 2008-06-25T23:10:14-07:00 "for example, pressing after completion (last page) of builtin pager makes it skip to the next undeleted message. but when I use external pager, pressing at `Commands:' prompt brings it to the last of the index. try 'R' key, at the `Commands:' prompt, and you'll know what I mean. suggested solution: move the codes after pager.c:1668 should be moved into another function (with heck a lot of params...), and it should be called just before the return of mutt_display_message(), translating(?) the rc accordingly." john simon 969 Can't clear the 'N' (unseen) flag on read-only IMAP folders IMAP 1.3.25i 2.0 defect brendan new 2002-01-12T12:47:40-08:00 2010-01-24T11:01:52-08:00 "When reading read-only IMAP folders, I used to be able (1.2.5i) to clear the new flag by reading the message. When updating to 1.3.25i, the 'N' flag just stays and is still there the next time around. Going back to 1.2.5i, I notice that the 'toggle-new' function didn't work there on read-only imap folders, even though the flag got cleared by reading the message. Looking at RFC 2060, the client is allowed to modify the Seen flag if the server returns PERMANENTFLAGS on a SELECT: Here's a read-write folder: {{{ . select inbox * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] * 210 EXISTS * 0 RECENT * OK [UIDVALIDITY 914040081] * OK [UIDNEXT 9885] . OK [READ-WRITE] Completed }}} and here's a read-only one: {{{ . select fulcrum.internal.ms * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) * OK [PERMANENTFLAGS (\Seen)] * 7874 EXISTS * 0 RECENT * OK [UNSEEN 7872] * OK [UIDVALIDITY 914048337] * OK [UIDNEXT 7946] . OK [READ-ONLY] Completed }}} The PERMANENTFLAGS shows which flags out of those listed in FLAGS the client is allowed to change permanently. ""If the client can not change the permanent state of one or more of the flags listed in the FLAGS untagged response, the server SHOULD send a PERMANENTFLAGS response code in an OK untagged response, listing the flags that the client can change permanently."" Hope this helps.... rik. " Rik Harris 1431 misleading --disable-external-dotlock functionality/ documentation vs. naming/ intuition build 1.5.3i 2.0 defect mutt-dev reopened 2002-12-23T16:16:32-08:00 2009-06-30T07:20:51-07:00 "I configured mutt (same problem in 1.4 and 1.5.3) with the following command: `./configure --enable-pop --enable-imap --disable-external-dotlock --with-ssl` but despite the --disable-external-dotlock configure checks /var/mail ($mutt_cv_mailpath), finds that it is writable by group mail, and then configures to install mutt_dotlock setgid mail. However, when using mutt via imap the permissions on $mutt_cv_mailpath are totally irrelevant, thus if --disable-external-dotlock is specified no setgid mail mutt_dotlock program should be installed no matter what the permissions on $mutt_cv_mailpath are. The following patch to the configure script implements such a behaviour. {{{ --- mutt-1.5.3/configure.nosetgid Tue Dec 17 02:35:56 2002 +++ mutt-1.5.3/configure Mon Dec 23 15:44:44 2002 @@ -4570,6 +4570,12 @@ #define MAILPATH ""$mutt_cv_mailpath"" EOF +# Check whether --enable-external_dotlock or --disable-external_dotlock was given. +if test ""${enable_external_dotlock+set}"" = set; then + enableval=""$enable_external_dotlock"" + mutt_cv_external_dotlock=""$enableval"" +fi + echo $ac_n ""checking if $mutt_cv_mailpath is world writable""""... $ac_c"" 1>&6 echo ""configure:4576: checking if $mutt_cv_mailpath is world writable"" >&5 @@ -4618,6 +4624,7 @@ else + if test $mutt_cv_external_dotlock = yes; then echo $ac_n ""checking if $mutt_cv_mailpath is group writable""""... $ac_c"" 1>&6 echo ""configure:4623: checking if $mutt_cv_mailpath is group writable"" >&5 if eval ""test \""`echo '$''{'mutt_cv_groupwrite'+set}'`\"" = set""; then @@ -4668,13 +4675,8 @@ mutt_cv_setgid=yes fi + fi fi -fi - -# Check whether --enable-external_dotlock or --disable-external_dotlock was given. -if test ""${enable_external_dotlock+set}"" = set; then - enableval=""$enable_external_dotlock"" - mutt_cv_external_dotlock=""$enableval"" fi }}}" siegert@… 2807 pager.c remembers TopLine when it shouldn't display 1.5.14 2.0 defect mutt-dev new 2007-02-27T22:22:24-08:00 2009-06-30T07:26:12-07:00 "{{{ Since this change (http://mutt.kublai.com/hg/cvs/rev/b894fd4c9032) on Sep 08 2005, the builtin pager keeps its position even on OP_MAIN_NEXT_UNDELETED. So you cannot re-read the last message from the top of it with . (See How-To-Repeat) This must be a side-effect of http://bugs.mutt.org/1210 >How-To-Repeat: 1. :unset pager_stop 2. to a folder which has a long (more than a screen-length) message as the last entry. 3. Hit on the last message. 4. Repeat until the message finishes. 5. You will be in index mode (because the message is the last entry in the folder). 6. Hit again. You will see the _bottom_ of the message, not the top. >Fix: Forget TopLine when (with $pager_stop) causes OP_MAIN_NEXT_UNDELETED. (though Brendan called it ""a bogus detection"") }}}" tamo@… 2926 unnecessary scroll in pager display 1.5.16 2.0 defect mutt-dev new 2007-06-29T01:48:07-07:00 2009-01-29T15:33:10-08:00 "When viewing a message with , Mutt sometimes scroll to the bottom unnecessarily (instead of going directly to the bottom); this can make very slow with huge messages via a ssh connection. Steps to reproduce the bug:[[BR]] 1. Open a mailbox that has a single message.[[BR]] 2. View the message with .[[BR]] 3. Go to the bottom of the message with .[[BR]] 4. Delete the message with .[[BR]] 5. View the message with . If you can't see the bug because the terminal is too fast, you can see the problem by logging the tty session with ''script'' or ''ttyrec''." vinc17 2960 Terminal resize problem after editor is called display 1.5.16 2.0 defect mutt-dev new 2007-09-19T01:36:15-07:00 2009-04-02T08:31:09-07:00 "Mutt (ncurses?) doesn't seem to properly catch up upon terminal resize when the editor is involved. I have two scenarios where I can exactly reproduce it on OS X (xterm in Apple's X11 and Terminal.app) and FreeBSD (xorg's xterm). I use mutt hg tip with ncursesw 5.6 in all 3 cases. Scenario 1: * In the index, edit a message, quit without saving. * Enlarge the screen just a little bit. * Repeat step 1). * Now the index is drawn as if the terminal wasn't resized in step 2. Scenario 2: * From the index, start composing a message, edit message in the editor. * Leave the compose menu without postponing and sending. * Enlarge the terminal just a little bit. * Repeat step 1) * Now the compose menu is drawn as if the terminal wasn't resized in step 3). * When comming back to the index, it's also drawn as if no resize happened. In both cases, when resizing the terminal from the index, mutt recognizes the new size and everything seems to work fine again. However, once the editor was invoked either way, things are broken afterwards again. The only way to make mutt usable again is to exit it and restart. This is especially true when the terminal is made smaller since it completely messes up everything. I've put some debug printing in and it turns out that LINES and COLS are really the narrower old sizes afterwards, so mutt does everything right with wrong values reported by curses. Especially the fact that mutt gets the original size (just when mutt was started) over and over again if endwin() is called in between makes we wonder whether it's curses having a problem to catch up upon resizing or if it's mutt. But I'm by no means a curses expert." pdmef 3024 to_chars not utf-8 capable charset 1.5.18 2.0 defect mutt-dev new 2008-02-01T04:41:21-08:00 2010-11-21T12:29:05-08:00 "putting multi-byte chars into to_chars produces garbage, as addressing is done by byte index. without having tested it, i assume status_chars suffers the same problem. " ossi 3098 $SHELL differs from $0 in subshell mutt 2.0 defect mutt-dev new 2008-08-04T16:39:02-07:00 2008-08-27T09:32:05-07:00 "I set the subshell in the .muttrc[[BR]] `set shell=""/usr/bin/zsh""`[[BR]] mainly to have the .zsh_env sourced, which adjusts variables like $DISPLAY in reatached screen sessions. Unfortunately this doesn't work. in mutt[[BR]] `echo $SHELL; echo $0`[[BR]] reports that SHELL is set to zsh, but nevertheless a sh is executed. So what i would have expected is that $0 was also a zsh." schertz123456 3183 """Error opening mailbox"" (and death) after finishing reading in all headers." mutt 1.5.19 2.0 defect brendan accepted 2009-02-05T05:47:51-08:00 2011-06-25T21:35:54-07:00 "I searched your bug DB as best I could figure out how, but I couldn't find anything on this. On Tuesday afternoon the folks in corporate IT obviously did something to the exchange server on which my mailbox resides which mutt really didn't like. Unfortunately, I don't know what they did, and getting information from them will likely be nearly impossible. I was kicked out of mutt at the time, and I haven't been able to connect since. It looks like mutt gets through reading in all the headers, and after it reads in the last one (as far as I can tell by watching the numbers climb while loading), it just dies with the dreaded ""error opening mailbox"". It happens every time. I'm REALLY motivated to get this one fixed. I do *NOT* want to have to put up with that LookOut! crud that they expect everyone to use. I'll do pretty much whatever you need to help. I'll (try to) include d2 level a muttdebug file for you." tmg 467 "Mutt doesn't check mailboxes automatically while it's in ""browser"" mode" browser 1.5.18 2.0 enhancement mutt-dev new 2001-02-12T21:50:05-08:00 2009-06-30T07:29:10-07:00 "{{{ Package: mutt Version: 1.2.5i Severity: wishlist -- Please type your report below this line Mutt doesn't check the mailboxes automatically when it's in browser mode. It is able to check for new mail when I force a mail check, but nothing more. I set up the mail_check variable, but seems that mutt ignores that directive... -- Mutt Version Information Mutt 1.2.5i (2000-07-28) Copyright (C) 1996-2000 Michael R. Elkins e altri. Mutt non ha ALCUNA GARANZIA; usare `mutt -vv' per i dettagli. Mutt è software libero e sei invitato a ridistribuirlo sotto certe condizioni; scrivere `mutt -vv' per i dettagli. System: Linux 2.4.1-ac4 [using ncurses 4.0] Opzioni di compilazione: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_GSS -USE_SSL +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/spool/mail"" SHAREDIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" ISPELL=""/usr/bin/ispell"" Per contattare gli sviluppatori scrivi a . Per segnalare un bug usa il programma muttbug. --- Begin /home/rigel/.muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" set hdrs my_hdr Reply-To: a.gatti@inet.it my_hdr X-Operating-System: Linux 2.4.1-ac4 on waveform.inet.it my_hdr X-King: Elvis has left the building set include set spoolfile=$HOME/Mail/inbox set hostname=waveform.inet.it set use_8bitmime set alias_file=""~/.mutt_aliases"" source ~/.mutt_aliases set attribution=""On %d, %n wrote:"" set autoedit=no set auto_tag=yes set beep=no set beep_new=yes set edit_headers=yes set editor=""vim"" set folder=""$HOME/Mail"" set from=""a.gatti@inet.it"" set header=yes set hostname=""inet.it"" set in_reply_to=""%i; from %a on %{!%a, %b %d, %Y at %I:%M:%S%p %Z}"" set mail_check=5 set mask="".*"" set mbox_type=mbox set move=yes set pager_stop=yes set postponed=+outbox set query_command=""abook --mutt-query '%s'"" set realname=""Alessandro Gatti"" set record=+sent set save_empty=yes set save_name=yes set signature=""~/.signature"" set sort=threads set spoolfile=""/var/spool/mail/rigel"" set weed=no set bounce_delivered=yes mailboxes =inbox =trivia =inet-control =milug =inet-customer-control =inet-housing =inet-sic =cartasi =private =inet-troubleticket lists trivia milug inet-housing send-hook milug 'set signature=~/.signaturepersonal; my_hdr From: Alessandro Gatti ; my_hdr Reply-To: rigel@inet.it' send-hook ahpook 'set signature=~/.signaturepersonal; my_hdr From: Alessandro Gatti ; my_hdr Reply-To: rigel@inet.it' send-hook trivia 'set signature=~/.signaturepersonal; my_hdr From: Alessandro Gatti ; my_hdr Reply-To: rigel@inet.it' bind index previous-entry bind index next-entry bind pager previous-line bind pager next-line bind pager previous-entry bind pager next-entry bind browser g check-new mono normal none mono indicator reverse mono tree none mono status reverse mono error bold mono message none mono quoted bold mono signature none mono attachment underline mono search reverse mono tilde none mono markers bold mono hdrdefault none mono bold bold mono underline underline mono header bold ""^(from|subject):"" mono body underline ""((ftp|http|https)://|(file|mailto|news):|www\\.) [-a-z0-9_.:]*[a-z0-9](/[^][{} \t\n\r\""<>()]*[^][{} \t\n\r\""<>().,:!])?/?"" mono body underline ""[-a-z_0-9.]+@[-a-z_0-9.]+"" mono body bold ""(^| )\\*[-a-z0-9äöüß*]+\\*[,.?]?[ \n]"" mono body underline ""(^| )_[-a-z0-9äöüß_]+_[,.?]?[ \n]"" color normal brightwhite black color indicator brightcyan blue color tree brightred black color status brightyellow blue color error brightred black color message brightyellow black color signature red black color attachment blue cyan color search brightyellow red color tilde brightmagenta black color markers brightred black color hdrdefault blue black color bold red black color underline green black color quoted cyan black color quoted1 yellow black color quoted2 magenta black color quoted3 red black color quoted4 red black color quoted5 red black color quoted6 red black color quoted7 red black color quoted8 red black color quoted9 red black color header brightyellow black ""^(from|subject):"" color body brightgreen black ""((ftp|http|https)://|(file|mailto|news):|www\\.) [-a-z0-9_.:]*[a-z0-9](/[^][{} \t\n\r\""<>()]*[^][{} \t\n\r\""<>().,:!])?/?"" color body brightred black ""[-a-z_0-9.+]+@[-a-z_0-9.]+"" color body red black ""(^| )\\*[-a-z0-9*]+\\*[,.?]?[ \n]"" color body green black ""(^| )_[-a-z0-9_]+_[,.?]?[ \n]"" color index blue black ~F color index brightgreen black ~N color index magenta black ~T color index cyan black ~D set pgp_autosign=yes set pgp_replysign=yes set pgp_replysignencrypted=yes set pgp_decode_command=""gpg %?p?--passphrase-fd 0? --no-verbose --batch --output - %f"" set pgp_verify_command=""gpg --no-verbose --batch --output - --verify %s %f"" set pgp_decrypt_command=""gpg --passphrase-fd 0 --no-verbose --batch --output - %f"" set pgp_sign_command=""gpg --no-verbose --batch --output - --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a? %f"" set pgp_clearsign_command=""gpg --no-verbose --batch --output - --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f"" set pgp_encrypt_only_command=""pgpewrap gpg -v --batch --output - --encrypt --textmode --armor --always-trust -- -r %r -- %f"" set pgp_encrypt_sign_command=""pgpewrap gpg --passphrase-fd 0 -v --batch --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f"" set pgp_import_command=""gpg --no-verbose --import -v %f"" set pgp_export_command=""gpg --no-verbose --export --armor %r"" set pgp_verify_key_command=""gpg --no-verbose --batch --fingerprint --check-sigs %r"" set pgp_list_pubring_command=""gpg --no-verbose --batch --with-colons --list-keys %r"" set pgp_list_secring_command=""gpg --no-verbose --batch --with-colons --list-secret-keys %r"" set pgp_getkeys_command="""" --- End /home/rigel/.muttrc --- Begin /usr/local/etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" --- End /usr/local/etc/Muttrc >How-To-Repeat: >Fix: }}}" Alessandro Gatti 507 message/partial MIME type not handled as expected MIME 1.3.9i 2.0 enhancement mutt-dev new 2001-03-15T09:42:57-08:00 2008-06-25T23:45:03-07:00 "If I receive multiple mail messages with MIME type message/partial, I expect to be able to read the rebuilt attachment by looking at each part with 'v' and having a mailcap entry: {{{ message/partial; showpartial %s %{id} %{number} %{total} }}} But mutt treats the ""message"" type specially and never looks for a mailcap entry for this subtype. This appears to make it impossible to read such multipart attachments with mutt." Dave Davey 2018 virtual folders wanted mutt 2.0 enhancement mutt-dev new 2005-08-01T08:42:15-07:00 2009-01-02T12:26:51-08:00 "a virtual folder is a message list based on a named filter expression. generally it behaves like a regular mailbox, with some minor restrictions. one particularly interesting feature is combining threading with filtering, so an entire thread is pulled into the vfolder if one message from it is matched." ossi@… 2064 wish: imap operations should be interruptable IMAP CVS HEAD 2.0 enhancement mutt-dev new 2005-09-11T13:06:48-07:00 2012-02-13T02:07:50-08:00 "It would be nice if IMAP operations could be stopped. There are two easy examples where it'd be really nice. First, when downloading a big message, you may change your mind and not want to see the message -- it would be nice to be able to control-C it (like all other mutt operations) to stop. Second, when the network connection goes away (say, I'm running mutt on my laptop, close the lid, go home for the day, and open up the laptop), it'd be nice to be able to tell mutt ""give up now"" rather than having to wait for `$connect_timeout`" kyle-mutt-dev@… 2339 Only retrieve one screenful at a time of messages IMAP 2.0 enhancement mutt-dev new 2006-07-07T12:16:53-07:00 2007-04-07T14:27:19-07:00 When using mutt to access IMAP folders with several thousand messages, it would be nice for an option to behave like current Pine revisions do, grabbing only the most recent screenful-worth of headers, and grabbing headers only as needed (i.e. if the user chooses to change the sort order, etc). hobart@… 2969 new function: lock-tag-prefix mutt 2.0 enhancement mutt-dev new 2007-10-10T23:38:52-07:00 2008-05-17T18:42:57-07:00 "I wanted a way to have a macro that: - when applied with tag-prefix, applies several commands to all tagged messages - when applied without tag-prefix, applies the same commands to the current message So I added two functions to mutt: lock-tag-prefix and unlock-tag-prefix. The idea is that the said macro starts with and ends with . lock-tag-prefix lock the tag-prefix to ""on"", but only if it is in effect. unlock-tag-prefix unlocks it. Please let me know if you apply this patch and require me to write the documentation, I'll try to write something sensible." cypherpunk 2992 Re: wish: enable encrytion to arbitrary number of keys (was: Re: crypto 2.0 enhancement mutt-dev new 2007-11-23T04:53:32-08:00 2008-05-17T19:14:21-07:00 "On Fri, Nov 23, 2007 at 03:34:54AM -0500, Derek Martin wrote: > While I don't really oppose this, it seems to me that the far saner > way to deal with this is for the mailing list software to allow the > subscribing users to upload their public key, and to make the mailing It would make it easier in some cases, but you do lose security - anybody who can somehow get themselves onto the list can read it, and anybody compromising the mailing list host automatically gets to read everything. If the senders do the encryption, that doesn't happen. Whether most people need that level of security is another question, but then again most people don't use encrypted mailing lists at all... :-) " Paul Walker 3031 Handle multiple folders at the same time (via command) mutt 2.0 enhancement mutt-dev new 2008-02-15T07:50:19-08:00 2009-09-26T03:16:26-07:00 "This addresses a complaint/question that comes up every now and then, and would probably provide a lot of side-benefits that we can't even think of at the moment. It would be excellent if mutt could view the contents of several folders at the same time, in an integrated display (i.e. there's not necessarily any visible distinction between messages in one folder and another). If this worked, one could (for example) set limits and search within multiple folders. It MAY even be useful to add another % option to index_format that allows each message to display which folder it's from, and a new sorting option to sort (or sort_aux) by folder. Here's the way I imagine the interface could work (just a suggestion). works as it currently does (namely, it clears the index and rebuilds the index from the contents of the new folder), however we can add a new command: . This command would behave similar to (i.e. the prompt, the cycling through mailboxes, etc.) but instead of clearing the index and rebuilding it with the contents of the new folder, it adds the contents of the new folder to the existing index list, and re-sorts the index to merge the two together. If this could work generically, one could theoretically view both the local mailspool and an IMAP INBOX at the same time (for example). You could also view all new mail messages at the same time in all of your mailboxes (by adding them all, and then limiting the view to just new messages). You could even search all mailboxes by adding all mailboxes and then searching. Thinking beyond this, really blue-sky, would be if mailboxes were handled similar to the way threading is handled: that all messages in a given mailbox could be ""collapsed"" the way a thread can be collapsed. I don't know how difficult any of this would be to implement. It would be awesome, though: very mutt-like, very simple interface, and extraordinarily powerful (better than any other mail reader out there, bar none)." memoryhole 3059 Add pattern to match ranges relative to matched results. mutt 1.5.18 2.0 enhancement mutt-dev new 2008-05-23T05:56:58-07:00 2008-05-28T22:07:30-07:00 "I would like to propose a new pattern '''~M''' that allows you to select a range from matched results. This is useful for: * Limiting/tagging the first 500 results: '''~M <500 (other patterns)'''[[BR]] * Limiting/tagging results from the 5th to 10th: '''~M 5-10 (other patterns)'''[[BR]] * Limiting/tagging by matching the 50th result: '''~M 50 (other patterns)'''[[BR]] etc. I have attached a patch implementing this feature. It works on both 1.5.18 and the mercurial development branch. I also attempted to add documentation regarding this pattern as best as possible." naveen 3064 "Implement ""show"" menu to list various internal configs as a nicely paged menu" display 2.0 enhancement mutt-dev new 2008-05-30T07:25:56-07:00 2008-08-26T08:25:58-07:00 "Running ':attachments ?' in mutt shows current attachment settings on stdout instead of inside mutt... which is ugly. The attached patch implements a ""show"" menu with a few ""demo"" views to show what this can be used for: * show attachments: Replacement for ""attachments ?"" (latter kept for compatibility) * show config [regex]: Show all config options matching regex (if omitted, regex defaults to ""."", i.e. all) * show mailboxes: Show all known mailboxes in order they were defined * show spam: Show all currently configures spam recognition commands Except ""config"" these don't seem to be extremely useful. However, what comes to mind and why I took the prototype this far is to mostly prepare the code to be ready to implement this for hooks. For example, 'show folder-hook [folder-regex]' would be nice to have to know what folder-hooks mutt would execute in what order." pdmef 3071 Bug#469489: mutt: should support CONDSTORE IMAP 1.5.18 2.0 enhancement brendan new 2008-06-07T16:01:23-07:00 2010-02-20T19:40:26-08:00 "{{{ Date: Wed, 5 Mar 2008 14:18:30 +0000 From: ""brian m. carlson"" Subject: Bug#469489: mutt: should support CONDSTORE }}} It would be very nice if mutt would support IMAP CONDSTORE. In conjunction with a supporting server, this has the potential to reduce the amount of bandwidth used. " myon 3072 Bug#477277: provide a second level of limit functionality mutt 1.5.18 2.0 enhancement mutt-dev new 2008-06-07T16:49:15-07:00 2009-01-02T07:27:32-08:00 " {{{ (See also #2967) ----- Forwarded message from martin f krafft ----- Date: Tue, 22 Apr 2008 09:38:10 +0200 From: martin f krafft To: Debian Bug Tracking System Subject: Bug#477277: provide a second level of limit functionality I have a number of filters which I constantly want ""on"" when I browse my mailboxes, such as: ~(~hX-Ignore-Thread) or ~h'X-Label: Debian::mutt' I would like to be able to treat these independently of the standard function, for a number of reasons: - I use a lot - I want to be able to change the limit without having to re-run the expensive ~h filters noted above every time - I would like to be able to replace an existing filter by just starting to type, which replaces the entire line. If I have to use the same for the aforementioned ""persistent"" filters, then, to replace e.g. ~L dato with ~s mutt, I have to use the cursor keys to navigate to the end of the persistent filters and hit ctrl-k before I can change the filter. Thanks for your consideration. ----- End forwarded message ----- }}}" myon 3099 (pager.c) Background of quoted text doesn't fill the whole line display 1.5.18 2.0 enhancement mutt-dev new 2008-08-06T20:30:51-07:00 2009-06-30T07:47:22-07:00 "In the pager, suppose there is a quoted line {{{ >> abcd }}} Only the background of ""abcd"" is painted with the color specified in muttrc, resulting in ugly quoted blocks. The correct behavior should be to paint the background of the _whole line_. Something like the following should fix it. (But please double check, since I modified pager.c at multiple places and I'm not quite sure this is indeed the trunk fixing this problem). In pager.c: {{{ else def_color = ColorDefs[ (*lineInfo)[m].type ]; + if ((*lineInfo)[m].type == MT_COLOR_QUOTED) { + struct q_class_t *class = (*lineInfo)[m].quote; + + if (class) + { + def_color = class->color; + + while (class && class->length > cnt) + { + def_color = class->color; + class = class->up; + } + } + } + + attrset (def_color); #ifdef HAVE_BKGDSET bkgdset (def_color | ' '); }}}" jcolinzheng 3103 expand environment variables in folder names mutt 2.0 enhancement mutt-dev new 2008-08-13T15:32:20-07:00 2009-01-04T12:37:15-08:00 My shop has been using the attached patch for years to allow us to use a $ENVVAR in the filename when saving to a folder. I suspect others would benefit from this function as well, so I'm submitting it as an enhancement request. eravin 3110 Bug#71996: can't set empty header fields mutt 2.0 enhancement mutt-dev new 2008-08-23T09:41:33-07:00 2009-01-04T12:36:46-08:00 " {{{ An old one I couldn't find in the bug list: ----- Forwarded message from Gerfried Fuchs ----- Date: Tue, 19 Sep 2000 09:18:03 +0200 From: Gerfried Fuchs Reply-To: Gerfried Fuchs , 71996@bugs.debian.org To: Debian Bug Tracking System Subject: Bug#71996: can't set empty header fields Package: mutt Version: 1.2.5-1 Severity: wishlist Currently it is not possible to set an epmty header field, which I think would be great, to have e.g. Pgp: Attach: per Default on the screen. There are already other empty headers on the screen - so why it's not possible to have this also as a user-feature? }}}" myon 3118 Implement internationalized email header support mutt 2.0 enhancement mutt-dev new 2008-09-10T06:12:53-07:00 2008-09-10T06:12:53-07:00 The specs are: http://www.ietf.org/rfc/rfc5335.txt, http://www.ietf.org/rfc/rfc5336.txt and http://www.ietf.org/rfc/rfc5337.txt. Or use some library to handle it (if available). pdmef 3121 Mutt should not use invalid charset when sending a message charset 2.0 enhancement mutt-dev new 2008-09-20T13:11:41-07:00 2009-06-17T08:07:39-07:00 "This is a followup to bug #2956. Mutt should not use invalid charset when sending a message, even when the user does something wrong. This can occur when $charset is a local-specific charset[*] and one does ""mutt address < file"" under UTF-8 locales where the file contains invalid UTF-8 sequences, due to the fallback to $charset. Mutt should either return an error or use a Content-Type specified by the user (defaulting to application/octet-stream?). [*] e.g. with a //TRANSLIT suffix. BTW, it can make sense to use //TRANSLIT even for UTF-8 as the terminal doesn't necessarily have all the necessary fonts." vinc17 3136 Please merge sendbox mode (Outbox for some IMAP servers) IMAP 2.0 enhancement brendan new 2008-11-23T20:53:30-08:00 2011-07-04T02:26:32-07:00 "Aron Griffis published a patch[1,2] so that mutt can be used as an IMAP client that is Outbox-aware. That's a Courier-IMAP[3] feature that allows for sending mails when they are added to a particular box (which defaults to INBOX.Outbox when this mode is enabled on the server). That proves to be particularly useful when one is using remote IMAP through offlineimap, since there's no need to have a local MTA, to track network status and the like (I've been using postfix and postqueue -f for some years now). Just taking care of running offlineimap (for both incoming and outgoing mail at the same time) is then sufficient. 1. http://n01senet.blogspot.com/2006/10/scratching-mutt-part-1-introducing.html 2. http://n01senet.blogspot.com/2007/02/scratching-mutt-part-2-patch-and.html 3. http://www.inter7.com/courierimap/INSTALL.html#imapsend The original patch was designed for mutt 1.5.12 and said to apply on 1.5.13 as well. I've “ported” it to 1.5.18, and it looks like it now applies on both the pristine 1.5.18 release and the “patched” version as used in the Debian mutt-patched package. I didn't really get the reason for keeping sent mails as unread, so I'm proposing a tiny modification. (I'll try and use hg next time, I've still got to read the manual a bit more before before efficient enough.) Mraw,[[BR]] !KiBi." KiBi 3140 ignore old flag set by other mail clients IMAP 2.0 enhancement brendan new 2008-12-14T06:33:59-08:00 2009-01-03T10:58:46-08:00 "I am occasionally using other mail clients to access my mailbox over IMAP. The IMAP server, however, adds to all new mails which have not been read the old flag (Status: O). I would prefer if all unread mails in mutt would all be marked as ""New"" and not some as ""Old"" and some as ""New"". I tried to get a patch included into dovecot but it was refused as it would violate the IMAP RFC. The attached patch let's mutt ignore that flag completely, with a new config option called ""ignore_old_flag"". All ""Old"" flagged mails are now still flagged as ""New""." adrian13 3200 Missing newline for To: field in composer window display 1.5.18 2.0 enhancement mutt-dev new 2009-03-11T00:51:21-07:00 2009-03-11T10:26:17-07:00 "Hi, when sending Mails to multiple receivers with long email addresses, it is no longer possible to see all receivers in the To: field of the composer window. The first two or three addresses are still visible, the remaining addresses are hidden, because the line length is longer than the window size. It should be possible to check if the line length is greater than the windows length and insert a number of ""virtual"" newlines such that all addresses are visible. I can provide a screenshot if that's necessary." matthias 3438 naming scheme for recalled draft tempfiles IMAP 1.5.20 2.0 enhancement brendan new 2010-08-06T09:18:12-07:00 2011-11-21T09:38:22-08:00 "This is about mutt's interaction with Vim, but if anything should be changed in response to this, it's on mutt's end. Vim automatically detects filenames that start with 'mutt' and end with any six characters that are either alphanums or - or _, and declares their filetype to be ""mail"". I am guessing that this is because at least on IMAP, when one recalls a postponed message, mutt downloads it and names the tempfile in tmpdir 'mutt' plus six chars. Therefore, Vim will set the filetype to mail when you edit a recalled draft message. Wonderful. Annoying side-effect: a mutt config file named, e.g., 'muttmacros', gets declared by Vim to be mail, which automatically sets annoying things (especially if one has added special autocommands for the mail filetype, like linebreaking stuff). The filetype *should* be ""muttrc"". In that file, one might have all of ones macros separated out from the muttrc. This happens to any mutt+6char filename, like muttrchook, muttemails, mutthooksrc, muttsource, muttimaprc, etc. Now this can be avoided by not using those filenames, but as a matter of principle, mutt ought to name the recalled-draft-tempfiles according to some other system that's unlikely to get trampled on by a user's ""normal"" config filename. Why not the usual tempfile naming system ""mutt-hostname-bunchofnumbers""? Or 'mutt' plus 18 chars instead of 6? BTW, setting a Vim modeline in those files to override Vim's behavior does not work." balderdash 3477 do not restrict variables for program calls to maximum path length mutt 2.0 enhancement mutt-dev new 2010-12-06T09:44:10-08:00 2011-11-21T09:37:21-08:00 "Nearly half of the variables of type ""path"" are not really paths, but strings that are handed over to system(3). They are not at all limited by the maximum path length (_POSIX_PATH_MAX == 256). It would make sense to add a new type (e.g. DT_CMD) for these variables. I attached a patch for better understanding. A (maybe incomplete) list of this variables is: $display_filter, $dotlock_program, $editor, $ispell, $mixmaster, $pager, $print_command, $query_command, $sendmail, $shell, $visual" jw 3484 wish: Mutt IMAP could support offline view mails when header&body cache enabled IMAP 1.5.21 2.0 enhancement brendan new 2010-12-30T23:33:54-08:00 2010-12-31T06:24:22-08:00 "What I expected is, IMAP cached mails could be viewed by mutt when Internet is not available. this function could be enabled when body cache is enabled. maybe this could be a possible solution: 1) cache message bodies in Maildir format 2) switching IMAP mode to read (read-only)local caches when internet is disabled. (or an control option could also be used in the .muttrc) this is just a simple description what I am thinking about, there may have a much better solution. I wonder such a IMAP function is just because sometime or somewhere we want to review our old mails but Internet is not available unfortunately. I knew here is a script named offlineIMAP could a similar thing, but I think it is somewhat not elaborate and a little ugly to use a python script to do such a function in parallel with mutt. so I wish the function involved in the mutt's future release. " duyang 3485 An option could be added to control IMAP message fetching IMAP 1.5.21 2.0 enhancement brendan new 2010-12-31T00:36:07-08:00 2011-06-25T22:36:44-07:00 "Hi, I found that all the message in the current window view(IMAP mailbox) would be fetched at once everything I switch to a new window page. this is a good for when most message's body have been cached. but this also has low performance, when I have a lot of messages not seen(have been cached yet) in one inbox and I want to check a mail which I have to switch several pages down the window, then I have to wait for all mails above the mail (which I want to check) being downloaded. if I have several large mails above it, maybe I have to wait for many hours. it is even more worse if I have a low network bandwidth. so it looks a little unacceptable. so I think an option could be added to control the way about message fetching for IMAP. it controls fetching message once for a page or once for a message just it was viewed. if allows message could be fetched only it was checked, the mutt's IMAP performance could be much more preferable. thanks a lot! du yang" duyang 123 Lack of fallback to default English responses in localized env. mutt 1.2i defect mutt-dev new 2000-05-14T12:30:16-07:00 2007-03-26T19:17:13-07:00 "{{{ Package: mutt Version: 1.2i Severity: normal -- Please type your report below this line The BIG problem in the Mutt is lack of fallback to English responce: keyboard usually stays in English mode and don't need to be switched to native mode just for simple yes/no reply (too many keys must be pressed), moreover, it is too hard to remember all that localized responces (for mutt_multi_choice case) while English responces are the same from system to system, i.e. user can use English responces on _any_ computer without searching a keys. Moreover, since all Mutt commands are English it is very contr-intuitive to use localized responces on English commands (as you can guess I am VERY against localized Mutt commands without fallback to English defaults too). English commands/responces must be enabled in any case _after_ localized commands/responces considered, even MS Windows implement this way in their localized software! This problem was discussed in mutt-dev mailing list long time ago and the next patch got many positive responses but constantly not included in the next Mutt versions for reason unknown to me. --- curs_lib.c.old Wed Sep 1 19:39:20 1999 +++ curs_lib.c Sun Sep 26 23:47:03 1999 @@ -156,6 +156,16 @@ def = 0; break; } + else if (tolower(ch.ch) == 'y') + { + def = 1; + break; + } + else if (tolower(ch.ch) == 'n') + { + def = 0; + break; + } else { BEEP(); @@ -413,8 +423,9 @@ { event_t ch; int choice; - char *p; + char *p, *nletters; + nletters = _(letters); mvaddstr (LINES - 1, 0, prompt); clrtoeol (); FOREVER @@ -428,6 +439,12 @@ } else { + p = strchr (nletters, ch.ch); + if (p) + { + choice = p - nletters + 1; + break; + } p = strchr (letters, ch.ch); if (p) { --- browser.c.orig Fri Sep 24 01:08:08 1999 +++ browser.c Sun Sep 26 23:46:25 1999 @@ -750,7 +750,7 @@ switch (mutt_multi_choice ((reverse) ? _(""Reverse sort by (d)ate, (a)lpha, si(z)e or do(n)'t sort? "") : _(""Sort by (d)ate, (a)lpha, si(z)e or do(n)'t sort? ""), - _(""dazn""))) + N_(""dazn""))) { case -1: /* abort */ resort = 0; --- commands.c.orig Wed Jul 7 02:56:24 1999 +++ commands.c Sun Sep 26 23:46:25 1999 @@ -337,7 +337,7 @@ switch (mutt_multi_choice (reverse ? _(""Rev-Sort (d)ate/(f)rm/(r)ecv/(s)ubj/t(o)/(t)hread/(u)nsort/si(z)e/s(c)ore?: "") : _(""Sort (d)ate/(f)rm/(r)ecv/(s)ubj/t(o)/(t)hread/(u)nsort/si(z)e/s(c)ore?: ""), - _(""dfrsotuzc""))) + N_(""dfrsotuzc""))) { case -1: /* abort - don't resort */ return -1; --- compose.c.orig Wed Aug 25 10:23:12 1999 +++ compose.c Sun Sep 26 23:46:25 1999 @@ -130,7 +130,7 @@ struct pgp_vinfo *pgp = pgp_get_vinfo(PGP_SIGN); switch (mutt_multi_choice (_(""(e)ncrypt, (s)ign, sign (a)s, (b)oth, select (m)ic algorithm, or (f)orget it? ""), - _(""esabmf""))) + N_(""esabmf""))) { case 1: /* (e)ncrypt */ bits |= PGPENCRYPT; --- muttlib.c.orig Sun Apr 9 14:39:02 2000 +++ muttlib.c Fri May 12 11:26:58 2000 @@ -671,7 +671,7 @@ if (*append == 0 && access (fname, F_OK) == 0) { switch (mutt_multi_choice - (_(""File exists, (o)verwrite, (a)ppend, or (c)ancel?""), _(""oac""))) + (_(""File exists, (o)verwrite, (a)ppend, or (c)ancel?""), N_(""oac""))) { case -1: /* abort */ case 3: /* cancel */ -- Mutt Version Information Mutt 1.2i (2000-05-09) Copyright (C) 1996-2000 Michael R. Elkins É ÄÒÕÇÉÅ. Mutt ÒÁÓÐÒÏÓÔÒÁÎÑÅÔÓÑ âåú ëáëéè-ìéâï çáòáîôéê; ÄÌÑ ÐÏÌÕÞÅÎÉÑ ÂÏÌÅÅ ÐÏÄÒÏÂÎÏÊ ÉÎÆÏÒÍÁÃÉÉ ××ÅÄÉÔÅ `mutt -vv'. Mutt Ñ×ÌÑÅÔÓÑ Ó×ÏÂÏÄÎÙÍ ÐÒÏÇÒÁÍÍÎÙÍ ÏÂÅÓÐÅÞÅÎÉÅÍ. ÷Ù ÍÏÖÅÔÅ ÒÁÓÐÒÏÓÔÒÁÎÑÔØ ÅÇÏ ÐÒÉ ÓÏÂÌÀÄÅÎÉÉ ÏÐÒÅÄÅÌÅÎÎÙÈ ÕÓÌÏ×ÉÊ; ÄÌÑ ÐÏÌÕÞÅÎÉÑ ÂÏÌÅÅ ÐÏÄÒÏÂÎÏÊ ÉÎÆÏÒÍÁÃÉÉ ××ÅÄÉÔÅ `mutt -vv'. System: FreeBSD 5.0-CURRENT [using ncurses 5.0] ðÁÒÁÍÅÔÒÙ ËÏÍÐÉÌÑÃÉÉ: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK -USE_FCNTL +USE_FLOCK +USE_IMAP -USE_GSS -USE_SSL +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" SHAREDIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" ISPELL=""/usr/local/bin/ispell"" þÔÏÂÙ Ó×ÑÚÁÔØÓÑ Ó ÒÁÚÒÁÂÏÔÞÉËÁÍÉ, ÉÓÐÏÌØÚÕÊÔÅ ÁÄÒÅÓ . þÔÏÂÙ ÓÏÏÂÝÉÔØ Ï ÏÛÉÂËÅ, ÉÓÐÏÌØÚÕÊÔÅ ÐÒÏÇÒÁÍÍÕ muttbug. >How-To-Repeat: >Fix: }}}" """Andrey A. Chernov"" " 498 mutt does not process PGP/MIME in digests crypto defect mutt-dev new 2001-03-08T06:47:47-08:00 2009-06-30T07:38:33-07:00 "{{{ Package: mutt Version: 1.3.15-2 Severity: normal [NOTE: this bug report has been submitted to the debian BTS as Bug#88860. Please Cc all your replies to 88860@bugs.debian.org.] From: JP Sugarbroad Subject: mutt does not process PGP/MIME in digests Date: Wed, 7 Mar 2001 13:43:05 -0600 When viewing digests with the 'v' key, mutt does not process the PGP/MIME signed messages that the digest might contain. -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux dragon 2.4.2-ac3 #1 Mon Feb 26 00:01:32 CST 2001 i686 Versions of packages mutt depends on: ii libc6 2.2.2-1 GNU C Library: Shared libraries an ii libncurses5 5.0-8 Shared libraries for terminal hand ii libsasl7 1.5.24-5 Authentication abstraction library ii postfix [mail-transport-a 0.0.20010228-2 A high-performance mail transport -- Taral Please use PGP/GPG to send me mail. ""Never ascribe to malice what can as easily be put down to stupidity."" >How-To-Repeat: >Fix: }}}" """Marco d'Itri"" " 580 mutt stores PGP passphrase insecurely crypto 1.5.19 defect mutt-dev reopened 2001-05-03T22:29:01-07:00 2009-07-27T10:13:38-07:00 "{{{ Package: mutt Version: 1.3.15-2 [NOTE: this bug report has been submitted to the debian BTS as Bug#96144. Please Cc all your replies to 96144@bugs.debian.org.] From: Brian Ristuccia Subject: mutt stores PGP passphrase insecurely Date: Thu, 3 May 2001 01:44:50 -0400 When caching passphrases, mutt uses memory that's not locked. The passphrase can be recovered if that part of mutt's address space is swapped to disk. In order for the secret key to remain secure in the event that the machine is lost or stolen, the memory area occupied by the passphrase must be locked to prevent the swap file from being contaminated with the passphrase. Note that mutt zeros out the passphrase when it times out, but there's no guarantee that any old blocks on the swap space will be overwritten before the machine is shut down or stolen. This issue is of particular importance with laptop computers, since PGP encryption is the only thing standing between an unauthorized reader and your email should the machine get stolen. Since Linux 2.2.x and 2.4.x don't seem to allow ordinary users to lock even small amounts of memory, one potential solution would be to have mutt executed by a wrapper program that passes it a locked shared memory segment just big enough to hold the passphrase. Swap over an encrypted loopback filesystem initialized with a throwaway key at each reboot is a workaround. But using an encrypted loopback filesystem is computationally intensive and might drain batteries prematurely, especially on smaller laptops. A kernel level swap cleaner daemon that overwrites recently freed swap blocks would also work, but with a similar battery life penalty. -- Brian Ristuccia brian@ristuccia.com bristucc@cs.uml.edu >How-To-Repeat: >Fix: }}}" Marco d'Itri 975 pgp-hook confirmation relief and automatic key selection mutt 1.3.25i defect mutt-dev new 2002-01-14T08:54:07-08:00 2007-03-26T19:47:32-07:00 "{{{ Package: mutt Version: 1.3.25i Severity: wishlist -- Please type your report below this line As has been noted before (bug #343), use of pgp-hook unnecessarily prompts for confirmation about the key selected via the pgp-hook for a particular recipient. Furthermore, it is often the case with pgp-hook that a single key is selected, yet a list of keys (usually 1 with multiple uids) is presented for selection. It has been noted that since the recipient argument for pgp-hook is a regular expression, confirmation is necessary to avoid false positives matching the hook. Still, I believe it should be possible to circumvent the hook confirmation if so desired. Even one could avoid the hook confirmation, a list of keys is always presented, which brings me to the other (related) item. Whether key matching is done via pgp-hook or using recipient address(es), there are often cases where a single key is listed (sometimes with multiple uids). Again, the decision to show a list of keys when there is only one (real) key should be up to the user. This patch http://www.woolridge.org/mutt/patches/patch-1.3.25.dw.pgp-hook.3 implements the above desired features by adding two variables: pgp_confirmhook and pgp_autoselectkey. The names were selected in an attempt to be as similar as possible to existing variables. The patch also allows multiple pgp-hook's per recipient, which I personally don't use, but it might be useful for other people (something like bug #973 comes to mind). Documentation for the added variables is also included with the patch. -- 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 /opt/gcc-2.95.2/lib/gcc-lib/i586-pc-linux-gnu/2.95.2/specs gcc version 2.95.2 19991024 (release) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.3.25i (2002-01-01) 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.2.19 (i586) [using ncurses 4.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=""/var/spool/mail"" PKGDATADIR=""/opt/share/mutt"" SYSCONFDIR=""/opt/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.3.25.dw.pgp-hook.3 >How-To-Repeat: >Fix: }}}" Dale Woolridge 1126 Minor RFC differences mutt 1.3.27i defect mutt-dev new 2002-03-23T21:37:31-08:00 2005-10-14T02:03:57-07:00 "{{{ Package: mutt Version: 1.3.27-4 Severity: wishlist -- Please type your report below this line I found a couple minor incorrect behaviours of Mutt in respect to RFC2822: - Quoting double quotes within a quoted string is not handled. E.g. To: ""Giant; \""Big\"" Box"" is converted to: To: ""Giant; Big Box"" - The Resent-* headers are appended to the header, but should be prepended. - Comments are allowed within Content-* fields, so 'Content-type: (comment)text/plain' should be allowed. Regards, Wouter Verheijen, XS2Mail -- 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 cc Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs gcc version 2.95.4 (Debian prerelease) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.3.27i (2002-01-22) 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.10 (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_GNUTLS +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 +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.3.27.bse.xtitles.1 patch-1.3.26.appoct.3 patch-1.3.15.sw.pgp-outlook.1 patch-1.3.27.admcd.gnutls.17 Md.use_editor Md.paths_mutt.man Md.muttbug_no_list Md.use_etc_mailname Md.muttbug_warning Md.gpg_status_fd patch-1.3.24.rr.compressed.1 patch-1.3.25.cd.edit_threads.9.1 patch-1.3.23.1.ametzler.pgp_good_sign >How-To-Repeat: >Fix: }}}" Wouter Verheijen 1158 persistent locale setting mutt 1.3.28i defect mutt-dev new 2002-04-19T05:32:13-07:00 2007-04-07T07:25:29-07:00 "{{{ Package: mutt Version: 1.3.28-2 Severity: normal -- Please type your report below this line I've set a send-hook which changes the $locale variable to have the month string and day string changed in the date, when quoting a mail received from the person concerned with this send-hook. And when I return to the menu after sending the mail, the date is written with this locale instead of my default locale. -- 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 cc Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs gcc version 2.95.4 20011002 (Debian prerelease) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.3.28i (2002-03-13) 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.17 (i586) [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_GNUTLS +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 +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.5.tlr.mx_open_append.2 patch-1.3.28.cvs.indexsegfault patch-1.3.27.bse.xtitles.1 patch-1.3.26.appoct.3 patch-1.3.15.sw.pgp-outlook.1 patch-1.3.27.admcd.gnutls.19 Md.use_editor Md.paths_mutt.man Md.muttbug_no_list Md.use_etc_mailname Md.muttbug_warning Md.gpg_status_fd patch-1.3.24.rr.compressed.1 patch-1.3.25.cd.edit_threads.9.1 patch-1.3.23.1.ametzler.pgp_good_sign >How-To-Repeat: >Fix: }}}" Bernard Massot 1267 mutt: mbox: From_ line inconsistent time mutt defect mutt-dev reopened 2002-07-09T19:07:04-07:00 2009-04-16T09:36:05-07:00 "{{{ Package: mutt Version: 1.4i Severity: wishlist There is a problem in the From line of mbox messages. You are using ctime() and that function uses localtime without saving the timezone. So you must use asctime (gmtime (&t)) for these dates to have any meaning. It moves from localtime to gmtime. Because localtimes must be accompanied with a timezone and rollback one hour once a year. There are two ways to close this bug: - Applying the patch. - Adding the timezone in the form +0100, but this would break the format }}}" Eduardo Pérez Ureta 1385 "Macros with """" don't work on tagged messages" mutt 1.5.20 defect mutt-dev new 2002-11-13T22:52:26-08:00 2009-06-19T14:25:29-07:00 "{{{ Package: mutt Version: 1.4.0-5 Severity: normal -- Please type your report below this line Hi, In my .muttrc: macro index ""unset wait_key\nless\nset wait_key\n"" ""Some silly command to test macros"" macro index ""less\n"" ""Some silly command to test macros"" Now, if I tag a few messages and do tag-F3 (; and then F3), the message the cursor is on now gets piped to less. But if I do tag-F4 (; and then F4), all tagged messages get piped to less. I would expect the F3 macro to behave like the F4 macro regarding this point. I have: pipe_decode unset pipe_split unset -- 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 cc Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs gcc version 2.95.4 20011002 (Debian prerelease) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.4i (2002-05-29) 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 (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_GNUTLS +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 +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.4.0.dw.pgp-traditional.2 patch-1.4.Md.gpg-agent patch-1.4.Md.domain_gethostbyname patch-1.3.28.cvs.indexsegfault patch-1.5-me_editor.2 patch-1.5.1.tlr.mailboxes-overflow.1 patch-1.4.0.me.maildir.1 patch-1.3.27.bse.xtitles.1 patch-1.3.27.me.aliasdups.1 patch-1.3.26.appoct.3 patch-1.3.27.bayer.quiet_gnupg patch-1.4.admcd.gnutlsbuild.53d patch-1.4.admcd.gnutlsdlopen.53d patch-1.4.admcd.gnutls.55d Md.paths_mutt.man Md.muttbug_no_list Md.muttbug_warning Md.gpg_status_fd patch-1.4.0.cd.edit_threads.9.2 patch-1.3.24.rr.compressed.1 patch-1.3.23.1.ametzler.pgp_good_sign Received: (at submit) by bugs.guug.de; 6 May 2003 18:30:08 +0000 From md@Linux.IT Tue May 06 20:30:08 2003 Received: from attila.bofh.it ([213.92.8.2] ident=postfix) by trithemius.gnupg.org with esmtp (Exim 3.35 #1 (Debian)) id 19D7CQ-0004AH-00 for ; Tue, 06 May 2003 20:29:58 +0200 Received: by attila.bofh.it (Postfix, from userid 10) id 4A1BB5F84C; Tue, 6 May 2003 20:31:53 +0200 (CEST) Received: by wonderland.linux.it (Postfix/Md, from userid 1001) id 04E7C141F3; Tue, 6 May 2003 20:31:36 +0200 (CEST) From: Marco d'Itri To: submit@bugs.guug.de Subject: mutt: tag-prefix works only on the first command of a macro X-GUUG-CC: 192145@bugs.debian.org Message-Id: <20030506183136.04E7C141F3@wonderland.linux.it> Date: Tue, 6 May 2003 20:31:36 +0200 (CEST) Package: mutt Version: 1.5.4-1 Severity: normal [NOTE: this bug report has been submitted to the debian BTS as Bug#192145. Please Cc all your replies to 192145@bugs.debian.org .] From: ""dr.Danko Miklos"" Subject: mutt: tag-prefix works only on the first command of a macro Date: Tue, 06 May 2003 13:47:29 +0200 When using a macro on tagged messages, the tag-prefix (;) works only on the first of the commands. A test case: macro index A ""cat >> test1\n\ cat >> test2\n"" ""Adds message(s) to test files"" After adding this to .muttrc, tag a few messages. Use tag-prefix (';' by default) and 'A'. After this, test1 will contain the tagged messages, while test2 the message, which is under the cursor. -- System Information Debian Release: testing/unstable Kernel Version: Linux chewing 2.4.20 #3 Mon Mar 3 14:54:08 CET 2003 i686 unknown unknown GNU/Linux Versions of the packages mutt depends on: ii exim 3.36-6 An MTA (Mail Transport Agent) ii libc6 2.3.1-17 GNU C Library: Shared libraries and Timezone ii libdb4.0 4.0.14-1.2 Berkeley v4.0 Database Libraries [runtime] ii libidn9 0.1.11-3 GNU libidn library, implementation of IETF I ii libncurses5 5.3.20021109-2 Shared libraries for terminal handling ii libsasl7 1.5.27-3.5 Authentication abstraction library. ii exim 3.36-6 An MTA (Mail Transport Agent) ^^^ (Provides virtual package mail-transport-agent) >How-To-Repeat: >Fix: }}}" lionel@… 1445 "mistaken folding of initial ""From "" breaks header parsing by adding lines" mutt 1.4i defect mutt-dev new 2003-01-27T20:03:01-08:00 2005-10-04T11:36:54-07:00 "{{{ Package: mutt Version: 1.4i Severity: important -- Please type your report below this line A lot of email that I receive has a line below the initial ""From"" line. Every time mutt saves out a folder containing such a message, it sticks new status information into the message, making it grow in size. This doesn't destroy any data but it does become quite annoying as the bogus status lines start showing up in mail when you try to read it. For example, consider the following message: ---- cut here ---- From a@b.c Thu Jan 2 19:48:59 2003 id Subject: test To: andru@cs.cornell.edu Status: RO Content-Length: 14989 Lines: 364 This is an email message that will grow every time you read it in mutt. ---- cut here ---- If you put this in a file and open it with mutt, then quit, you will get a messsage that looks like this: ---- cut here ---- From a@b.c Thu Jan 2 19:48:59 2003 id Status: O Content-Length: 155 Lines: 6 Subject: test To: andru@cs.cornell.edu Status: RO Content-Length: 14989 Lines: 364 This is an email message that will grow every time you read it in mutt. ---- cut here ---- Although the build environment info below says mutt 1.2.5, I have just tested it on 1.4i and the same problem exists there. Andrew Myers (andru@cs.cornell.edu) -- 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-redhat-linux/2.96/specs gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.2.5.1i (2000-07-28) Copyright (C) 1996-2000 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.18-4 [using slang 10404] Compile options: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID -USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP +USE_GSS +USE_SSL +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" SHAREDIR=""/etc"" SYSCONFDIR=""/etc"" ISPELL=""/usr/bin/ispell"" To contact the developers, please mail to . To report a bug, please use the muttbug utility. --- Begin /usr/local/etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" --- End /usr/local/etc/Muttrc >How-To-Repeat: >Fix: }}}" Andrew Myers 1453 charset= ignored when Content-Type != text/plain w/ base64 charset 1.5.3i defect mutt-dev new 2003-02-02T20:40:39-08:00 2009-06-30T07:41:07-07:00 "{{{ Package: mutt Version: 1.5.3-1 Severity: normal Tags: upstream -- Please type your report below this line Please look on the mails that our DDTP (ddtp.debian.org) sends. It contains the data (basically text in various encodings) embedded in base64 chunks. The Content-Type is not text/plain, but mutt recognices it as text and shows in the pager when you view the attachment. However, mutt IGNORES THE CHARSET SPECIFICATION IN THIS CASE and does not recode the content to my current environment's charset (UTF-8), so I see non-ascii chars as escape codes. ------------=_1044181221-30562-2 Content-Type: application/debian-dt; charset=""ISO-8859-1""; name=""bug21394.txt"" Content-Disposition: inline; filename=""bug21394.txt"" Content-Transfer-Encoding: base64 CiMgQnVnLU5yLjogMjEzOTQgCiMgICAKCgpCVFNDTE9TRTogMjEzOTQKIyBQ YWNrYWdlczogb3BlbmdhdGUKIyBvbGQgZGVzY3JpcHRpb246CiMgRGVzY3Jp -- System Information Debian Release: testing/unstable Kernel Version: Linux zombie 2.4.21-pre4 #6 Fri Jan 31 10:00:46 CET 2003 i686 unknown unknown GNU/Linux Versions of the packages mutt depends on: hi libc6 2.3.1-10 GNU C Library: Shared libraries and Timezone ii exim 3.36-4 An MTA (Mail Transport Agent) ii libncurses5 5.3.20021109-2 Shared libraries for terminal handling ii libsasl7 1.5.27-3.3 Authentication abstraction library. ii exim 3.36-4 An MTA (Mail Transport Agent) ^^^ (Provides virtual package mail-transport-agent) -- 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 cc Reading specs from /usr/lib/gcc-lib/i386-linux/3.2.2/specs Configured with: /build/packages/gcc/3.2/gcc-3.2-3.2.2ds6/src/configure -v --enable-languages=c,c++,java,f77,proto,pascal,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --disable-__cxa_atexit --enable-java-gc=boehm --enable-objc-gc i386-linux Thread model: posix gcc version 3.2.2 20030129 (Debian prerelease) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.3i (2002-12-17) Copyright (C) 1996-2002 Michael R. Elkins und andere. Mutt übernimmt KEINERLEI GEWÄHRLEISTUNG. Starten Sie `mutt -vv', um weitere Details darüber zu erfahren. Mutt ist freie Software. Sie können es unter bestimmten Bedingungen weitergeben; starten Sie `mutt -vv' für weitere Details. System: Linux 2.4.21-pre4 (i686) [using ncurses 5.3] Einstellungen bei der Compilierung: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +IMAP_EDIT_THREADS -USE_GSS -USE_SSL +USE_GNUTLS +USE_SASL -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_PGP +HAVE_SMIME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" Um die Entwickler zu kontaktieren, schicken Sie bitte eine Nachricht (in englisch) an . Um einen Bug zu melden, verwenden Sie bitte das Programm flea(1). patch-1.5.3.Md.gpg_status_fd patch-1.4.Md.gpg-agent patch-1.5.1.cd.edit_threads.9.2 patch-1.5.3.Md.etc_mailname_gethostbyname patch-1.3.23.1.ametzler.pgp_good_sign patch-1.3.27.bse.xtitles.1 Md.muttbug patch-1.4.admcd.gnutlsdlopen.53d patch-1.4.admcd.gnutlsbuild.53d patch-1.4.admcd.gnutls.55d patch-1.5.3.rr.compressed.1 Received: (at submit) by bugs.guug.de; 2 Feb 2003 11:20:22 +0000 From md@Linux.IT Sun Feb 02 12:20:22 2003 Received: from attila.bofh.it ([213.92.8.2] ident=postfix) by trithemius.gnupg.org with esmtp (Exim 3.35 #1 (Debian)) id 18fIAW-0008Us-00 for ; Sun, 02 Feb 2003 12:20:12 +0100 Received: by attila.bofh.it (Postfix, from userid 10) id E07FE5F703; Sun, 2 Feb 2003 12:21:57 +0100 (CET) Received: by wonderland.linux.it (Postfix/Md, from userid 1001) id 7893333BE2; Sun, 2 Feb 2003 12:14:48 +0100 (CET) From: Marco d'Itri To: submit@bugs.guug.de Subject: mutt-1.5.3i: charset= ignored when Content-Type != text/plain w/ base64 X-GUUG-CC: 179445@bugs.debian.org Message-Id: <20030202111448.7893333BE2@wonderland.linux.it> Date: Sun, 2 Feb 2003 12:14:48 +0100 (CET) Package: mutt Version: 1.5.3-1 Severity: normal [NOTE: this bug report has been submitted to the debian BTS as Bug#179445. Please Cc all your replies to 179445@bugs.debian.org .] From: blade@debian.org Subject: mutt-1.5.3i: charset= ignored when Content-Type != text/plain w/ base64 Date: Sun, 02 Feb 2003 11:40:39 +0100 -- Please type your report below this line Please look on the mails that our DDTP (ddtp.debian.org) sends. It contains the data (basically text in various encodings) embedded in base64 chunks. The Content-Type is not text/plain, but mutt recognices it as text and shows in the pager when you view the attachment. However, mutt IGNORES THE CHARSET SPECIFICATION IN THIS CASE and does not recode the content to my current environment's charset (UTF-8), so I see non-ascii chars as escape codes. ------------=_1044181221-30562-2 Content-Type: application/debian-dt; charset=""ISO-8859-1""; name=""bug21394.txt"" Content-Disposition: inline; filename=""bug21394.txt"" Content-Transfer-Encoding: base64 CiMgQnVnLU5yLjogMjEzOTQgCiMgICAKCgpCVFNDTE9TRTogMjEzOTQKIyBQ YWNrYWdlczogb3BlbmdhdGUKIyBvbGQgZGVzY3JpcHRpb246CiMgRGVzY3Jp -- System Information Debian Release: testing/unstable Kernel Version: Linux zombie 2.4.21-pre4 #6 Fri Jan 31 10:00:46 CET 2003 i686 unknown unknown GNU/Linux Versions of the packages mutt depends on: hi libc6 2.3.1-10 GNU C Library: Shared libraries and Timezone ii exim 3.36-4 An MTA (Mail Transport Agent) ii libncurses5 5.3.20021109-2 Shared libraries for terminal handling ii libsasl7 1.5.27-3.3 Authentication abstraction library. ii exim 3.36-4 An MTA (Mail Transport Agent) ^^^ (Provides virtual package mail-transport-agent) -- 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 cc Reading specs from /usr/lib/gcc-lib/i386-linux/3.2.2/specs Configured with: /build/packages/gcc/3.2/gcc-3.2-3.2.2ds6/src/configure -v --enable-languages=c,c++,java,f77,proto,pascal,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --disable-__cxa_atexit --enable-java-gc=boehm --enable-objc-gc i386-linux Thread model: posix gcc version 3.2.2 20030129 (Debian prerelease) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.3i (2002-12-17) Copyright (C) 1996-2002 Michael R. Elkins und andere. Mutt übernimmt KEINERLEI GEWÄHRLEISTUNG. Starten Sie `mutt -vv', um weitere Details darüber zu erfahren. Mutt ist freie Software. Sie können es unter bestimmten Bedingungen weitergeben; starten Sie `mutt -vv' für weitere Details. System: Linux 2.4.21-pre4 (i686) [using ncurses 5.3] Einstellungen bei der Compilierung: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +IMAP_EDIT_THREADS -USE_GSS -USE_SSL +USE_GNUTLS +USE_SASL -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_PGP +HAVE_SMIME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" Um die Entwickler zu kontaktieren, schicken Sie bitte eine Nachricht (in englisch) an . Um einen Bug zu melden, verwenden Sie bitte das Programm flea(1). patch-1.5.3.Md.gpg_status_fd patch-1.4.Md.gpg-agent patch-1.5.1.cd.edit_threads.9.2 patch-1.5.3.Md.etc_mailname_gethostbyname patch-1.3.23.1.ametzler.pgp_good_sign patch-1.3.27.bse.xtitles.1 Md.muttbug patch-1.4.admcd.gnutlsdlopen.53d patch-1.4.admcd.gnutlsbuild.53d patch-1.4.admcd.gnutls.55d patch-1.5.3.rr.compressed.1 >How-To-Repeat: >Fix: }}}" blade@… 1741 ANSI Checks Invoked AFTER display_filter :-( display 1.5.5.1i defect mutt-dev new 2003-12-21T03:20:08-08:00 2008-07-09T05:48:26-07:00 "{{{ Package: mutt Version: 1.5.5.1i Severity: wishlist -- Please type your report below this line When you have a filter that changes the colors in a message, the results of that filter (which are presumably trusted, as the filter can easily toss ANSI escape sequences if it doesn't like 'em) are what's filtered when allow_ansi is disabled, rather than the original message (which is presumably untrusted). I think it makes more sense to have allow_ansi work the other way (although I admit that people using complex display_filters will probably want to enable allow_ansi, anyway). Note, BTW, that my entire config is available online: http://www.bigfatdave.com/dave/mutt/ -- System Information System Version: Linux dave2 2.4.22 #2 SMP Mon Oct 27 06:48:20 EST 2003 i686 unknown unknown GNU/Linux -- 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 Leyendo especificaciones de /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/specs Configurado con: ./configure --enable-version-specific-runtime-libs --enable-languages=c,c++ Modelo de hilos: posix gcc versión 3.2.3 - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.5.1i (2003-11-05) Copyright (C) 1996-2002 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.22 (i686) [using ncurses 5.3] Opciones especificadas al compilar: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP +USE_IMAP -USE_GSS +USE_SSL -USE_SASL -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/beta/mutt_cvs/usr/share/mutt"" SYSCONFDIR=""/beta/mutt_cvs/usr/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER Para contactar a los desarrolladores mande un mensaje a . Para reportar un fallo use la utilería flea(1) por favor. --- Begin /home/dave/.muttrc source ~/.mutt/muttrc --- End /home/dave/.muttrc --- Begin /beta/mutt_cvs/usr/etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /beta/mutt_cvs/usr/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /beta/mutt_cvs/usr/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /beta/mutt_cvs/usr/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" --- End /beta/mutt_cvs/usr/etc/Muttrc >How-To-Repeat: >Fix: }}}" lists+mutt_bugs@… 1775 Threading should be deterministic mutt 1.5.5.1i defect mutt-dev new 2004-01-23T09:54:11-08:00 2005-10-08T09:22:58-07:00 "{{{ Package: mutt Version: 1.5.5.1-200401 Severity: wishlist -- Please type your report below this line Mutt's threading isn't deterministic. For instance, in my archive mailbox, I have initially: 5583 + 2002-01-25 xxxxxx xxxxxxx ( 41) linux 5584 F 2002-01-25 To xxxxxx xxxxx ( 62) `-> 5585 F 2002-01-25 To xxxxxx xxxxx ( 17) `-> 5586 F 2002-01-25 To xxxxxx xxxxx ( 25) `-> 5587 F 2002-01-25 To xxxxxx ( 16) Piles du Psion (was: Le futur 5588 F 2002-01-25 To mutt-dev@mut ( 15) C99 comments [...] 14979 + 2003-07-23 bugzilla-daemon ( 12) [Bug 213444] Crash due to Ja 14980 F 2002-01-25 To xxxxxx ( 18) Re: Le futur en question. 14981 r L 2002-01-25 xxx ( 55) |-> 14982 F 2002-01-25 To xxxxxx ( 14) | `-> 14983 r L 2002-01-25 xxx ( 17) `---> 14984 L 2002-01-25 xxx ( 40) |-> 14985 L 2002-07-31 xxxxxx xxxxx ( 12) |->Re: Psion (5mx...) et L 14986 L 2003-07-23 xxxxx xxxxxx ( 27) `->Re: Tr: ARM Conference: 14987 sL 2003-07-23 xxxxxx xxxxx ( 141) Re: mutt sets charset to utf But if I modify a message (e.g. flag-message twice on the latest message) and synchronize, I get: 5583 + 2002-01-25 xxxxxx xxxxxxx ( 41) linux 5584 F 2002-01-25 To xxxxxx xxxxx ( 62) `-> 5585 F 2002-01-25 To xxxxxx xxxxx ( 17) `-> 5586 F 2002-01-25 To xxxxxx xxxxx ( 25) `-> 5587 F 2002-01-25 To mutt-dev@mut ( 15) C99 comments [...] 14978 + 2003-07-23 bugzilla-daemon ( 12) [Bug 213444] Crash due to Ja 14979 F 2002-01-25 To xxxxxx ( 16) -->Piles du Psion (was: Le f 14980 L 2002-01-25 xxx ( 40) `--->Re: Le futur en questio 14981 r L 2002-01-25 xxx ( 17) |->Re: Le futur en questio 14982 F 2002-01-25 To xxxxxx ( 18) | `-> 14983 r L 2002-01-25 xxx ( 55) | `-> 14984 F 2002-01-25 To xxxxxx ( 14) | `-> 14985 L 2002-07-31 xxxxxx xxxxx ( 12) |->Re: Psion (5mx...) et L 14986 L 2003-07-23 xxxxx xxxxxx ( 27) `->Re: Tr: ARM Conference: 14987 sL 2003-07-23 xxxxxx xxxxx ( 141) Re: mutt sets charset to utf If I do another modification, I get the first threading. -- 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 cc Reading specs from /usr/lib/gcc-lib/powerpc-linux/3.3.2/specs Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc --disable-multilib powerpc-linux Thread model: posix gcc version 3.3.2 (Debian) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.5.1i (2003-11-05) Copyright (C) 1996-2002 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.18-newpmac (ppc) [using ncurses 5.3] [using libidn 0.1.14 (compiled with 0.1.14)] 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 -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME +BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/local/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/home/lefevre/Mail"" PKGDATADIR=""/home/lefevre/share/mutt"" SYSCONFDIR=""/home/lefevre/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.3.24.ats.parent_match.1 patch-1.5.1.vl.savehist.1 >How-To-Repeat: >Fix: }}}" vincent@… 1777 mailx mode clears screen mutt 1.4.1i defect mutt-dev new 2004-01-24T13:40:51-08:00 2005-10-28T03:22:25-07:00 "{{{ Package: mutt Version: 1.4.1i Severity: normal -- Please type your report below this line When running ""mutt -x"", the screen gets cleared. This is not consistent with mailx, and it makes it mildly annoying to copy/paste under Xwindows (because there's no keyboard shortcut for paste, it requires two mouse operations). -- 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 Using builtin specs. gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.4.1i (2003-03-19) Copyright (C) 1996-2002 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: NetBSD 1.5.4_ALPHA (i386) [using ncurses 5.2] Compile options: DOMAIN=""panix.com"" -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 SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/pkg/mutt-1.4.1/share/mutt"" SYSCONFDIR=""/pkg/mutt-1.4.1/etc/conf/mutt/mutt-1.4.1"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. --- Begin /net/u/1/a/aahz/.muttrc folder-hook conwork set sort=date source ~/.muttaliases bind index + next-page bind index - previous-page macro index X ""|spamassassin -r"" ""Vipul's Razor"" bind pager G bottom ignore ""from "" received content- mime-version status x- message-id ignore references in-reply-to return-path lines ignore list- delivered precedence errors-to user-agent ignore >received ignore phone ignore resent- ignore path article nntp- xref macro index \eb '/~B ' 'search entire message' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /pkg/mutt-1.3.25/libdata/mutt-1.3.25/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /pkg/mutt-1.3.25/libdata/mutt-1.3.25/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /pkg/mutt-1.3.25/libdata/mutt-1.3.25/manual.txt\n"" ""Show Mutt documentation"" set hostname=panix.com set abort_unmodified=no set alias_file=""~/.muttaliases"" set alternates=""aahz@pobox.com|aahz@panix*"" set arrow_cursor=yes set ascii_chars=yes set attribution=""On %d, %n wrote:\n>"" set beep=no set confirmappend=no set date_format=""!%a, %b %d, %Y"" set delete=yes set fast_reply=yes set fcc_attach=no set forward_format=""FWD: %s"" set forward_quote=yes set honor_followup_to=ask-yes set include=ask-yes set index_format=""%S%3C %{%b %d} %-17.17L %4l %s"" set mime_forward=ask-no set pager_context=2 set pager_index_lines=0 set pager_stop=yes set postpone=ask-no set postponed=""~/Mail/POSTPONED"" set print=no set record=""~/Mail/sent"" set reply_to=yes set reverse_alias=yes set save_empty=no set save_name=yes set sort=reverse-date set status_on_top=yes set tmpdir=""/var/tmp"" set to_chars="" +++ L"" set wait_key=yes --- End /net/u/1/a/aahz/.muttrc --- Begin /pkg/mutt-1.4.1/etc/conf/mutt/mutt-1.4.1/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /pkg/mutt-1.4.1/libdata/mutt-1.4.1/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /pkg/mutt-1.4.1/libdata/mutt-1.4.1/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /pkg/mutt-1.4.1/libdata/mutt-1.4.1/manual.txt\n"" ""Show Mutt documentation"" set hostname=panix.com set tmpdir=""/var/tmp"" --- End /pkg/mutt-1.4.1/etc/conf/mutt/mutt-1.4.1/Muttrc >How-To-Repeat: >Fix: }}}" aahz@… 2017 "mutt_addr_is_user() ""null address is assumed to be the user""" mutt 1.5.9 defect mutt-dev new 2005-08-01T04:35:55-07:00 2009-06-30T07:40:33-07:00 "{{{ In alias.c, mutt_addr_is_user(): > /* NULL address is assumed to be the user. */ > if (!addr) > { > dprint (5, (debugfile, ""mail_addr_is_user: yes, NULL address\n"")); > return 1; > } This causes a strange effect: A message with no headers is shown as sent from me, on the index menu. I'm afraid mutt_addr_is_user() is misused at almost all its occurences. We should not assume that env->from matches $alternates just because mutt_addr_is_user(env->from) returns 1. Why not return 0? >How-To-Repeat: Delete FROM header of a message. The message will be flagged as ""F"" with the default $to_chars and $index_format. >Fix: Simply return 0? But that could have side effects. }}}" ttakah@… 2041 pgp-inline failure mode should detect incorrect password crypto 1.5.x defect mutt-dev new 2005-08-16T17:38:34-07:00 2007-04-07T14:37:11-07:00 "When attempting to send a mail encrypted ""inline"", if you type in the wrong pgp passphrase, mutt will ask if you would like to fall back to sending it via pgp-MIME. This is a silly question if all you did was type in the wrong password. Mutt should be able to tell that the passphrase was incorrect and it wasn't a case of pgp-inline being incapable of signing the mail. I think this is a bug and not a change request, but I may be wrong. >How-To-Repeat: Compose a text message, set it to be sent via pgp-inline, then type in the wrong passphrase. >Fix: Unknown" kyle-mutt-dev@… 2057 Mutt displays my IMAP folders as mail/ in the folder browser IMAP 1.4.2.1i defect mutt-dev new 2005-09-06T20:04:47-07:00 1969-12-31T16:00:00-08:00 "{{{ I access my Harvard mail account with folder=imap://math.harvard.edu This puts me in the home directory by default. All my folders are in the mail/ subdirectory, so I set imap_home_namespace=""mail"" If imap_list_subscribed is set, then my folders, aside from INBOX, are displayed in the folder browser each as ""mail/"", i.e. as a directory, and the contents of each is the contents of my mail/ subdirectory, i.e. the folders I wanted displayed. If imap_list_subscribed is unset, then the folders are displayed correctly (i.e. with their leading directory stripped) but of course now I don't have folder subscriptions so I get other junk instead; in this case, I get a folder called ~/, which leads to my home directory, which contains nothing of interest to an IMAP client. More bizarrely still. If I try to circumvent the imap_home_namespace problem by setting folder=imap://math.harvard.edu/mail (and unsetting spoolfile so that it looks for INBOX in the correct place, /var/mail), then the folders display correctly but INBOX is not shown in the folder browser, which makes it inconvenient to reselect it after changing folders. I get the picture that mutt's handling of these options does the following: when imap_home_namespace is set, mutt issues the LIST command with LIST ""$imap_home_namespace"" * which, naturally, returns in my case (imap_home_namespace=""mail"") lines of the form LIST ""/"" mail/sent-mail Mutt is then intelligent enough to trim the path for $imap_home_namespace. HOWEVER, if imap_list_subscribed is set, mutt apparently forgets to trim $imap_home_namespace from the results of LSUB (returned in the same spirit), leading to spurious displays of the same subdirectory which are shown in complete violation of the intent of the imap_home_namespace variable. Now, I don't want to make baseless accusations. So I checked the source, and from what I can tell, Mutt treats LIST and LSUB exactly the same. Hmm, maybe it's the server; the source certainly is littered with comments about inconsistent behavior among servers. So I ssh into math.harvard.edu and run imapd locally (this is how we do things, for whatever reason) and simply issue the commands myself. They return the following intriguing data: 1 LIST ""mail"" * * LIST (\NoSelect) ""/"" mail * LIST (\NoInferiors \Marked) ""/"" mail/sent-mail * LIST (\NoInferiors \Marked) ""/"" mail/saved-messages 2 LSUB ""mail"" * * LSUB () ""/"" mail/saved-messages * LSUB () ""/"" mail/sent-mail I suspect, therefore, that this is falling afoul of the workaround indicated in the comment starting line 142: it asks for just folder (in this case ""mail"") and tries to tack on the delimeter, but in fact the code in the block starting at line 106 didn't even find a folder, since LSUB didn't return it. Therefore we never change folders and everything shows up one level removed from where it's supposed to. Just to check, I subscribe to ""mail"". All better. This is clearly a one-time bug, but extremely vexing and hard to diagnose (I had to read the source for this?!). One should not have to subscribe to a folder to see its subscribed-to contents when they are explicitly requested (especially since mutt DOES display them...incorrectly). The solution is to use LIST always, rather than LIST or LSUB, in the 106 block. Just my two cents. >How-To-Repeat: >Fix: See above: in short, the folder in question should be subscribed to. }}}" reich@… 2059 "Mutt sometimes(!) cannot connect to imaps saying ""Interrupted system call""" IMAP 1.5.10 defect mutt-dev reopened 2005-09-07T04:08:44-07:00 2006-09-23T12:12:39-07:00 "{{{ Most of the time (9 of 10 attempts) I try to connect to my imaps I get ""Cannot connect to .ru (Interrupted system call)"" and mutt aborts. Older mutts sometimes showed this problem too, but much more rarely. Server is available. I can run another IMAP client without a hitch. Besides, ""Interrupted system call"" is not what we usually get on refused connection... >How-To-Repeat: >Fix: Unknown }}}" alex@… 2118 pager line sometimes not reset display defect mutt-dev new 2005-10-24T09:56:15-07:00 2009-06-30T07:44:25-07:00 "{{{ under relatively rare circumstances i was not able to isolate, yet, the line offset of the pager is not reset when viewing a new message. >How-To-Repeat: >Fix: }}}" ossi@… 2222 gpgme - diffence in key selection crypto cvs defect mutt-dev new 2006-05-04T11:38:55-07:00 2009-06-30T07:44:11-07:00 "{{{ I have noticed a difference in gpg key selection (using gpgme and mutt cvs) for the recipient ""xxx@domain"" versus """". This is my example: > gpg --list-keys Pleiner pub 1024D/613C21EA 2001-07-30 uid Alex Pleiner uid Alex Pleiner uid Alex Pleiner uid Alex Pleiner sub 1024g/2C55D552 2001-07-30 If I compose an e-mail to ""alex@zeitform.de"" I will not be asked for the recipient key. The correct one is automatically selected. If I write to ""Alex Pleiner "" or even "" I get to the pgp menu with all those above entries and have to manually select the right one. Is this correct behaviour? Feature or bug? This does not happen if I disable gpgme. >How-To-Repeat: encrypt mail to recipient with multiple subkeys (e-mail addresses) via gpgme an use backets around recipient address. >Fix: Unknown }}}" alex-mutt@… 2456 some S/MIME smime_keys.pl add_p12 failures crypto 1.5.13 defect mutt-dev new 2006-08-30T04:06:14-07:00 2009-06-30T07:43:38-07:00 "{{{ Hello, The S/MIME helper Perl script smime_keys.pl has some small problems, needing Perl skilled helpers. -1) add_p12 creates and unlinks temp files in the directory of pkcs12 original certificates. It could destroy important file unluckily named something.pem, or fail if readonly: | $ ./smime_keys add_p12 readonly-keys-container/cert.p12 | | NOTE: This will ask you for two passphrases: | 1. The passphrase you used for exporting | 2. The passphrase you wish to secure your private key with. | | Error opening output file readonly-keys-container/cert.p12.pem | readonly-keys-container/cert.p12.pem: Permission denied | '/usr/bin/openssl pkcs12 -in readonly-keys-container/cert.p12 -out \ | readonly-keys-container/cert.p12.pem' returned 256 at ./smime_keys line 111. -2) Fails when filenames have spaces: | $ ./smime_keys add_p12 ""My certificate.p12"" | | NOTE: This will ask you for two passphrases: | 1. The passphrase you used for exporting | 2. The passphrase you wish to secure your private key with. | | Usage: pkcs12 [options] | where options are [snip OpenSSL options] | '/usr/bin/openssl pkcs12 -in My certificate.p12 -out My certificate.p12.pem' \ | returned 256 at ./smime_keys line 111. -3) Fails when the p12 file contains only client cert (and private key). May seem a justified failure: Lacking path to root CA. But the issuer's cert is in fact present in the database, in both .smime/certificates and ca-bundle. | $ ./smime_keys add_p12 simple.p12 | | NOTE: This will ask you for two passphrases: | 1. The passphrase you used for exporting | 2. The passphrase you wish to secure your private key with. | | Enter Import Password: | MAC verified OK | Enter PEM pass phrase: | Verifying - Enter PEM pass phrase: | Couldn't identify root certificate! | No root and no intermediate certificates. Can't continue. at ./smime_keys line 662. -4) The /usr/bin/openssl command path is hardcoded. It fails if OpenSSL is installed in /usr/local/bin/ or elsewhere. -5) Verification of a database certificate againt a revocation list fails (grep returns non-0 when there is no match): | $ ./smime_keys verify 12345678.0 revoke.x509 | | ==> about to verify certificate of email@example.com | | /tmp/.smime/certificates/12345678.0: OK | '/usr/bin/openssl crl -text -noout -in revoke.x509 | grep -A1 123456789ABCDEF123456789ABCDEF12 | ' returned 256 at ./smime_keys line 875, chunk 1. Bye! Alain. >How-To-Repeat: >Fix: }}}" Alain Bench 2851 "cannot attach files in dirs with a ""cur"" subdirectory" browser defect mutt-dev new 2007-03-16T13:25:02-07:00 2009-06-30T07:43:27-07:00 "{{{ This is a pretty weird one, but anyway, it's a bug... ----- Forwarded message from Thomas Poindessous = ----- Date: Wed, 29 Jan 2003 12:04:24 +0100 From: Thomas Poindessous Reply-To: Thomas Poindessous , 178899@bugs.debian.org To: Debian Bug Tracking System Subject: Bug#178899: mutt: When adding a attachment, I can't go in a dire= ctory which name is less than 4 char long Package: mutt Version: 1.5.3-1 Severity: normal Hi, when I wnat to add a attachment, I can't go in a directory which name is less than 4 char long. For example, I want to add the file : /tmp/t/cur/toto and find /tmp/t/ : /tmp/t /tmp/t/cur /tmp/t/cur/toto so there is only one file. I can't go to /tmp/t/cur [...] ----- End forwarded message ----- ----- Forwarded message from Thomas Poindessous = ----- Date: Wed, 29 Jan 2003 15:28:18 +0100 From: Thomas Poindessous Reply-To: Thomas Poindessous , 178899@bugs.debian.org To: Marco d'Itri , 178899@bugs.debian.org Subject: Bug#178899: mutt: When adding a attachment, I can't go in a dire= ctory which name is less than 4 char long On Wednesday 29 January 2003 13:46, Marco d'Itri wrote: > tag 178899 unreproducible moreinfo > thanks > > On Jan 29, Thomas Poindessous wrote: > >when I wnat to add a attachment, I can't go in a directory which name= is > >less than 4 char long. > > I cannot reproduce this. In fact, I found the bug. The directory is named cur, and mutt tried to determine if it's a maildir= or=20 not. (it is, in fact) To me, it seems that the test in mx.c:390 snprintf (tmp, sizeof (tmp), ""%s/cur"", path); if (stat (tmp, &st) =3D=3D 0 && S_ISDIR (st.st_mode)) return (M_MAILDIR); doesn't work, I tried to put a breakpoint on the ""if ..."" line with ddd, = and=20 it doesn't work. In this case, it should return M_MAILDIR --=20 Thomas Poindessous ----- End forwarded message ----- ----- Forwarded message from Adeodato Sim=F3 ----- Date: Sun, 23 May 2004 21:36:30 +0200 From: Adeodato Sim=F3 Reply-To: Adeodato Sim=F3 , 178899@bugs.debian.org To: Thomas Poindessous , 178899@bugs.debian.org Subject: Bug#178899: mutt: When adding a attachment, I can't go in a dire= ctory which name is less than 4 char long * Thomas Poindessous [Wed, 29 Jan 2003 15:28:18 +0100]: > In fact, I found the bug. > The directory is named cur, and mutt tried to determine if it's a maild= ir or=20 > not. (it is, in fact) > To me, it seems that the test in mx.c:390 > snprintf (tmp, sizeof (tmp), ""%s/cur"", path); > if (stat (tmp, &st) =3D=3D 0 && S_ISDIR (st.st_mode)) > return (M_MAILDIR); > doesn't work, I tried to put a breakpoint on the ""if ..."" line with ddd= , and=20 > it doesn't work. In this case, it should return M_MAILDIR mmm, it *does* work. if it exists dir/cur, mutt thinks it's a maildir and it won't let you browse it as a normal folder. if you want to attach a message, you can use the attach message (binded to 'A' key) function. real trouble is when you have a directory (not a maildir) with a directory named 'cur' under it. but that seems odd. what do we do with this bug? --=20 Adeodato Sim=F3 EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 =20 Under capitalism, man exploits man. Under communism, it's just the opposite. -- J.K. Galbraith ----- End forwarded message ----- Christoph --=20 cb@df7cb.de | http://www.df7cb.de/ >Fix: Unknown }}}" Christoph Berg 2855 macro handled as multiple keys makes status bar useless mutt hg tip defect mutt-dev new 2007-03-22T06:05:13-07:00 2007-03-27T16:06:33-07:00 notifications about (async) events are always shown between two iterations of the main loop (i guess), usually two keypresses. i was never a fan of this, but here's a case where it actually fails: when you have a macro that resolves to multiple simulated key presses, you might see nothing more than a flash (if anything) in the status bar, because a message appears and disappears during the replay of the macro. ossi@… 49 mutt: confirmation on deleted attachements mutt enhancement mutt-dev new 2000-02-24T11:44:23-08:00 2005-07-31T22:12:21-07:00 "{{{ Package: mutt Version: 1.0pre4-1 Severity: wishlist [NOTE: this bug report has been submitted to the debian BTS as Bug#48477. Please Cc all your replies to 48477@bugs.debian.org.] From: Ulf Jaenicke-Roessler Subject: mutt: confirmation on deleted attachements Date: Wed, 27 Oct 1999 17:03:22 +0200 Hi, mutt doesn't ask for confirmation before it stores mails into mailboxes after attachements were deleted. IMHO it should do so, in order to prevent accidential data loss. Thanks, Ulf -- System Information Debian Release: potato Kernel Version: Linux pkfp20 2.2.13 #1 Tue Oct 26 11:11:53 CEST 1999 i586 unknown Versions of the packages mutt depends on: ii libc6 2.1.2-6 GNU C Library: Shared libraries and timezone ii libncurses4 4.2-3.4 Shared libraries for terminal handling ii exim 3.03-1 Exim Mailer ^^^ (Provides virtual package mail-transport-agent) >How-To-Repeat: >Fix: }}}" """Marco d'Itri"" " 64 mutt: set reply-to on commandline mutt enhancement mutt-dev new 2000-03-04T04:19:30-08:00 2005-08-06T13:19:29-07:00 "{{{ Package: mutt Version: 1.0.1-9 Severity: wishlist Hi, It would be nice if it were able to set the Reply-To header on the commandline in mutt, and have this address be subject to alias expansion. The REPLYTO environment variable is not subject to alias expansion, nor is setting a ""my_hdr Reply-To: foo"" as a -e flag to mutt. I added a -r commandline switch. Here's my patch to the mutt 1.1.7i source: diff -durN mutt-1.1.7/doc/manual.sgml mutt-1.1.7-hacked/doc/manual.sgml --- mutt-1.1.7/doc/manual.sgml Wed Mar 1 01:19:52 2000 +++ mutt-1.1.7-hacked/doc/manual.sgml Fri Mar 3 18:26:17 2000 @@ -2598,6 +2598,7 @@ -n do not read the system Muttrc -m specify a default mailbox type -p recall a postponed message +-r specify a reply-to (Reply-To) address -R open mailbox in read-only mode -s specify a subject (enclose in quotes if it contains spaces) -v show version number and compile-time definitions diff -durN mutt-1.1.7/doc/mutt.man mutt-1.1.7-hacked/doc/mutt.man --- mutt-1.1.7/doc/mutt.man Tue Feb 1 19:44:04 2000 +++ mutt-1.1.7-hacked/doc/mutt.man Fri Mar 3 18:17:02 2000 @@ -34,6 +34,7 @@ [-H \fIdraftfile\fP] [-i \fIinclude\fP] [-m \fItype\fP] +[-r \fIaddress\fP] [-s \fIsubject\fP] .SH DESCRIPTION .PP @@ -68,6 +69,8 @@ Causes Mutt to bypass the system configuration file. .IP ""-p"" Resume a postponed message. +.IP ""-r"" +Specify a reply-to (Reply-To) address. .IP ""-R"" Open a mailbox in \fIread-only\fP mode. .IP ""-s \fIsubject\fP"" @@ -102,7 +105,7 @@ .IP ""TMPDIR"" Directory in which temporary files are created. .IP ""REPLYTO"" -Default Reply-To address. +Default Reply-To address. Overrules -r flag. .IP ""VISUAL"" Editor to invoke when the ~v command is given in the builtin editor. .SH FILES diff -durN mutt-1.1.7/main.c mutt-1.1.7-hacked/main.c --- mutt-1.1.7/main.c Thu Feb 24 22:24:36 2000 +++ mutt-1.1.7-hacked/main.c Fri Mar 3 18:19:29 2000 @@ -117,6 +117,7 @@ -m \tspecify a default mailbox type\n\ -n\t\tcauses Mutt not to read the system Muttrc\n\ -p\t\trecall a postponed message\n\ + -r\t\tspecify a reply-to (Reply-To) address\n\ -R\t\topen mailbox in read-only mode\n\ -s \tspecify a subject (must be in quotes if it has spaces)\n\ -v\t\tshow version and compile-time definitions\n\ @@ -360,7 +361,7 @@ memset (Options, 0, sizeof (Options)); memset (QuadOptions, 0, sizeof (QuadOptions)); - while ((i = getopt (argc, argv, ""a:b:F:f:c:d:e:H:s:i:hm:npRvxyzZ"")) != EOF) + while ((i = getopt (argc, argv, ""a:b:F:f:c:d:e:H:s:i:hm:npr:RvxyzZ"")) != EOF) switch (i) { case 'a': @@ -378,12 +379,15 @@ case 'b': case 'c': + case 'r': if (!msg) msg = mutt_new_header (); if (!msg->env) msg->env = mutt_new_envelope (); if (i == 'b') msg->env->bcc = rfc822_parse_adrlist (msg->env->bcc, optarg); + else if (i == 'r') + msg->env->reply_to = rfc822_parse_adrlist (msg->env->reply_to, optarg); else msg->env->cc = rfc822_parse_adrlist (msg->env->cc, optarg); break; diff -durN mutt-1.1.7/send.c mutt-1.1.7-hacked/send.c --- mutt-1.1.7/send.c Thu Feb 17 19:20:16 2000 +++ mutt-1.1.7-hacked/send.c Fri Mar 3 18:20:13 2000 @@ -1043,6 +1043,7 @@ msg->env->to = mutt_expand_aliases (msg->env->to); msg->env->cc = mutt_expand_aliases (msg->env->cc); msg->env->bcc = mutt_expand_aliases (msg->env->bcc); + msg->env->reply_to = mutt_expand_aliases (msg->env->reply_to); } else { Patching as patch -p1 < patchfile in the mutt source gives the -r flag. BTW, on Tue, 28 Dec 1999 17:36:40 +0100, I posted an earlier version of this patch on mutt-dev@mutt.org. I need this feature to get my work done. Hope this is of any use to someone else also :) Bye, Joost van Baal -- System Information Debian Release: 2.2 Kernel Version: Linux nagy 2.2.12 #1 Wed Sep 1 11:43:20 CEST 1999 i686 unknown >How-To-Repeat: >Fix: }}}" Joost van Baal 215 ! and % in full name should be quoted MIME 1.2.4i enhancement mutt-dev new 2000-08-02T15:09:04-07:00 2009-06-30T07:43:16-07:00 "{{{ Package: mutt Version: 1.2.4i Severity: wishlist -- Please type your report below this line If I need to send mail to someone with a ! or % in the full name, mutt does not automatically quote the full name. This causes minor problems in some systems. The ! and % characters are not specials according to RFC 822. However, they are still used in some environments, and some mailers will try to parse such addresses. The mailers may get a little bit confused when presented with unquoted ! or % characters in the full name. I can't find any RFC that says ! or % should be quoted in the full name part. Therefore I think this is only a feature request. -- Mutt Version Information Mutt 1.2.4i (2000-07-07) Copyright (C) 1996-2000 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.0.36 [using ncurses 5.0] Compile options: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP -USE_GSS -USE_SSL +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -ENABLE_NLS SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/spool/mail"" SHAREDIR=""/.software/share/mutt-1.2.4/data"" SYSCONFDIR=""/.software/share/mutt-1.2.4/config"" ISPELL=""/usr/bin/ispell"" To contact the developers, please mail to . To report a bug, please use the muttbug utility. >How-To-Repeat: >Fix: }}}" acli@… 257 Support for gzipped mail boxes? mutt 1.2.5i enhancement mutt-dev new 2000-09-02T01:41:29-07:00 2005-07-31T22:24:42-07:00 "{{{ Package: mutt Version: 1.2.5-1 Severity: wishlist -- Please type your report below this line Hi, I snipped this bug report's extra info, because this is simply a feature request. I would love to see transparent support for gzipped folders. This is basically so that I can keep a couple of months' archive of e.g. debian-devel mailing list, which generates a lot of traffic, without wasting too much space on my disk. (If this is already implemented, interpret this as a bug about documentation. ;) Hugo van der Merwe -- System Information Debian Release: woody Kernel Version: Linux gorilla 2.2.17 #1 Sun Jul 30 16:57:39 SAST 2000 i686 unknown To contact the developers, please mail to . To report a bug, please use the muttbug utility. >How-To-Repeat: >Fix: }}}" Hugo van der Merwe 261 comments in alias files are not shown in alias menue mutt 1.2.5i enhancement mutt-dev new 2000-09-04T09:38:04-07:00 2005-08-06T13:21:05-07:00 "{{{ Package: mutt Version: 1.2.5i Severity: wishlist -- Please type your report below this line Dear mutt developers, this is a wish. It is possible to add comments in an alias file like this: jd John Doe Never met that guy or like this: jd John Doe (Never met that guy) but when it comes to composing email these comments are not in the list shown when one hits ^i at the To:-prompt. It would be nice to see the comments especially when mailing to a person you do not know very well but e.g. their function in a organisation... Ciao, Gregor -- Mutt Version Information Mutt 1.2.5i (2000-07-28) Copyright (C) 1996-2000 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.2.13-12 [using ncurses 5.0] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK -USE_FCNTL +USE_FLOCK -USE_IMAP -USE_GSS -USE_SSL -USE_POP -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/spool/mail"" SHAREDIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" ISPELL=""/usr/bin/ispell"" To contact the developers, please mail to . To report a bug, please use the muttbug utility. >How-To-Repeat: >Fix: }}}" Gregor Zattler 333 mutt: pgp/gpg headers - Content-Disposition (wishlist) mutt enhancement mutt-dev new 2000-10-28T08:25:59-07:00 2005-08-06T13:24:09-07:00 "{{{ Package: mutt Version: 1.2.5-1 Severity: wishlist [NOTE: this bug report has been submitted to the debian BTS as Bug#75701. Please Cc all your replies to 75701@bugs.debian.org.] From: Tuomas Heino Subject: mutt: pgp/gpg headers - Content-Disposition (wishlist) Date: Fri, 27 Oct 2000 11:59:23 +0300 Some other MUA users have been complaining about the following headers a bit: --+pHx0qQiF2pBVqBT Content-Type: application/pgp-encrypted Content-Disposition: inline; filename=""msg.asc"" Version: 1 --+pHx0qQiF2pBVqBT Content-Type: application/octet-stream Content-Disposition: inline -----BEGIN PGP MESSAGE----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org ... the real problem being that other MUA being stupid but ... Does giving the second Content-Disposition a filename sound doable or just plain silly? ;) (like Content-Disposition: inline; filename=""contents.asc"") -- System Information Debian Release: woody Kernel Version: Linux bx3 2.4.0-test9 #283 Wed Oct 4 21:20:52 EEST 2000 i686 unknown Versions of the packages mutt depends on: ii libc6 2.1.95-1 GNU C Library: Shared libraries and Timezone data ii libncurses5 5.0-4 Shared libraries for terminal handling ii exim 3.12-5 Exim Mailer ^^^ (Provides virtual package mail-transport-agent) >How-To-Repeat: >Fix: }}}" """Marco d'Itri"" " 345 mutt: saving/deleting a thread while in limited view doesn't work mutt enhancement mutt-dev new 2000-11-07T04:31:07-08:00 2005-09-04T11:21:31-07:00 "{{{ Package: mutt Version: 1.2-1 Severity: normal [NOTE: this bug report has been submitted to the debian BTS as Bug#76361. Please Cc all your replies to 76361@bugs.debian.org.] From: Toni Mueller Subject: mutt: saving/deleting a thread while in limited view doesn't work Date: 6 Nov 2000 09:18:35 -0000 Hello, when I view my messages limited to something and then tag a thread with 'ESC-t', the whole thread gets tagged. But when I subsequently try to save that thread to a mailbox (ie, ';s'), it does only save the messages in view and not the whole thread (at least if there is more than one thread selected). When I subsequently unlimit my view, I see only a part of the messages of a thread deleted. Imho this is inconsistent and confusing. Best Regards, --Toni++ -- System Information Debian Release: 2.2 Kernel Version: Linux oak 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i686 unknown Versions of the packages mutt depends on: ii libc6 2.1.3-13 GNU C Library: Shared libraries and Timezone ii libncurses5 5.0-6 Shared libraries for terminal handling ii exim 3.12-10 Exim Mailer ^^^ (Provides virtual package mail-transport-agent) >How-To-Repeat: >Fix: }}}" """Marco d'Itri"" " 395 my_hdr and Mixmaster mutt 1.2.5i enhancement mutt-dev new 2000-12-21T03:50:18-08:00 2005-10-04T21:49:26-07:00 "{{{ Package: mutt Version: 1.2.5-2 Severity: normal -- Please type your report below this line Mutt does not remove extra headers set with my_hdr when sending mail in Mixmaster mode. It should better drop _all_ unneeded headers. A header line like X-Request-PGP: URL-of-homepage might not be that good. -- System Information Debian Release: woody Kernel Version: Linux kasiski 2.2.14 #3 Tue Apr 18 16:50:01 CEST 2000 i586 unknown Versions of the packages mutt depends on: ii libc6 2.1.96-1 GNU C Library: Shared libraries and Timezone ii libncurses5 5.0-3 Shared libraries for terminal handling ii exim 3.16-7 Exim Mailer ^^^ (Provides virtual package mail-transport-agent) -- Mutt Version Information Mutt 1.2.5i (2000-07-28) Copyright (C) 1996-2000 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.2.14 [using ncurses 5.0] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP +USE_GSS +USE_SSL +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/spool/mail"" SHAREDIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" ISPELL=""/usr/bin/ispell"" To contact the developers, please mail to . To report a bug, please use the muttbug utility. >How-To-Repeat: >Fix: }}}" Werner Koch 406 wish $index_format %B displays narrower list addy or alias mutt 1.3.13i enhancement mutt-dev new 2001-01-01T18:45:59-08:00 2005-10-15T02:53:58-07:00 "{{{ Package: mutt Version: 1.3.13i Severity: wishlist -- Please type your report below this line It would be nice if the %B sequence in the index_format option could be used in conjunction with the subscribe and lists commands to match domains and other strings which do not appear at the start of email addresses. So if I receive email from: somelonglistname-abc@somewhere.net somelonglistname-xyz@somewhere.net somelongerlistname-xyz@somewhere.net I could match '-xyz' or '@somewhere.net' instead of 'somelonglistname' or 'somelongerlistname'. Furthermore, I like to keep my %B field as narrow as possible (currently five characters) and thus it's no good if the index displays: somel somel somel for each of the addresses shown above, respectively. My patches allow the parameters to the 'subscribe' command to match at places other than the start of email addresses. This is ONLY enabled if the option 'list_submatches' is set (by default it is not). Furthermore, when this option is set, only the portion of the email address occurring after the start of the match is shown in the %B field. So if I had the configuration line 'subscribe -xyz @somewhere.net' then my index would show somew -xyz@ -xyz@ for each of the addresses, respectively. Some moot points: - should the matching behaviour option be separate from the %B display option (currently both are affected/effected by the list_submatches option). - my patches elide a leading % or @ character. should they also remove a leading - character? That is, should the last triplet have been: @some -xyz@ -xyz@ or somew xyz@s xyz@s or somew -xyz@ -xyz@ As far as I can tell, my changes only affect the determination of whether an address matches a subscribed list and the display of the list name with the %B sequence. They do not interfere with the use of the list-reply option. Also note that the documentation patch mentions both the lists and subscribe commands. I'm new to mutt 1.3 so I don't understand much about the differences between these and my remarks may be confused. Also, check my /*...*/ comments for suitability. I use this patch myself, however I only use it in the way I expect, so there could be bugs ;) Index: protos.h =================================================================== RCS file: /home/roessler/cvs/mutt/protos.h,v retrieving revision 2.67 diff -u -r2.67 protos.h --- protos.h 2000/12/31 11:24:19 2.67 +++ protos.h 2001/01/01 10:01:48 @@ -201,6 +201,7 @@ void mutt_query_menu (char *, size_t); void mutt_safe_path (char *s, size_t l, ADDRESS *a); void mutt_save_path (char *s, size_t l, ADDRESS *a); +void mutt_save_path_s (char *s, size_t l, ADDRESS *a, int astart); void mutt_score_message (CONTEXT *, HEADER *, int); void mutt_select_fcc (char *, size_t, HEADER *); #define mutt_select_file(A,B,C) _mutt_select_file(A,B,C,NULL,NULL) Index: muttlib.c =================================================================== RCS file: /home/roessler/cvs/mutt/muttlib.c,v retrieving revision 2.34 diff -u -r2.34 muttlib.c --- muttlib.c 2000/10/10 19:22:45 2.34 +++ muttlib.c 2001/01/01 10:01:50 @@ -840,15 +840,23 @@ void mutt_save_path (char *d, size_t dsize, ADDRESS *a) { + mutt_save_path_s( d, dsize, a, 0 ); +} + +void mutt_save_path_s (char *d, size_t dsize, ADDRESS *a, int astart) +{ if (a && a->mailbox) { - strfcpy (d, a->mailbox, dsize); + char* addr = a->mailbox; + if ( astart > 0 && astart < (strlen(addr)-1) /* must have at least one char */ ) + addr += astart; /* should only occur if OPTLISTSUBMATCH is set */ + strfcpy (d, addr, dsize); if (!option (OPTSAVEADDRESS)) { char *p; if ((p = strpbrk (d, ""%@""))) - *p = 0; + *p = 0; } mutt_strlower (d); } Index: mutt.h =================================================================== RCS file: /home/roessler/cvs/mutt/mutt.h,v retrieving revision 2.88 diff -u -r2.88 mutt.h --- mutt.h 2000/12/31 11:24:19 2.88 +++ mutt.h 2001/01/01 10:01:50 @@ -336,6 +339,7 @@ OPTSSLSYSTEMCERTS, #endif OPTIMPLICITAUTOVIEW, + OPTLISTSUBMATCH, OPTMAILCAPSANITIZE, OPTMAILDIRTRASH, OPTMARKERS, Index: hdrline.c =================================================================== RCS file: /home/roessler/cvs/mutt/hdrline.c,v retrieving revision 2.23 diff -u -r2.23 hdrline.c --- hdrline.c 2000/10/17 15:10:51 2.23 +++ hdrline.c 2001/01/01 10:01:51 @@ -38,8 +38,22 @@ if (addr->mailbox) { for (;p; p = p->next) + { if (mutt_strncasecmp (addr->mailbox, p->data, mutt_strlen (p->data)) == 0) - return 1; + return 1; /* the character number of the start of the match */ + else + if ( option(OPTLISTSUBMATCH) ) + { + const char* match; + if ( ( match = mutt_stristr(addr->mailbox, p->data) ) != NULL ) /* is mutt_stristr the right thing to use?? */ + if ( *match == '%' || *match == '@' ) + match++; /* move past the % or @, so that we don't choose folder names starting with '@' or '%' */ + if ( match > addr->mailbox && match < (addr->mailbox+mutt_strlen(addr->mailbox) ) ) + { + return (int)((match-addr->mailbox)+1); /* the character number of the start of the match (1-based not 0-based) */ + } + } + } } return 0; } @@ -95,11 +109,12 @@ static int first_mailing_list (char *buf, size_t buflen, ADDRESS *a) { + int matchstart; /* see mutt_is_subscribed_list and mutt_save_path_s */ for (; a; a = a->next) { - if (mutt_is_subscribed_list (a)) + if ( (matchstart = mutt_is_subscribed_list (a)) != 0 ) { - mutt_save_path (buf, buflen, a); + mutt_save_path_s (buf, buflen, a, matchstart-1 /* convert char number into char index */ ); return 1; } } Index: init.h =================================================================== RCS file: /home/roessler/cvs/mutt/init.h,v retrieving revision 2.112 diff -u -r2.112 init.h --- init.h 2000/12/21 09:19:41 2.112 +++ init.h 2001/01/01 10:01:53 @@ -1398,6 +1406,20 @@ */ #endif + { ""list_submatches"", DT_BOOL, R_NONE, OPTLISTSUBMATCH, 0 }, + /* + ** .pp + ** When unset (the default) mutt will match lists and subscribes + ** only at the start of mail addresses. When set, values entered + ** through the lists and subscribe commands will match anywhere + ** in a mail address. When displayed in indices (eg. the %B + ** sequence) the partial match text will be displayed instead of + ** the full mail address. If an argument to one of the commands is + ** @xxx and there is a match then xxx will be displayed (instead + ** of @xxx). The first match is the one that will be displayed, + ** so put general matches at the end of your lists or subscribe + ** commands, not at the beginning. + */ { ""pipe_split"", DT_BOOL, R_NONE, OPTPIPESPLIT, 0 }, /* ** .pp -- Mutt Version Information Mutt 1.3.13i (2000-12-31) Copyright (C) 1996-2000 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: SunOS 5.8 [using ncurses 5.0] 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/local/bin/ispell"" SENDMAIL=""/usr/lib/sendmail"" MAILPATH=""/var/mail"" SHAREDIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" James Devenish 428 mutt: wishlist: request for mono attributes to be applied to color terminals display enhancement mutt-dev new 2001-01-16T11:04:27-08:00 2009-06-30T07:42:55-07:00 "{{{ Package: mutt Version: 1.3.12-2 Severity: wishlist [NOTE: this bug report has been submitted to the debian BTS as Bug#82474. Please Cc all your replies to 82474@bugs.debian.org.] From: Jeff Sheinberg Subject: mutt: wishlist: request for mono attributes to be applied to color terminals Date: Mon, 15 Jan 2001 19:15:18 -0500 (EST) Hi, One should be able to apply all of the mono attributes to any terminal that supports them, eg, `brightdefault default reverse' would give inverse bold using the default colors. I know that my terminal can do this, since, eg, nvi writes its error messages in inverse bold. I think the an easy way to do this would to be able to set and unset the mono attributes cumulatively, and have them apply to any terminal that can support them, eg, bold + underline on a Debian xterm. Thanks, -- Jeff Sheinberg --- Begin /home/jeff/.muttrc unset bounce_delivered unset help # set it to turn top status bar back on set folder=""~/.Mail"" set header set move=ask-yes bind editor ""\ch"" backward-char ## bug broken ## bind editor ""\c?"" backspace ## bug broken ## bind editor """" delete-char bind editor ""\ct"" transpose-chars bind editor ""\e"" kill-word ignore * unignore from: sender: to: date: x-loop: x-been-there: user-agent: unignore x-mailer: subject: apparentely-to: x-zippy-says: unhdr_order * hdr_order from: sender: to: date: x-loop: x-been-there: user-agent: hdr_order x-mailer: subject: apparentely-to: x-zippy-says: color hdrdefault brightdefault default color header default default .* color indicator default white color markers default default color signature default default color status default white --- End /home/jeff/.muttrc -- System Information Debian Release: 2.3-woody-testing Kernel Version: Linux eden-hda7.my.local 2.2.18 #1 Fri Jan 12 21:23:37 EST 2001 i586 unknown Versions of the packages mutt depends on: ii libc6 2.2-6 GNU C Library: Shared libraries and Timezone ii libncurses5 5.0-6.0potato1 Shared libraries for terminal handling ii libsasl7 1.5.24-4.1 Authentication abstraction library. ii postfix 0.0.20000531.S A high-performance mail transport agent ^^^ (Provides virtual package mail-transport-agent) >How-To-Repeat: >Fix: }}}" """Marco d'Itri"" " 442 better color control (wishlist) mutt 1.2.5i enhancement mutt-dev new 2001-01-28T03:03:02-08:00 2005-08-08T12:54:00-07:00 "{{{ Package: mutt Version: 1.2.5i Severity: wishlist -- Please type your report below this line Mutt needs better color control. For example, take the index. There's no way to make the indicator bar only change the background (to, say, blue) so that the foreground colors stay the same (including seperate colors for the tree markers, etc). There should also be ways to only change one or the other color attribute, and there should be ways to modify color attributes (eg, I want ""bright"" added to all colors when a message is addressed to me). Perhaps a more uniform scheme (adding patterns and regexps to everything, not having special cases for ""index"" colors) is in order. Just an idea. -- Mutt Version Information Mutt 1.2.5i (2000-07-28) Copyright (C) 1996-2000 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.0 [using ncurses 5.2] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP -USE_GSS +USE_SSL +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" SHAREDIR=""/usr/share/mutt"" SYSCONFDIR=""/usr/share/mutt"" -ISPELL To contact the developers, please mail to . To report a bug, please use the muttbug utility. >How-To-Repeat: >Fix: }}}" jim@… 624 """fcc-hook . +%F"" and ""save-hook . +%F"" behave different: fcc pre-pends ""To """ mutt 1.3.17i enhancement mutt-dev new 2001-05-26T07:36:35-07:00 2005-08-18T12:15:02-07:00 "{{{ Package: mutt Version: 1.3.17i (2001-03-28) Severity: wishlist -- Please type your report below this line This Problem occurs in all Versions of mutt: Saving a message using ""save-hook . +%F"" saves it to +""Real Name"" Sending a message using ""fcc-hook . +%F"" saves/fccs it to +""To Real Name"" ^^^ This is annoying, because this ""feature"" makes it impossible to use threads in correspondences. The manual states: ""%F author name, or recipient name if the message is from you"" but this is obviously wrong. As a work around i use dozends of lines like this in my muttrc: fcc-save-hook 'texmex@uni.de' +'Gregor Zattler' But every time i write or reply to a new person i have to do this *before* writing and source the muttrc. As a matter of fact i don't do this and end up having dozends of ""To Real Name"" mail folders and ""Real Name"" mail folders. As a consequence i cannot read a whole correspondence but only my or the recipient's part of it. I think %F is established with this behavior. So the solution would be to add a new printf() -like sequence ""%R"" which does the trick. Or to add a ""%r"" printf() -like sequence which does for the recipient what ""%n"" does for the author"": %n author's real name (or address if missing) %r recipient's real name (or address if missing) This would make mutt much more useable for me because i communicate with persons not with email addresses. Ciao, Gregor -- Mutt Version Information Mutt 1.3.17i (2001-03-28) Copyright (C) 1996-2000 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.2.18pre21 [using ncurses 5.0] 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=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" SHAREDIR=""/usr/local/stow/mutt//share/mutt"" SYSCONFDIR=""/usr/local/stow/mutt//etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" Gregor Zattler 655 color-only markers for line wrap indicators display enhancement mutt-dev new 2001-06-11T00:32:55-07:00 2009-06-30T07:52:00-07:00 "{{{ Package: mutt Version: 1.2.5-4 Severity: wishlist It would be really nice if when combining 'unset markers' and 'set smart_wrap' the color for markers was applied to the first character in the wrapped line still. This would make it easy to see when lines are being wrapped (on color terminals anyway) but not interfere with the ability to easily cut and paste chunks of wrapped text without extraneous characters. The old behavoir could ofcourse be simulated by setting the marker color to the color of normal text, should someone find this new behavior undesireable. -- Jamie Heilman http://audible.transient.net/~jamie/ ""Most people wouldn't know music if it came up and bit them on the ass."" -Frank Zappa >How-To-Repeat: >Fix: }}}" Jamie Heilman 663 IMAP should only download (large) attachments when they are viewed IMAP 1.3.19i enhancement mutt-dev new 2001-06-19T15:36:09-07:00 2007-02-07T10:06:23-08:00 "{{{ Package: mutt Version: 1.3.19i Severity: wishlist -- Please type your report below this line The IMAP code currently downloads the entire message (via BODY) when the message is read. This includes any attachments. It would be cool if mutt could use BODYSTRUCTURE to determine whether there are attachments, their MIME type and their size. Those that can be viewed inline could be downloaded and displayed; those that require an external viewer could be left on the server until requested by the user. This would be useful if there are large attachments or if the IMAP server is on the other end of a low bandwidth link. -- Mutt Version Information Mutt 1.3.19i (2001-06-07) 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.2.12-20 [using ncurses 4.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=""/usr/sbin/sendmail"" MAILPATH=""/var/spool/mail"" PKGDATADIR=""/opt/share/mutt"" SYSCONFDIR=""/opt/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" sit@… 680 Opening/searching several folders at once mutt enhancement mutt-dev new 2001-07-03T20:02:41-07:00 2005-09-05T16:16:53-07:00 "{{{ Package: mutt Version: 1.3.19i Severity: wishlist I use a different folder each month for my archived mail. From time to time, I find myself looking for an email and I remember that I sent it say in the last quarter of 1999. I then have to do run a limit command on each of the folders until I find what I am looking for. If the period of time is long, I concatenate all the folders into one and open this temporary folder. A great feature would be to be able to tag several folders and open them and do a search on them all at once. Thanks. :-) This would also be useful in order to tag and reply to multiple messages at once when they sit in different folders. Regards, Hugo -- Hugo Haas - http://larve.net/people/hugo/ Everybody gotta wear clothes, and if you don't, you get arrested. -- Mr. T >How-To-Repeat: >Fix: }}}" Hugo Haas 795 "mutt shows ""T"" in index even when the other recipient is the sender" mutt 1.3.22.1i enhancement mutt-dev new 2001-09-25T22:57:46-07:00 2005-09-04T11:26:07-07:00 "{{{ Package: mutt Version: 1.3.22.1i Severity: wishlist -- Please type your report below this line When a sender puts his From: address on the Cc: list, and there is no other recipient besides the mutt user, in the index, the letter ""T"" appears next to the message. It'd be nice if mutt recognized the sender Cc'd himself and displayed a ""+"", ""L"" or "" "" (depending on context) instead of the ""T"". -- Mutt Version Information Mutt 1.3.22.1i (2001-08-30) Copyright (C) 1996-2001 Michael R. Elkins und andere. Mutt übernimmt KEINERLEI GEWÄHRLEISTUNG. Starten Sie `mutt -vv', um weitere Details darüber zu erfahren. Mutt ist freie Software. Sie können es unter bestimmten Bedingungen weitergeben; starten Sie `mutt -vv' für weitere Details. System: Linux 2.4.10-ma1 [using ncurses 5.0] Einstellungen bei der Compilierung: -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=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER Um die Entwickler zu kontaktieren, schicken Sie bitte eine Nachricht (in englisch) an . Um einen Bug zu melden, verwenden Sie bitte das Programm flea(1). >How-To-Repeat: >Fix: }}}" ma@… 855 Add comment about PGP/MIME formatted messages in messag preamble mutt 1.3.23.1i enhancement mutt-dev new 2001-11-04T04:37:50-08:00 2005-09-04T11:34:31-07:00 "{{{ Package: mutt Version: 1.3.23.1i Severity: wishlist -- Please type your report below this line It would be nice if the PGP/MIME formatted messages carried a notice in their preamble (ie. before the first attachment) which says so. Something like This is a multi-part message in PGP/MIME format. See RFC 2015 for details. would suffice and would let those (poor) users of rfc2015-incapable mua's get a clue... -- 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/i486-suse-linux/2.95.2/specs gcc version 2.95.2 19991024 (release) - CFLAGS -Wall -pedantic -O2 -fomit-frame-pointer -I /usr/include/slang -- Mutt Version Information Mutt 1.3.23.1i (2001-10-31) 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.13 (i586) [using slang 10401] 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 SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""Mailbox"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/usr/share/mutt"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" AARG! Anonymous 885 storing number of new messages per box mutt 1.3.20i enhancement mutt-dev new 2001-11-21T14:44:43-08:00 2007-04-07T07:23:50-07:00 "{{{ Package: mutt Version: 1.3.20-1 Severity: wishlist -- Please type your report below this line hi, i think a great addition to mutt would be an integer associated with each mailbox, for storing hte number of new messages in it. it would be adjusted every time mail arrived or was read or deleted, and would provide the user with a high-level description of changes in mailboxes when they're choosing from the list. seeing that there are 46876 new bytes in a mailbox is not nearly as good as knowing that there are 2 new messages. of course, this could be taken farther: we could keep track of the number of messages in all different cases (new, unopened, replied, etc.). it would provide some very helpful folder listings. aaron brick. -- Mutt Version Information Mutt 1.3.20i (2001-07-24) 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.2.17 [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 +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" Aaron Brick 950 mutt: Better file navigation for attachments, folders browser enhancement mutt-dev new 2002-01-07T06:47:37-08:00 2009-06-30T07:51:37-07:00 "{{{ Package: mutt Version: 1.3.24-2 Severity: wishlist [NOTE: this bug report has been submitted to the debian BTS as Bug#126569. Please Cc all your replies to 126569@bugs.debian.org.] From: Ajay Shah Subject: mutt: Better file navigation for attachments, folders Date: Thu, 27 Dec 2001 07:59:20 +0530 --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Package: mutt Version: 1.3.24-2 Severity: wishlist Currently, when we use ""c"" to change folders or ""a"" to add attachments, mutt puts us in a textmode file navigator, using which the folder or file are selected. Every time ""c"" or ""a"" are used, mutt remembers the directory where it was last, and continues from there. My mail folders all like in $HOME/Mail. My attachments lie all over the place (e.g. I often process stuff in /tmp and then send it off). Every time this happens, I painfully go from /tmp to $HOME/Mail and vice versa, to flip between doing attachments or doing folders. I think my usage is fairly typical in these regards. Hence my wishlist for new features is: Wishlist 1: When doing ""a"" or ""c"" it should be possible to just type in a directory and get him to jump there. E.g. it's only five keystrokes ""/tmp"" to say I want to deal with /tmp. Currently I am forced to act like a Windows Moron (WM) and painfully navigate manually. Similarly, it should possible to type in ~/Mail and then continue from there using the file navigator. Wishlist 2: mutt should remember the directory where it was for ""a"", and track that separately. mutt should remember the directory where it was for ""c"", and track that separately. There should not be only one directory remembered for file navigati= on, but two. This way, my ""c"" would all endup being in $HOME/Mail. For ""a"" I would wander all over the place, but that's okay. Thanks, -ans. -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux sanna 2.4.17 #1 Tue Dec 25 01:11:29 IST 2001 i686 Locale: LANG=3DC, LC_CTYPE=3DC Versions of packages mutt depends on: ii exim 3.33-1 Exim Mailer ii exim [mail-transport-agen 3.33-1 Exim Mailer ii libc6 2.2.4-7 GNU C Library: Shared librarie= s an ii libncurses5 5.2.20010318-3 Shared libraries for terminal = hand ii libsasl7 1.5.27-2 Authentication abstraction lib= rary --=20 ---------------------------------------------------------------------------= ---- Ajay Shah ajayshah@mayin= .org Consultant, URL http://www.mayin.org/~ajay= shah Department of Economic Affairs, Ministry of Finance, New Delhi <*(:-? - wizard who doesn't know the an= swer --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8KoeASttXBLG4LuERArhOAJ9JzjmT3KB7JBiY0wJotP/OqAtThQCfZ2YW +o/SRmV/JcN0wXr2iGSM/j8= =FnlJ -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4-- >How-To-Repeat: >Fix: }}}" Marco d'Itri 949 mutt -Z should not clear the screen if there is no new mail mutt enhancement mutt-dev new 2002-01-07T06:48:31-08:00 2007-04-12T09:58:47-07:00 "[NOTE: this bug report has been submitted to the debian BTS as Bug!#127544. Please Cc all your replies to 127544@bugs.debian.org.] {{{ From: Gonzalo Paniagua Javier Subject: mutt: Behavior of the -Z option Date: Thu, 03 Jan 2002 00:06:58 +0100 }}} It would be nice if the -Z option simply shows the message saying that there are no mailboxes with new mail without clearing the screen first." Marco d'Itri 947 mutt: Use of tag-functions in pager mutt enhancement mutt-dev new 2002-01-07T06:48:50-08:00 2005-08-20T06:38:42-07:00 "{{{ Package: mutt Version: 1.3.24-2 Severity: wishlist [NOTE: this bug report has been submitted to the debian BTS as Bug#127957. Please Cc all your replies to 127957@bugs.debian.org.] From: Alexander Neumann Subject: mutt: Use of tag-functions in pager Date: Sun, 06 Jan 2002 01:07:56 +0100 Package: mutt Version: 1.3.24-2 Severity: wishlist I would like to apply actions to tagged messages even in the pager. Today, this isn't possible due to the nonexistance of this function in the pager. It would be nice to integrate that. Yours, Alexander -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux sigsegv 2.4.16 #4 Tue Dec 4 14:08:31 CET 2001 i686 Locale: LANG=en_US, LC_CTYPE=en_US Versions of packages mutt depends on: ii libc6 2.2.4-7 GNU C Library: Shared libraries an ii libncurses5 5.2.20010318-3 Shared libraries for terminal hand ii libsasl7 1.5.27-2 Authentication abstraction library ii postfix [mail-tr 0.0.20011115.SNAPSHOT-1 A high-performance mail transport >How-To-Repeat: >Fix: }}}" Marco d'Itri 1027 Wishlist: Change to sort/sort_aux choices mutt 1.3.25i enhancement mutt-dev new 2002-02-06T13:03:01-08:00 2005-08-25T10:36:56-07:00 "{{{ Package: mutt Version: 1.3.25-1 Severity: wishlist -- Please type your report below this line This is a feature request based on a mailing list discussion. Several of us would like the option to sort a mailbox by more than two criteria, i.e. thread/subject/date thread/score/date The consensus seems to be that it would be easiest if we could specify a single sort option like this: sort=thread/subject/date but it would be fine if one or two more sort_aux fields could be added, like this: sort=thread sort_aux=subject sort_aux2=date etc. I've looked at the code; I'm certain that the second option is easier, but I've decided you might be willing to implement the first option. If you aren't willing to implement this change, I will consider maintaining my own patch to do it. If you would like to include this change, but don't have time to implement it, I would probably be willing to implement the change myself and submit a patch to you for approval. Thank you. KEN -- 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 cc Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs gcc version 2.95.4 (Debian prerelease) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.3.27i (2002-01-22) 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.2.19pre17 (i586) [using ncurses 5.2] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP +USE_NNTP -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=""/usr/sbin/sendmail"" INEWS=""no -hS"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please use the flea(1) utility. vvv.nntp >How-To-Repeat: >Fix: }}}" pronovic@… 1048 Wishlist: New mail notification: notify in pager, report key headers in status mutt 1.5.0i enhancement mutt-dev new 2002-02-13T01:17:34-08:00 2007-04-07T07:36:04-07:00 "{{{ Package: mutt Version: 1.5.0i Severity: wishlist -- Please type your report below this line One thing that I've always missed since I switched from pine to mutt was pine's more verbose e-mail notification. Instead of just saying ""New mail in this mailbox."" it would say something like: [New mail from Philip Mak re New mail notification ideas] Also, pine checks for new mail when it is in the pager. In mutt's case, it doesn't, so if I stay inside the pager for hours then I won't see any new messages. I would like to suggest that these features (verbose new e-mail notification line, and check for new mail while in the pager) be implemented in mutt. -- 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-redhat-linux/2.96/specs gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.0i (2002-01-22) 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.7-10 (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 +HAVE_SMIME +HAVE_SMIME -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=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" pmak@… 1078 pine-like arrow navigation mutt enhancement mutt-dev new 2002-03-01T23:16:31-08:00 2005-08-01T18:06:21-07:00 "{{{ Package: mutt Severity: wishlist it would be cool if mutt supported arrow navigation like pine does. i tried to emulate it by setting keybindings, but it doesn't feel really good. >How-To-Repeat: >Fix: }}}" ossi@… 1079 Lines enclosing a forwarded mail can't be customized from muttrc mutt 1.3.27i enhancement mutt-dev new 2002-03-02T00:21:55-08:00 2005-08-01T18:05:13-07:00 "{{{ Package: mutt Version: 1.3.27i Severity: wishlist -- Please type your report below this line The lines enclosing a forwarded mail can't be customized from muttrc. ""----- Forwarded message from foo@bar.org -----"" -- 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 cc -I/usr/local/include Using builtin specs. gcc version 2.95.3 20010315 (release) [FreeBSD] - CFLAGS -Wall -pedantic -O -pipe -march=pentium -- Mutt Version Information Mutt 1.3.27i (2002-01-22) 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: FreeBSD 4.5-RELEASE (i386) [using ncurses 5.1] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK +USE_POP +USE_IMAP -IMAP_EDIT_THREADS -USE_GSS -USE_SSL -USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +COMPRESSED +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 SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.3.26.dw.pgp-hook.3 patch-nolock-if-saving patch-1.3.26.waf-cd.save_flag_with_trash_folder.1 1.3.27.tlr-me.maildir_efficiency.2 1.3.27.nr.unmailboxes.1 patch-1.3.27.cd.trash_folder.3 patch-1.3.27.cd.edit_threads.9.2 1.3.26.unk.keep_marked_old-nr 1.3.26.nr.tag_prefix_cond 1.3.26.nr.color-questions 1.3.26.mha.resend-fcc.1-nr patch-1.3.26.devl.narrow_tree.1 rr.compressed 1.3.26.bj.current_shortcut.1-nr >How-To-Repeat: >Fix: }}}" list@… 1113 "No option ""askto""" mutt 1.3.20i enhancement mutt-dev new 2002-03-18T10:06:53-08:00 2005-08-01T07:40:07-07:00 "{{{ Package: mutt Version: 1.3.20-1 Severity: wishlist -- Please type your report below this line I should be able to set ""askto"" to no. That way, when I edit a draft message that already contains a ""To"" header, it won't bother to ask me for it. -- Mutt Version Information Mutt 1.3.20i (2001-07-24) 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.2.17 [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 +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" Jeremy Malcolm 1128 new subject breaks thread option mutt enhancement mutt-dev reopened 2002-03-26T04:00:57-08:00 2005-08-20T12:35:02-07:00 "{{{ Package: mutt Version: 1.5.0i Severity: wishlist -- Please type your report below this line On some mailing lists that I am subscribed to, people sometimes send out completely new messages by replying to previous messages even when the new message has nothing to do with the previous message. I try to educate people not to do this, but it would be really useful if mutt could create new threads when the subject changes. This is a sample from my mailbox, the thread ""ylug: Some printing issues"" is not related to the other thread ""ylug: Next meeting, where"". 226 F 11 Oct 01 8:To ylug@halibut ylug: Next meeting, where 227 L 11 Oct 01 24:Richard G. Cleg |-> ylug: Some printing issues 228 r L 12 Oct 01 34:Arthur Clune |-> 229 L 12 Oct 01 36:Richard G. Cleg |-> 230 F 12 Oct 01 266:To ylug@halibut |-> 231 L 12 Oct 01 15:Richard G. Cleg |-> 232 L 12 Oct 01 18:Ewan Mac Mahon |-> Re: ylug: Next meeting, where 233 L 12 Oct 01 20:Arthur Clune |-> 234 L 12 Oct 01 46:GIBBS, PAUL |*> 235 L 12 Oct 01 22:Ewan Mac Mahon |-> -- System Information Debian Release: testing/unstable Kernel Version: Linux bloodnok 2.4.16 #1 Fri Mar 22 14:30:53 GMT 2002 i686 unknown -- 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 20011006 (Debian prerelease) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.0i (2002-01-22) 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.16 (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 +HAVE_SMIME -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=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/stow/mutt-cvs/share/mutt"" SYSCONFDIR=""/usr/local/stow/mutt-cvs/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. --- Begin /home/steve/.muttrc set folder = ~/.Mail set reverse_alias set alias_file = ~/.mail.addresses source ~/.mail.addresses set sort_alias = alias set quit = yes # exit without prompting set realname='Stephen Patterson' set alternates=""s\.patterson@freeuk\.com|cassat@freeuk\.com|lexx\.uklinux\.net"" unset beep # be quiet (don't beep) unset prompt_after # don't prompt after external commands set edit_headers # allow me to edit message headers set editor = ""jmacs +8"" set postponed = +postponed # where to save postponed messages set attribution=""On %d, %n (%a) wrote:"" set fast_reply # don't prompt for recipient address set abort_unmodified = ask-yes # ask if i want to send unmodified replies set record = +sent-mail # where to save sent messages send-hook . my_hdr From: steve@lexx.uklinux.net send-hook . unmy_hdr Reply-To: send-hook perl-win32 my_hdr From: cassat@freeuk.com send-hook perl-win32 my_hdr Reply-To: perl-win32-users@listserv.activestate.com fcc-hook '~s ""Job Application""' +jobs # job mail gets seperated fcc-hook '~s Application' +jobs fcc-hook '~s CV' +jobs set sendmail_wait = -1 # don't wait for sendmail to finish set forward_quote # quote forwarded text unset confirmappend # don't ask when appending messages to a mailbox unset confirmcreate # don't ask when creating mailboxes unset save_empty # delete empty mailboxes set read_inc = 25 mailboxes =mbox =ylug =wylug =CPAN =procmail =perl-win32 =jobs =mutt =root =thinkpad unset collapse_unread # don't collapse threads containing unread messages unset mark_old # mark old unread messages as new set wrap_search # goto top when search hits bottom set delete = yes # delete messages without asking set mask = '!(^\.)|(\.log$)|(\.cache$)' # don't show . .. and *.log in mailbox set mailcap_path = ~/.mailcap:/etc/mailcap set print_command = 'a2ps -1 --borders=no -Email -q --left-title=mutt' set print = yes # print without asking subscribe wylug-help wylug-announce wylug-discuss ylug perl-win32 mutt-dev procmail linux-thinkpad set followup_to # keep list traffic on lists set honor_followup_to = yes # ditto bind index l list-reply bind pager l list-reply bind index y print-message bind pager y print-message bind browser M enter-mask macro browser m ""Compose message"" macro index S s+spam\n macro pager S s+spam\n macro index G ""!fetchmail\n"" ""Check for new mail"" macro pager G ""!fetchmail\n"" ""Check for new mail"" macro index A ""!jmacs ~/.mail.addresses\n:source ~/.mail.addresses\n"" ""edit aliases"" macro pager A ""!jmacs ~/.mail.addresses\n:source ~/.mail.addresses\n"" ""edit aliases"" set pager_stop # don't move to next msg automatically unset markers # don't mark wrapped lines set pager_index_lines=4 # msgs to show above pager ignore * unignore from: subject date unhdr_order * hdr_order from to date subject folder-hook sent-mail ignore * folder-hook sent-mail unignore to subject date folder-hook jobs ignore * folder-hook jobs unignore to subject date color attachment cyan blue color bold white default color hdrdefault green default color header yellow default .*subject.* color indicator black cyan color markers cyan default color quoted white default color quoted1 green default color quoted2 red default color quoted3 cyan default color search cyan magenta color tree brightred default color signature yellow default color status yellow blue color body white default ""(ftp|http|https|mailto)://[^ ]+"" color body white default ""mailto:[-a-z_0-9.]+@[-a-z_0-9.]+"" color body white default ""[-a-z_0-9.]+@[-a-z_0-9.]+"" color index green default .*[Ww]ylug.*[Dd]iscuss.* color index cyan default .*[Ww]ylug.*[Hh]elp.* color index default default .*[Ww]ylug.*[Aa]nnounce.* folder-hook . set sort=threads folder-hook . set sort_aux=date folder-hook mbox set sort=date folder-hook mbox set sort_aux=subject folder-hook sent-mail set sort=date-sent folder-hook . 'exec collapse-all' # collapse all threads set date_format = ""%d %b %y"" set index_format=""%4C %Z %d %4l:%-15.15F %2M %s"" set status_on_top # statbar on top of screen set pgp_replysign = yes # sign replies to signed messages set pgp_verify_sig = yes # verify signed messages send-hook . 'set pgp_autosign' send-hook perl-win32 'unset pgp_autosign' send-hook wylug 'unset pgp_autosign' send-hook ~sJob 'unset pgp_autosign' send-hook ~sCV 'unset pgp_autosign' set pgp_decode_command=""gpg --quiet --no-verbose %?p?--passphrase-fd 0? --batch --output - %f"" set pgp_verify_command=""gpg --no-verbose --batch --output - --verify %s %f"" set pgp_decrypt_command=""gpg -q --passphrase-fd 0 --batch --output - %f"" set pgp_sign_command=""gpg -q --batch --output - --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a? %f"" set pgp_encrypt_only_command=""pgpewrap gpg -v --batch --output - --encrypt --textmode --armor --always-trust -- -r %r -- %f"" set pgp_encrypt_sign_command=""pgpewrap gpg --passphrase-fd 0 -v --batch --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f"" set pgp_import_command=""gpg --quiet --import -v %f"" set pgp_export_command=""gpg --quiet --export --armor %r"" set pgp_verify_key_command=""gpg --quiet --batch --fingerprint --check-sigs %r"" set pgp_list_pubring_command=""gpg --quiet --batch --with-colons --list-keys %r"" set pgp_list_secring_command=""gpg --quiet --batch --with-colons --list-secret-keys %r"" --- End /home/steve/.muttrc --- Begin /usr/local/stow/mutt-cvs/etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /usr/local/stow/mutt-cvs/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /usr/local/stow/mutt-cvs/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /usr/local/stow/mutt-cvs/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" --- End /usr/local/stow/mutt-cvs/etc/Muttrc Received: (at submit) by bugs.guug.de; 8 Aug 2000 16:15:00 +0000 From PeterBartosch@t-online.de Tue Aug 8 18:15:00 2000 Received: from mailout05.sul.t-online.com (mailout05.sul.t-online.com [194.25.134.82]) by sigtrap.guug.de (8.9.3/8.9.3/Debian/GNU) with ESMTP id SAA12528 for ; Tue, 8 Aug 2000 18:15:00 +0200 Received: from fwd05.sul.t-online.com by mailout05.sul.t-online.com with smtp id 13MC1r-0000wf-06; Tue, 8 Aug 2000 18:14:59 +0200 Received: from mind.bartosch.net (320089164316-0001@[62.156.23.175]) by fwd05.sul.t-online.com with esmtp id 13MC1l-25ZssSC; Tue, 8 Aug 2000 18:14:53 +0200 Received: from peter by mind.bartosch.net with local (Exim 3.11 #1 (Debian)) id 13MBx3-0000t2-00; Tue, 08 Aug 2000 18:10:01 +0200 Reply-To: peter@bartosch.net Subject: mutt-1.2i: wish: ability to devide a thread if needed To: submit@bugs.guug.de Message-Id: From: PeterBartosch@t-online.de (Peter Bartosch) Date: Tue, 08 Aug 2000 18:10:01 +0200 X-Sender: 320089164316-0001@t-dialin.net Package: mutt Version: 1.2-1 Severity: wishlist -- Please type your report below this line i want to devide a thread in parts if somebody starts a new topic right in the middle of a thread -> start a new thread when the topic (mail) becomes of topic (thread) the debian-package maintainer wrote that a patch for such funktionality was declined ... please add this, its usefull Peter Bartosch ... -- System Information Debian Release: 2.2 Kernel Version: Linux mind 2.2.13ac3 #1 SMP Mon Mar 13 13:32:29 CET 2000 i686 unknown Versions of the packages mutt depends on: ii libc6 2.1.3-10 GNU C Library: Shared libraries and Timezone dat ii libncurses5 5.0-6 Shared libraries for terminal handling ii exim 3.12-10 Exim Mailer ^^^ (Provides virtual package mail-transport-agent) -- Mutt Version Information System: Linux 2.2.13ac3 [using ncurses 5.0] Einstellungen bei der Compilierung: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP +USE_GSS +USE_SSL +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/spool/mail"" SHAREDIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" ISPELL=""/usr/bin/ispell"" >How-To-Repeat: >Fix: }}}" Stephen Patterson 1142 toggle-quoted should let the user know where quoted text has been removed display 1.3.28i enhancement mutt-dev new 2002-04-01T15:09:18-08:00 2009-06-30T07:50:44-07:00 "{{{ Package: mutt Version: 1.3.28-1 Severity: wishlist -- Please type your report below this line Hi. When 'T' is used to hide quoted text, one cannot see where quoted text was. It would be really cool if there could be an indication of hidden quoted lines. For example, the following: ueoaueoa ueaouoa > ueao ueao auao > ueaoueo ao ueaoua could be replaced by: ueoaueoa ueaouoa > [-- Quoted text snipped --] ueaoua Thanks. Regards, Hugo -- 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 cc Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs gcc version 2.95.4 (Debian prerelease) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.3.28i (2002-03-13) 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.18-jibboom (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=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/mutt-1.3.28/share/mutt"" SYSCONFDIR=""/usr/local/mutt-1.3.28/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" Hugo Haas 1166 Wishlist: save some info on email sign/encrypt histories mutt 1.3.28i enhancement mutt-dev new 2002-04-25T07:39:33-07:00 2005-08-01T18:21:04-07:00 "{{{ Package: mutt Version: 1.3.28-2 Severity: wishlist -- Please type your report below this line I would like it if I could see if an fcc_clear=yes saved email was sent encrypted or signed, for reference purposes. Same goes for decrypt-save'd emails. Maybe some X-* header? Thanks, Hugo -- Build environment information -- Mutt Version Information Mutt 1.3.28i (2002-03-13) >How-To-Repeat: >Fix: }}}" Hugo van der Merwe 1223 wish generate Lines: header for Maildir maildir/mh 1.3.28i enhancement mutt-dev new 2002-06-01T01:15:30-07:00 2009-06-30T07:48:38-07:00 "{{{ Package: mutt Version: 1.3.28-2 Severity: normal -- Please type your report below this line All e-mails that i have sent and stored via Fcc: don't have valid Line: headers in the Fcc: folder. I think this is a bug. -- 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 cc Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs gcc version 2.95.4 20011002 (Debian prerelease) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.3.28i (2002-03-13) 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.12-xfs (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_GNUTLS +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 +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.5.tlr.mx_open_append.2 patch-1.3.28.cvs.indexsegfault patch-1.3.27.bse.xtitles.1 patch-1.3.26.appoct.3 patch-1.3.15.sw.pgp-outlook.1 patch-1.3.27.admcd.gnutls.19 Md.use_editor Md.paths_mutt.man Md.muttbug_no_list Md.use_etc_mailname Md.muttbug_warning Md.gpg_status_fd patch-1.3.24.rr.compressed.1 patch-1.3.25.cd.edit_threads.9.1 patch-1.3.23.1.ametzler.pgp_good_sign Received: (at submit) by bugs.guug.de; 22 Aug 2003 21:02:24 +0000 From vincent@vinc17.org Fri Aug 22 23:02:24 2003 Received: from iramx1.ira.uni-karlsruhe.de ([141.3.10.80]) by trithemius.gnupg.org with esmtp (Exim 3.35 #1 (Debian)) id 19qJ3A-0008WL-00 for ; Fri, 22 Aug 2003 23:02:24 +0200 Received: from i20fw2.iaks.uni-karlsruhe.de ([141.3.32.129] helo=avalon.ira.uka.de) by iramx1.ira.uni-karlsruhe.de with esmtp (Exim 3.30 #10 (Debian)) id 19qJ5P-0005b6-00; Fri, 22 Aug 2003 23:04:43 +0200 Received: from falcon.iaks.uka.de (falcon [172.20.21.46]) by avalon.ira.uka.de (8.8.8p2+Sun/8.8.8) with ESMTP id XAA02367; Fri, 22 Aug 2003 23:03:45 +0200 (MET DST) From: vincent@vinc17.org Received: from ay (gast1 [172.20.22.84]) by falcon.iaks.uka.de (8.11.7+Sun/8.8.8) with ESMTP id h7ML3hj21985; Fri, 22 Aug 2003 23:03:43 +0200 (MEST) Received: from lefevre by ay with local (Exim 3.36 #1 (Debian)) id 19qJ5L-00077S-00; Fri, 22 Aug 2003 23:04:39 +0200 Subject: mutt-1.5.4i: Add a Lines header when message is read To: submit@bugs.guug.de Message-Id: Date: Fri, 22 Aug 2003 23:04:40 +0200 Package: mutt Version: 1.5.4-1 Severity: wishlist -- Please type your report below this line I would like that once the number of lines is known (e.g. if the message has been read), a Lines header should be added to the message if not already present. For instance, when opening a message from a maildir mailbox, a Lines header could be added to the message and saved at the next synchronization. Or when copying a message, a Lines header could be added too. A Lines header is useful when using %l in $index_format and also when piping a group of messages (for a line-based filter). -- 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 cc Reading specs from /usr/lib/gcc-lib/powerpc-linux/3.3.1/specs Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc --disable-multilib powerpc-linux Thread model: posix gcc version 3.3.1 20030626 (Debian prerelease) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.4i (2003-03-19) Copyright (C) 1996-2002 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.18-newpmac (ppc) [using ncurses 5.3] [using libidn 0.1.14 (compiled with 0.1.14)] 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 -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME +BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/local/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/home/lefevre/share/mutt"" SYSCONFDIR=""/home/lefevre/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.3.24.ats.parent_match.1 patch-1.5.1.vl.savehist.1 >How-To-Repeat: >Fix: }}}" Nikolaus Rath 1268 open directory view with cursor on current mailbox or subdir left browser enhancement mutt-dev new 2002-07-10T05:45:53-07:00 2009-06-30T07:48:55-07:00 "{{{ Package: mutt Severity: wishlist Version: 1.4i the directory view should start up with the cursor on the current mailbox if the mailbox happens to be in this dir (there could, btw, be an option to always change into the dir the current mailbox lives in, and a command to explicitly request it). same for the explicit mailbox mode. >How-To-Repeat: >Fix: }}}" Oswald Buddenhagen 1283 mutt: 'killing' threads mutt enhancement mutt-dev new 2002-07-23T06:27:47-07:00 2005-08-23T11:20:41-07:00 "{{{ Package: mutt Version: 1.4.0-2 Severity: wishlist [NOTE: this bug report has been submitted to the debian BTS as Bug#153887. Please Cc all your replies to 153887@bugs.debian.org .] From: ""Norbert Veber"" Subject: mutt: 'killing' threads Date: Mon, 22 Jul 2002 12:14:06 -0400 It would be nice if mutt had the ability to kill threads. This would be a feature similar to that of news readers. Currently we have ctrl-r which marks an entire thread as read. The kill threads feature should work something like this: -mark thread as read (same as ctrl-r) -any future messages that fall under this thread should also be marked as read Many times on various mailing lists, I find myself completely uninterested in certain message threads, but have no way of avoiding new messages that come in, other than hitting ctrl-r over and over and over again... I think many others would find such a feature useful as well. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux pyre.virge.net 2.4.19-pre10 #1 Thu Jun 6 20:57:36 EDT 2002 i686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 Versions of packages mutt depends on: ii libc6 2.2.5-12 GNU C Library: Shared libraries an ii libncurses5 5.2.20020112a-8 Shared libraries for terminal hand ii libsasl7 1.5.27-3.3 Authentication abstraction library ii postfix [mail-transport- 1.1.11-2 A high-performance mail transport -- no debconf information >How-To-Repeat: >Fix: }}}" Marco d'Itri 1295 mutt: Message-ID extra data removal mutt enhancement mutt-dev new 2002-08-02T06:05:19-07:00 2007-04-07T07:23:08-07:00 "{{{ Package: mutt Version: 1.4i Severity: wishlist Tags: patch I don't like to tell in every email I send, how many messages I've sent in the current mutt session. So this patch removes the MsgIdPfx and getpid from the Message-ID Instead I've added microseconds to the Message-ID, so it's as difficult to have two messages with the same Message-ID If you also don't like sending extra data in Message-ID you should apply this patch. }}}" Eduardo Pérez Ureta 1315 iconv transliteration charset 1.4i enhancement mutt-dev new 2002-08-16T21:32:10-07:00 2009-06-30T07:49:14-07:00 "{{{ Package: mutt Version: 1.4i Severity: wishlist -- Please type your report below this line It would be great if mutt enabled iconv transliteration when displaying messages. The current work-around when using GNU libiconv is to set the charset to ISO-8859-1//TRANSLIT or the like, but that seems unclean. Why not add a muttrc configuration option that enables or disables iconv transliteration when available? Either that, or always turn on transliteration. Most of the enabling code is already available in intl/loadmsgcat.c. -Tony -- 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 cc cc: Error: no source, object or ucode file specified - CFLAGS -std1 -fast -O4 -tune host -arch host -D_XOPEN_SOURCE_EXTENDED -- Mutt Version Information Mutt 1.4i (2002-05-29) 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: OSF1 V4.0 (alpha) 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/local/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/spool/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" Tony Leneis 1359 reverse_alias_force option mutt enhancement mutt-dev new 2002-10-26T03:00:53-07:00 2005-09-04T11:52:01-07:00 "{{{ Package: mutt Version: 1.4i Severity: wishlist currently when the reverse_alias option is set, a found alias will override the realname even when the from header already contains one. i think this should not happen by default (but should be still possible (to make the paranoid happy :)). >How-To-Repeat: >Fix: }}}" Oswald Buddenhagen 1360 folder-leave-hook mutt enhancement mutt-dev new 2002-10-26T03:14:36-07:00 2008-08-21T06:47:05-07:00 "{{{ Package: mutt Version: 1.4i Severity: wishlist i want mutt to fork a (wrapped) isync process in the background when i leave a folder. but there don't seem to be hooks which are invoked when a context is left, only when one is entered. >How-To-Repeat: >Fix: }}}" Oswald Buddenhagen 1372 wishlist: better integration of query_command mutt 1.4i enhancement mutt-dev new 2002-11-01T19:05:18-08:00 2005-08-01T19:23:55-07:00 "{{{ Package: mutt Version: 1.4.0-4 Severity: wishlist -- Please type your report below this line it would be awesome if mutt would incorporate the query_command better. for instance, i'd love to be able to invoke mutt like: mutt pan and have it run `$query_command pan` before displaying a list of possible matches to choose from. this in addition to putting a search string in the headers that i edit directly and mutt displaying a list of matches when the rfc821 file I just edited is being returned to mutt. basically i love the aliases interaction of mutt. if that could be extended to allow transparent use of a query command like lbdbq if one wishes to do so instead of the aliases flat file, i would be happy!!! -- 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 cc Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs gcc version 2.95.4 20011002 (Debian prerelease) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.4i (2002-05-29) 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-grsec+freeswan-fishbowl (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_GNUTLS +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 +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.3.28.cvs.indexsegfault patch-1.3.27.bse.xtitles.1 patch-1.3.26.appoct.3 patch-1.3.15.sw.pgp-outlook.1 patch-1.4.admcd.gnutlsbuild.53d patch-1.4.admcd.gnutlsdlopen.53d patch-1.4.admcd.gnutls.55d Md.use_editor Md.paths_mutt.man Md.muttbug_no_list Md.use_etc_mailname Md.muttbug_warning Md.gpg_status_fd patch-1.4.0.cd.edit_threads.9.2 patch-1.3.24.rr.compressed.1 patch-1.3.23.1.ametzler.pgp_good_sign >How-To-Repeat: >Fix: }}}" madduck@… 1403 attach attachments from some other message in some other folder to a message mutt 1.3.28i enhancement mutt-dev new 2002-12-03T03:05:52-08:00 2005-11-01T00:55:02-08:00 "{{{ Package: mutt Version: 1.3.28-2 Severity: wishlist -- Please type your report below this line hello all i am doing this for the first time. so sorry if i am doing something wrong and improperly. while i was working with mutt, i wanted to attach to the message i was composing, one among several attachments to a message in another folder. i could not find a command to do it directly. so i went through a topsy-turvy way of going to that folder, going to that message, saving the attachment as a file. coming back to composition of message and attaching the file. i wish, just as i can attach a message, i could attach an attachment to other message. thanx for your help sandip p deshmukh ------***-------- -- 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 cc Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs gcc version 2.95.4 20011002 (Debian prerelease) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.3.28i (2002-03-13) 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.18-bf2.4 (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_GNUTLS +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 +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.5.tlr.mx_open_append.2 patch-1.3.28.cvs.indexsegfault patch-1.3.27.bse.xtitles.1 patch-1.3.26.appoct.3 patch-1.3.15.sw.pgp-outlook.1 patch-1.3.27.admcd.gnutls.19 Md.use_editor Md.paths_mutt.man Md.muttbug_no_list Md.use_etc_mailname Md.muttbug_warning Md.gpg_status_fd patch-1.3.24.rr.compressed.1 patch-1.3.25.cd.edit_threads.9.1 patch-1.3.23.1.ametzler.pgp_good_sign >How-To-Repeat: >Fix: }}}" sandip 1437 Verify signatures in background crypto enhancement mutt-dev new 2003-01-13T21:54:30-08:00 2009-06-30T07:48:29-07:00 "{{{ Package: mutt Version: 1.4.0-5 / 2003-01-13 Severity: wishlist [NOTE: this bug report has been submitted to the debian BTS as Bug#176473. Please Cc all your replies to 176473@bugs.debian.org .] From: Peter Palfrader Subject: Verify signatures in background Date: Hello Marco, hi Thomas, it would be really neat if mutt could verify PGP Signatures in the background. Upon encountering an OpenPGP signed mail mutt should display it right away, perhaps with »Still processing« in the standard PGP brackets and launch GnuPG/whatever in the background. Once the background process finishes the message should be redisplayed with GnuPG's output that we very well know. If the user moves to the next message before GnuPG could finish it should be up to the user what is done by default (1) either let the command run (so that updating trustdb can finnish eventually). Once the command exited only the latest message should be tried to get verified. or (2) kill the process immediatly. I favour option (1). yours, peter [If you've downloaded my PGP key before please redownload it for I've changed cipher preferences: gpg --keyserver pgp.dtype.org --recv 94c09c7f] -- PGP signed and encrypted | .''`. ** Debian GNU/Linux ** messages preferred. | : :' : The universal | `. `' Operating System http://www.palfrader.org/ | `- http://www.debian.org/ Received: (at submit) by bugs.guug.de; 9 Dec 2001 03:45:13 +0000 From aaronl@vitelus.com Sun Dec 09 04:45:13 2001 Received: from vitelus.com ([64.81.243.207] ident=aaronl) by trithemius.gnupg.org with esmtp (Exim 3.12 #1 (Debian)) id 16Cutt-0006GY-00 for ; Sun, 09 Dec 2001 04:45:13 +0100 Received: from aaronl by vitelus.com with local (Exim 3.33 #1 (Debian)) id 16CusS-0001Z9-00 for ; Sat, 08 Dec 2001 19:43:44 -0800 Date: Sat, 8 Dec 2001 19:43:44 -0800 From: Aaron Lehmann To: submit@bugs.guug.de Subject: Please display pgp information incrementally Message-ID: <20011208194344.A5918@vitelus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.20i Package: mutt Severity: wishlist I like to use a tool called sigtrace which prints out a key trust path between myself and the signer of a message. I set it up to run as part of the pgp verification command in mutt. The problem this causes is that it takes awhile to run, and in the meantime mutt blocks waiting for it to complete. I would like to start reading a message while PGP verification commands are still running. Ideally, a signed message would start out in the pager as: [-- PGP output follows (current time: Sat 08 Dec 2001 07:00:25 PM PST) --] [-- End of PGP output --] ...body of message... and output from the PGP/gpg/sigtrace process would be filled in between the first two lines as it was received on on the pipe, preventing mutt from blocking as it waits for all of the output. I don't know how difficult this would be. I suspect that it largely hinges on the pager's ability to insert text at a point in the middle of a message. >How-To-Repeat: >Fix: }}}" Marco d'Itri 1467 checking of imap mailbox delays opening inbox IMAP 1.5.3i enhancement mutt-dev new 2003-02-14T22:40:39-08:00 2007-03-30T20:59:30-07:00 "if you have an imap folder watched via ""mailboxes"" it will also be checked for new mail right at the startup of mutt. This delays the showing of the local inbox folder because mutt tries to authenticate to the imap server before showing the inbox. The inbox should be drawn first imho." muttbug@… 1481 Support for headers other than From in send-hooks (patch included) mutt 1.5.3i enhancement mutt-dev new 2003-02-24T08:50:31-08:00 2005-08-17T15:01:01-07:00 "{{{ Package: mutt Version: mutt-1.5.3i Severity: wishlist -- Please type your report below this line Description ^^^^^^^^^^^ Actually, one could use my_hdr command in send-hooks for any field, but only From: field would be modified for current mail, other fields would be modified _after_. Demonstration ^^^^^^^^^^^^^ Let use this typical .muttrc for the test set autoedit = no set charset = ""iso-8859-15"" set send_charset = ""us-ascii:iso-8859-1:iso-8859-15:utf-8"" set edit_headers = yes send-hook . 'my_hdr From: me@home.tld; my_hdr Bcc: me@home.tld; set signature=~/.signature; my_hdr Subject:' send-hook '@work.tld' 'my_hdr From: me@work.tld; my_hdr Bcc: me@work.tld; set signature=~/.signature.work' send-hook 'mail-list@server.tld' 'my_hdr From: me@tempaddress.tld; my_hdr Subject: [mail-list]' Suppose we write a mail to mail-list@server.tld. The subject should be preset with '[mail-list]', but it is empty, although From is me@tempaddress.tld, as expected, and the signature is the good one too. The Bcc is empty, although the default send-hook should have applied before the one for mail-list@server.tld. and set me@home.tld. Now we write a mail to somebody@work.tld. This time, Subject is preset with '[mail-list]', as it should have been for the preceding mail and Bcc is set to me@home.tld, while we hopped me@work.tld. At last, we write a mail to someone@somewhere.tld. Subject is no more preset, the From and the signature are good, as before, but the Bcc is set to me@work.tld rather than me@home.tld. Suggested fix ^^^^^^^^^^^^^ I tracked down the problem to the processing order of function ci_send_message in send.c . Actually, - my_hdr commands are executed, - headers are edited, - the mail we are replying to is taken into account, - send-hooks are executed. So if send_hooks modify recipient headers, they will be taken into account... for the next mail. A solution could be : for each header in To, Cc and Bcc : execute my_hdr command for this header, edit header, take into account the mail we are replying to, reevaluate send-hooks; edit remaining headers. So Cc, Bcc and Subject could depend on To; Bcc and Subject could depend on Cc and so on. To couldn't depend on Cc, for example, but that would probably be far more complex to code and even to use. Suggested patch ^^^^^^^^^^^^^^^ Following is a patch which implements this solution : --------------------Cut here--------------------------------------------------- --- mutt-1.5.3.orig/send.c 2002-12-11 23:45:38.000000000 +0100 +++ mutt-1.5.3/send.c 2003-01-03 02:16:32.000000000 +0100 @@ -200,18 +200,23 @@ return 0; } -static int edit_envelope (ENVELOPE *en) +static int edit_envelope_recip_field (const char *field, ENVELOPE *en) { - char buf[HUGE_STRING]; - LIST *uh = UserHeader; - - if (edit_address (&en->to, ""To: "") == -1 || en->to == NULL) + if (strcmp(field, ""to"") == 0 && (edit_address (&en->to, ""To: "") == -1 || en->to == NULL)) return (-1); - if (option (OPTASKCC) && edit_address (&en->cc, ""Cc: "") == -1) + if (strcmp(field, ""cc"") == 0 && option (OPTASKCC) && edit_address (&en->cc, ""Cc: "") == -1) return (-1); - if (option (OPTASKBCC) && edit_address (&en->bcc, ""Bcc: "") == -1) + if (strcmp(field, ""bcc"") == 0 && option (OPTASKBCC) && edit_address (&en->bcc, ""Bcc: "") == -1) return (-1); + return 0; +} + +static int edit_envelope_remaining (ENVELOPE *en) +{ + char buf[HUGE_STRING]; + LIST *uh = UserHeader; + if (en->subject) { if (option (OPTFASTREPLY)) @@ -246,21 +251,29 @@ return 0; } -static void process_user_recips (ENVELOPE *env) +static void process_user_recip_field (const char *field, ENVELOPE *env) { LIST *uh = UserHeader; for (; uh; uh = uh->next) { - if (ascii_strncasecmp (""to:"", uh->data, 3) == 0) + if (strcmp(field, ""to"") == 0 && ascii_strncasecmp (""to:"", uh->data, 3) == 0) env->to = rfc822_parse_adrlist (env->to, uh->data + 3); - else if (ascii_strncasecmp (""cc:"", uh->data, 3) == 0) + else if (strcmp(field, ""cc"") == 0 && ascii_strncasecmp (""cc:"", uh->data, 3) == 0) env->cc = rfc822_parse_adrlist (env->cc, uh->data + 3); - else if (ascii_strncasecmp (""bcc:"", uh->data, 4) == 0) + else if (strcmp(field, ""bcc"") == 0 && ascii_strncasecmp (""bcc:"", uh->data, 4) == 0) env->bcc = rfc822_parse_adrlist (env->bcc, uh->data + 4); } } +static void process_user_recips (ENVELOPE *env) +{ + process_user_recip_field(""to"", env); + process_user_recip_field(""cc"", env); + process_user_recip_field(""bcc"", env); + /* suboptimal, but shorter */ +} + static void process_user_header (ENVELOPE *env) { LIST *uh = UserHeader; @@ -1040,6 +1053,8 @@ int i, killfrom = 0; int fcc_error = 0; int free_clear_content = 0; + char *recip_headers[] = {""to"", ""cc"", ""bcc"", NULL}; + char **fieldp; #if defined(HAVE_PGP) || defined(HAVE_SMIME) BODY *save_content = NULL; @@ -1168,60 +1183,75 @@ envelope_defaults (msg->env, ctx, cur, flags) == -1) goto cleanup; - if (option (OPTHDRS)) - process_user_recips (msg->env); + for (fieldp = recip_headers; *fieldp; ++fieldp) { + /* Process user default for this header */ + if (option (OPTHDRS)) + process_user_recip_field (*fieldp, msg->env); + + /* Expand aliases and remove duplicates/crossrefs */ + mutt_fix_reply_recipients (msg->env); + + /* Edit header if needed */ + if (! (flags & SENDMAILX) && + ! (option (OPTAUTOEDIT) && option (OPTEDITHDRS)) && + ! ((flags & SENDREPLY) && option (OPTFASTREPLY))) + { + if (edit_envelope_recip_field (*fieldp, msg->env) == -1) + goto cleanup; + } - /* Expand aliases and remove duplicates/crossrefs */ - mutt_fix_reply_recipients (msg->env); + /* (Re)evaluate send-hooks, which may depend on the field just edited */ - if (! (flags & SENDMAILX) && - ! (option (OPTAUTOEDIT) && option (OPTEDITHDRS)) && - ! ((flags & SENDREPLY) && option (OPTFASTREPLY))) - { - if (edit_envelope (msg->env) == -1) - goto cleanup; - } + /* the from address must be set here regardless of whether or not + * $use_from is set so that the `~P' (from you) operator in send-hook + * patterns will work. if $use_from is unset, the from address is killed + * after send-hooks are evaluated */ + + if (!msg->env->from) + { + msg->env->from = mutt_default_from (); + killfrom = 1; + } - /* the from address must be set here regardless of whether or not - * $use_from is set so that the `~P' (from you) operator in send-hook - * patterns will work. if $use_from is unset, the from address is killed - * after send-hooks are evaulated */ + if ((flags & SENDREPLY) && cur) + { + /* change setting based upon message we are replying to */ + mutt_message_hook (NULL, cur, M_REPLYHOOK); - if (!msg->env->from) - { - msg->env->from = mutt_default_from (); - killfrom = 1; - } + /* + * set the replied flag for the message we are generating so that the + * user can use ~Q in a send-hook to know when reply-hook's are also + * being used. + */ + msg->replied = 1; + } - if ((flags & SENDREPLY) && cur) - { - /* change setting based upon message we are replying to */ - mutt_message_hook (NULL, cur, M_REPLYHOOK); + /* change settings based upon recipients */ + + mutt_message_hook (NULL, msg, M_SENDHOOK); /* - * set the replied flag for the message we are generating so that the - * user can use ~Q in a send-hook to know when reply-hook's are also - * being used. + * Unset the replied flag from the message we are composing since it is + * no longer required. This is done here because the FCC'd copy of + * this message was erroneously get the 'R'eplied flag when stored in + * a maildir-style mailbox. */ - msg->replied = 1; - } + msg->replied = 0; - /* change settings based upon recipients */ - - mutt_message_hook (NULL, msg, M_SENDHOOK); - - /* - * Unset the replied flag from the message we are composing since it is - * no longer required. This is done here because the FCC'd copy of - * this message was erroneously get the 'R'eplied flag when stored in - * a maildir-style mailbox. - */ - msg->replied = 0; + if (killfrom) + { + rfc822_free_address (&msg->env->from); + killfrom = 0; + } + } - if (killfrom) + /* Edit remaining headers */ + if (! (flags & SENDMAILX) && + ! (option (OPTAUTOEDIT) && option (OPTEDITHDRS)) && + ! ((flags & SENDREPLY) && option (OPTFASTREPLY))) { - rfc822_free_address (&msg->env->from); - killfrom = 0; + if (edit_envelope_remaining (msg->env) == -1) + goto cleanup; } if (option (OPTHDRS)) --------------------Cut here--------------------------------------------------- -- System Information System Version: Linux gaston.jamaislejeudi.dyns.org 2.4.19-16mdk #1 Fri Sep 20 18:15:05 CEST 2002 i686 unknown unknown GNU/Linux RedHat Release: Mandrake Linux release 9.0 (dolphin) for i586 -- 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/i586-mandrake-linux-gnu/3.2/specs Configured with: ../configure --prefix=/usr --libdir=/usr/lib --with-slibdir=/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --enable-long-long --enable-__cxa_atexit --enable-languages=c,c++,ada,f77,objc,java --host=i586-mandrake-linux-gnu --with-system-zlib Thread model: posix gcc version 3.2 (Mandrake Linux 9.0 3.2-1mdk) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.3i (2002-12-17) Copyright (C) 1996-2002 Michael R. Elkins et autres. Mutt ne fournit ABSOLUMENT AUCUNE GARANTIE ; pour les détails tapez `mutt -vv'. Mutt est un logiciel libre, et vous êtes libre de le redistribuer sous certaines conditions ; tapez `mutt -vv' pour les détails. System: Linux 2.4.19-16mdk (i686) [using ncurses 5.2] Options de compilation : -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP -USE_IMAP -USE_GSS -USE_SSL -USE_SASL -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_PGP +HAVE_SMIME -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=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/opt/mutt-1.5.3/share/mutt"" SYSCONFDIR=""/opt/mutt-1.5.3/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER Pour contacter les développeurs, veuillez écrire à . Pour signaler un bug, veuillez utiliser l'utilitaire flea(1). --- Begin /home/laurent/.muttrc set autoedit = no set charset = ""iso-8859-15"" set send_charset = ""us-ascii:iso-8859-1:iso-8859-15:utf-8"" set edit_headers = yes send-hook . 'my_hdr From: me@home.tld; my_hdr Bcc: me@home.tld; set signature=~/.signature; my_hdr Subject:' send-hook '@work.tld' 'my_hdr From: me@work.tld; my_hdr Bcc: me@work.tld; set signature=~/.signature.work' send-hook 'mail-list@server.tld' 'my_hdr From: me@tempaddress.tld; my_hdr Subject: [mail-list]' --- End /home/laurent/.muttrc --- Begin /opt/mutt-1.5.3/etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /opt/mutt-1.5.3/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /opt/mutt-1.5.3/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /opt/mutt-1.5.3/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" --- End /opt/mutt-1.5.3/etc/Muttrc >How-To-Repeat: >Fix: }}}" Laurent Dudouet 1489 does not recognize MAILPATH mutt enhancement mutt-dev new 2003-03-01T11:16:10-08:00 2007-03-28T11:26:25-07:00 "{{{ Package: mutt Version: 1.3.28-2 Severity: wishlist [NOTE: this bug report has been submitted to the debian BTS as Bug#182912. Please Cc all your replies to 182912@bugs.debian.org .] From: Matt Kraai Subject: does not recognize MAILPATH Date: Fri, 28 Feb 2003 14:18:50 -0800 Mutt does not know that mailboxes listed in MAILPATH receive mail. Matt -- Oink! >How-To-Repeat: >Fix: }}}" Marco d'Itri 1552 removing signature part when replying to message mutt 1.5.4i enhancement mutt-dev new 2003-04-26T19:49:33-07:00 2007-04-07T07:22:46-07:00 "{{{ Package: mutt Version: 1.5.4i Severity: wishlist -- Please type your report below this line It would be nice if mutt had a variable, which, when set, would cause the removal of the signature part (ie. everything from '-- \n' to the end of file) when one replies to a message, and the original message is included (quoted) in the reply. P.S. The copyright dates in the version string need to be updated. Mutt 1.5.4i (2003-03-19) Copyright (C) 1996-2002 Michael R. Elkins and others. ^^^^ -- System Information System Version: Linux unknown 2.2.14 #1 Fri Apr 26 00:00:00 GMT 2002 i386 unknown -- Build environment information - gcc version information - CFLAGS -- Mutt Version Information Mutt 1.5.4i (2003-03-19) Copyright (C) 1996-2002 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.18 (i686) [using slang 10401] 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 -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR -HAVE_START_COLOR -HAVE_TYPEAHEAD -HAVE_BKGDSET -HAVE_CURS_SET -HAVE_META -HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP -CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT -ENABLE_NLS +LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID -HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""Mailbox"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/usr/share/mutt"" EXECSHELL=""/bin/sh"" To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" 0dq94rkr001@… 1569 pgp_autosign and pgp_autoencrypt only if a key is available crypto 1.5.4i enhancement mutt-dev new 2003-05-19T03:55:05-07:00 2009-07-31T09:22:28-07:00 "{{{ Package: mutt Version: 1.5.4-1 Severity: wishlist -- Please type your report below this line I want to sign and encrypt all my mails if if have I a key of the recipient. I currently use the following .muttrc code: source 'gpg --list-keys | perl -e ""while(<>){/(\\b|[<(])([^ \\t]+@[^ \\t]+\.[^ \t]+)(\\b|[>)])/ and \$a{\$2}=1;}print map qq/send-hook \""~C \$_\"" set pgp_autosign pgp_autoencrypt\n/, keys %a;""|' But this becomes very slow. Maybe you can add an option to encrypt and sign a mail automatically if there is a key available. bye Nikolaus >How-To-Repeat: >Fix: }}}" Nikolaus@… 1593 mutt: Mutt needn't lock mailbox when opening read-only mutt enhancement mutt-dev new 2003-07-22T11:43:18-07:00 2005-09-05T23:52:51-07:00 "{{{ Package: mutt Version: 1.3.28-2.2 Severity: wishlist [NOTE: this bug report has been submitted to the debian BTS as Bug#202305. Please Cc all your replies to 202305@bugs.debian.org .] From: Andrew Shugg Subject: mutt: Mutt needn't lock mailbox when opening read-only Date: Tue, 22 Jul 2003 01:43:02 +0800 I became aware of this 'issue' when using Mutt to quickly check mailboxes on a remote NFS server, which is such a clunky old thing that it's faster to search mailboxes remotely with Mutt over NFS than it is to use grep locally. =) When running 'mutt -R -f /net//.../Mail/mailbox' I have to wait a while for the fnctl lock tries and fails a few times. When specifying the -R flag on the commandline it seems to me that locking the mailbox is unnecessary, and indeed -R may have been given because modifying the mailbox itself isn't possible. So, can the mailbox lock be skipped if M_RO is set? I'm wary of trying to hack the change in myself as I've no idea what I would break, but I'm guessing that a test could be added to mbox_open_mailbox() in mbox.c for M_RO or similar. While this is a completely harmless thing, maybe it can be fixed in a few seconds, or bumped upstream ... Thanks, Andrew S. -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux harp 2.4.21 #1 Thu Jun 19 13:00:41 WST 2003 i586 Locale: LANG=C, LC_CTYPE=C Versions of packages mutt depends on: ii libc6 2.2.5-11.5 GNU C Library: Shared libraries an ii libncurses5 5.2.20020112a-7 Shared libraries for terminal hand ii libsasl7 1.5.27-3 Authentication abstraction library ii sendmail [mail-transport 8.12.3-6.4 A powerful, efficient, and scalabl >How-To-Repeat: >Fix: }}}" Marco d'Itri 1603 "wish configurable ""Re: your mail"" on subject-less mail reply" mutt 1.5.4i enhancement mutt-dev new 2003-08-01T09:36:13-07:00 2007-04-07T07:35:12-07:00 "{{{ Package: mutt Version: 1.5.4-1 Severity: wishlist -- Please type your report below this line I wonder if it can be possible to change this default behavior when replying to an email where the Subject: line was empty and replace ""Re: your mail"" by something more elaborate like ""Re: (your mail from $DATE $HOUR)"" or somethink like that. It'll be very appreciate, I think. At least by me! ;-) (sorry, I really don't have the capabilities to write a patch myself!) -- System Information System Version: Linux navi 2.4.20 #1 Thu Jun 12 18:22:15 CEST 2003 i686 GNU/Linux -- 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 cc Lecture des spécification à partir de /usr/lib/gcc-lib/i386-linux/3.2.3/specs Configuré avec: ../src/configure -v --enable-languages=c,c++,f77,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-objc-gc i386-linux Modèle de thread: posix version gcc 3.2.3 (Debian) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.4i (2003-03-19) Copyright (C) 1996-2002 Michael R. Elkins et autres. Mutt ne fournit ABSOLUMENT AUCUNE GARANTIE ; pour les détails tapez `mutt -vv'. Mutt est un logiciel libre, et vous êtes libre de le redistribuer sous certaines conditions ; tapez `mutt -vv' pour les détails. System: Linux 2.4.20 (i686) [using ncurses 5.3] [using libidn 0.1.14 (compiled with 0.1.11)] Options de compilation : -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +IMAP_EDIT_THREADS -USE_GSS -USE_SSL +USE_GNUTLS +USE_SASL -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO +USE_CACHE ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" Pour contacter les développeurs, veuillez écrire à . Pour signaler un bug, veuillez utiliser l'utilitaire flea(1). patch-1.5.3.Md.gpg_status_fd patch-1.3.23.1.ametzler.pgp_good_sign patch-1.4.Md.gpg-agent patch-1.5.1.cd.edit_threads.9.2 patch-1.5.3.Md.etc_mailname_gethostbyname patch-1.3.27.bse.xtitles.1 Md.muttbug Md.use_debian_editor patch-1.4.admcd.gnutlsdlopen.53d patch-1.5.4.Z.hcache.8 patch-1.4.admcd.gnutlsbuild.53d patch-1.4.admcd.gnutls.55d patch-1.5.3.rr.compressed.1 Received: (at submit) by bugs.guug.de; 18 Jan 2004 16:06:06 +0000 From cri@linux.it Sun Jan 18 17:06:04 2004 Received: from smtp1.libero.it ([193.70.192.51]) by trithemius.gnupg.org with esmtp (Exim 3.35 #1 (Debian)) id 1AiFR1-0001mK-00 for ; Sun, 18 Jan 2004 17:05:59 +0100 Received: from wamozart.buliga.it (151.30.201.87) by smtp1.libero.it (7.0.020-DD01) id 3F6F0E480219A017; Sun, 18 Jan 2004 17:08:30 +0100 Received: by wamozart.buliga.it (Postfix, from userid 1000) id 6DB7A24586; Sun, 18 Jan 2004 17:07:33 +0100 (CET) From: Cristian Rigamonti Subject: mutt-1.5.5.1i: i18n of ""Re: your mail"" string To: submit@bugs.guug.de Message-Id: <20040118160733.6DB7A24586@wamozart.buliga.it> Date: Sun, 18 Jan 2004 17:07:33 +0100 (CET) X-Spam-Status: No, hits=-3.7 required=4.0 tests=BAYES_10,UPPERCASE_25_50 version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Package: mutt Version: 1.5.5.1i Severity: normal -- Please type your report below this line When answering a message with an empty ""Subject: "" field, mutt automatically puts ""Re: your mail"" in the answering message's ""Subject: "" field. This string (contained in send.c) should be gettextized (or it could be made user-configurable). -- 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 -g -O2 -- Mutt Version Information Mutt 1.5.5.1i (2003-11-05) Copyright (C) 1996-2002 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.18-bf2.4 (i686) [using ncurses 5.2] Opzioni di compilazione: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP -USE_IMAP -IMAP_EDIT_THREADS -USE_GSS -USE_SSL -USE_SASL -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID -HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER Per contattare gli sviluppatori scrivi a . Per segnalare un bug usa il programma flea(1). patch-1.5.5.1.cd.edit_threads.9.5 >How-To-Repeat: >Fix: }}}" Mathieu Dussier 1635 wishlist: edit attachments when forwarding mutt 1.5.4i enhancement mutt-dev new 2003-09-13T00:33:47-07:00 2009-06-02T04:36:20-07:00 "{{{ Package: mutt Version: 1.5.4+20030817 Severity: wishlist -- Please type your report below this line (a) When I forward a message with attachments, I'd like to be able to have the attachments attached _directly_ to the message I send (not attached to an attachment containing the entire forwarded message). (b) More generally, it would be nice to be able to edit the attachments tree before sending a message without having to 'e'dit the message manually. At the moment I see no way to view the tree structure before sending, let alone editing it. To clarify: I'd like to be able to move sub-attachments around the attachments heirarchy in some interactive fashion. >How-To-Repeat: >Fix: }}}" rupert.debian@… 1710 swapping To: and CC: field mutt 1.3.28i enhancement mutt-dev new 2003-11-19T00:58:27-08:00 2005-10-05T13:23:35-07:00 "{{{ Package: mutt Version: 1.3.28-2.2 Severity: wishlist -- Please type your report below this line I would like a keystroke that allow to swap the To: and CC: field in the `Compose' menu. This is useful when you use open mailing-lists, or mail-based systems like debbugs. Cheers, Bill. -- System Information Debian Release: 3.0 Kernel Version: Linux seventeen 2.4.21 #1 Sat Sep 6 12:44:52 CEST 2003 i686 unknown Versions of the packages mutt depends on: ii exim 3.35-1woody2 An MTA (Mail Transport Agent) ii libc6 2.2.5-11.5 GNU C Library: Shared libraries and Timezone ii libncurses5 5.2.20020112a- Shared libraries for terminal handling ii libsasl7 1.5.27-3 Authentication abstraction library. ii exim 3.35-1woody2 An MTA (Mail Transport Agent) ^^^ (Provides virtual package mail-transport-agent) -- 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 cc Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs gcc version 2.95.4 20011002 (Debian prerelease) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.3.28i (2002-03-13) Copyright (C) 1996-2001 Michael R. Elkins et autres. Mutt ne fournit ABSOLUMENT AUCUNE GARANTIE ; pour les détails tapez `mutt -vv'. Mutt est un logiciel libre, et vous êtes libre de le redistribuer sous certaines conditions ; tapez `mutt -vv' pour les détails. System: Linux 2.4.21 (i686) [using ncurses 5.2] Options de compilation : -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP -USE_GSS -USE_SSL +USE_GNUTLS +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 +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" Pour contacter les développeurs, veuillez écrire à . Pour signaler un bug, veuillez utiliser l'utilitaire flea(1). patch-1.5.tlr.mx_open_append.2 patch-1.3.28.cvs.indexsegfault patch-1.3.27.bse.xtitles.1 patch-1.3.26.appoct.3 patch-1.3.15.sw.pgp-outlook.1 patch-1.3.27.admcd.gnutls.19 Md.use_editor Md.paths_mutt.man Md.muttbug_no_list Md.use_etc_mailname Md.muttbug_warning Md.gpg_status_fd patch-1.3.24.rr.compressed.1 patch-1.3.25.cd.edit_threads.9.1 patch-1.3.23.1.ametzler.pgp_good_sign >How-To-Repeat: >Fix: }}}" Bill Allombert 1717 "wish ""color indicator"" option to keep an underlying color" mutt enhancement mutt-dev new 2003-11-25T00:07:07-08:00 2007-04-07T07:22:25-07:00 "{{{ Package: mutt Version: mutt-1.5.3i.nntp-1 Severity: wishlist -- Please type your report below this line If I have arrow_cursor=no, I cannot see the colour of my index lines when they are selected. It would be nice if I could say: color indicator blue black # Set default indicator colours color indicator red black ""~d >1w"" # Set a different colour for old messages in the same way I can colour unselected lines. -- System Information System Version: Linux undarum.ipv6.moonseas.net 2.4.22-1.2115.nptl #1 Wed Oct 29 15:42:51 EST 2003 i686 i686 i386 GNU/Linux RedHat Release: Fedora Core release 1 (Yarrow) -- 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-redhat-linux/3.3.2/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.3.2 20031022 (Red Hat Linux 3.3.2-1) - CFLAGS -Wall -pedantic -O2 -g -pipe -march=i386 -mcpu=i686 -O0 -- Mutt Version Information Mutt 1.5.3i (2002-12-17) Copyright (C) 1996-2002 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.22-1.2115.nptl (i686) [using slang 10405] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_NNTP +USE_IMAP -USE_GSS +USE_SSL -USE_SASL -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +COMPRESSED +HAVE_COLOR -HAVE_START_COLOR -HAVE_TYPEAHEAD -HAVE_BKGDSET -HAVE_CURS_SET -HAVE_META -HAVE_RESIZETERM +HAVE_PGP +HAVE_SMIME -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 +USE_CACHE ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. 1.3.25-me.smtp.3 patch-1.5.3.wk.mdn.1 Bloat patch: X-Backlog 1.3.25 by Stefan `Sec` Zehl patch-1.5.1.cd.signatures_menu.2.1 patch-1.3.24.ats.parent_match.1 1.5.2-me.hcache.1 patch-1.5.3.dgc.groupalts.1 vvv.quote vvv.initials vvv.nntp rr.compressed dw.xface mh.xface >How-To-Repeat: >Fix: }}}" Luke Ross 1723 [PATCH] New tag ~M for message filename mutt 1.5.4i enhancement mutt-dev new 2003-12-02T01:31:47-08:00 2005-09-04T12:17:02-07:00 "{{{ Package: mutt Version: 1.5.4i Severity: wishlist -- Please type your report below this line I use MH folders so that I can have full-text indexing on certain ""hot"" folders. I moved to MH folders because with MBOX folders, all you get is the line number of matching messages, which is useless. With MH folders, you get the filename of the actual message, which is great! .. except that mutt doesn't expose the underlying message filename. Even in unordered mode, h->msgno is just some monotonically increasing integer. There is no way to query or limit messages based on their filenames, so I'm forced to do my search, open the message with an editor, read the Subject, then search on that. This is obviously no good. The attached patch (against mutt-1.5.5.1i) adds a new tag ~M for the message's path. It solves my problem by letting me cut out the middle step: given a filename, I can jump to that message immediately by searching for it. Feel free to use this patch in whatever way you see fit. I hereby put this patch into the public domain, etc, etc. Notes: * this version uses eat_regexp, which means you can't do a range of messages cleanly. (That's too bad for MH-style folders.) * this is probably useless for MBOX folders; all messages share one path. ----8<---- diff -ru mutt-1.5.5.1/mutt.h mutt-1.5.5.1-nw/mutt.h --- mutt-1.5.5.1/mutt.h Wed Nov 5 01:41:32 2003 +++ mutt-1.5.5.1-nw/mutt.h Tue Dec 2 00:59:34 2003 @@ -221,6 +221,7 @@ M_WHOLE_MSG, M_SENDER, M_MESSAGE, + M_PATH, M_SCORE, M_SIZE, M_REFERENCE, diff -ru mutt-1.5.5.1/pattern.c mutt-1.5.5.1-nw/pattern.c --- mutt-1.5.5.1/pattern.c Wed Nov 5 01:41:33 2003 +++ mutt-1.5.5.1-nw/pattern.c Tue Dec 2 00:59:46 2003 @@ -63,6 +63,7 @@ { 'L', M_ADDRESS, 0, eat_regexp }, { 'l', M_LIST, 0, NULL }, { 'm', M_MESSAGE, 0, eat_range }, + { 'M', M_PATH, 0, eat_regexp }, { 'n', M_SCORE, 0, eat_range }, { 'N', M_NEW, 0, NULL }, { 'O', M_OLD, 0, NULL }, @@ -981,6 +982,8 @@ case M_MESSAGE: return (pat->not ^ (h->msgno >= pat->min - 1 && (pat->max == M_MAXRANGE || h->msgno <= pat->max - 1))); + case M_PATH: + return (pat->not ^ (h->path && regexec (pat->rx, h->path, 0, NULL, 0) == 0)); case M_DATE: return (pat->not ^ (h->date_sent >= pat->min && h->date_sent <= pat->max)); case M_DATE_RECEIVED: End of Patch. ---->8---- -- System Information System Version: Linux alfalfa.activestate.com 2.4.20-19.9 #1 Tue Jul 15 17:18:13 EDT 2003 i686 i686 i386 GNU/Linux RedHat Release: Red Hat Linux release 9 (Shrike) -- 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-redhat-linux/3.2.2/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.4i (2003-03-19) Copyright (C) 1996-2002 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.20-19.9 (i686) [using ncurses 5.3] 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 -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID -HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/apps/mutt/1.5.4/share/mutt"" SYSCONFDIR=""/usr/local/apps/mutt/1.5.4/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. --- Begin /home/neilw/.muttrc set mbox_type=MH set autoedit=yes auto_view text/x-patch auto_view text/html set edit_headers unset confirmappend set delete=yes set envelope_from unset fcc_attach set hostname=""ActiveState.com"" set include=yes set indent_str=""> "" set index_format = ""%4C %Z %{%b %d} %-15.15F (%4c) %s"" # format of index set forward_format=""Fw: %s"" # subject to use when forwarding messages set date_format=""%d/%m/%y %H:%M %Z"" # format of date set quote_regexp=""^([|>:}#][ \t]*)+"" set mime_forward=ask-yes set pager_stop=yes set rfc2047_parameters=yes set edit_headers set editor=""vim +':set textwidth=77' +':set wrap' +\`awk '/^$/ {print i+2; exit} {i++}' %s\` %s"" set nomark_old set reply_to=yes unset save_empty set dsn_notify='failure,delay' # when to return an error message set dsn_return=hdrs # what to return in the error message set reverse_name set auto_tag set spoolfile=""~/.mail/i"" set folder=""~/.mail"" set postponed=""=postponed"" set record=""=sent-mail"" folder-hook . set sort=threads folder-hook . set 'attribution=""%n [%d]:""' folder-hook . set signature=~/.mutt/sig.default folder-hook . my_hdr From: neil.watkiss@sophos.com (Neil Watkiss) folder-hook . my_hdr Reply-To: neil.watkiss@sophos.com (Neil Watkiss) folder-hook . unmy_hdr Cc folder-hook . my_hdr Bcc: neil.watkiss@sophos.com (Neil Watkiss) folder-hook . my_hdr Organization: Sophos folder-hook . my_hdr X-Operating-System: `uname -mnrs` folder-hook . ""push \""l!(~s 'FOLDER INTERNAL DATA')\n*\"""" folder-hook . ignore * folder-hook . unignore From To Cc Subject Date Reply-To Organization folder-hook . unignore X-PMX-Spam X-PerlMx-Spam X-Mailer User-Agent folder-hook . hdr_order From: Date: To: Cc: Subject: folder-hook bugs my_hdr From: neilw@activestate.com (Neil Watkiss) folder-hook bugs my_hdr Bcc: neilw@activestate.com (Neil Watkiss) folder-hook bugs unmy_hdr Reply-To folder-hook bugs my_hdr Cc folder-hook p4$ ignore To Cc folder-hook p4$ hdr_order From: Date: Subject: folder-hook perlmx.support my_hdr From: PureMessage-Support@sophos.com (Neil Watkiss) folder-hook perlmx.support my_hdr Reply-To: PureMessage-Support@sophos.com (Neil Watkiss) folder-hook perlmx.support my_hdr Cc: PureMessage-Support@sophos.com folder-hook perlmx.support unmy_hdr Bcc folder-hook perlmx.support set sig_dashes=yes folder-hook perlmx.support set signature=~/.mutt/sig.perlmx-support set move=no macro generic ""!less /usr/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /usr/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /usr/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" set alias_file=~/.mutt/aliases source ~/.mutt/aliases source ~/.mutt/activators source ~/.mutt/colours --- End /home/neilw/.muttrc --- Begin /usr/local/apps/mutt/1.5.4/etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /usr/local/apps/mutt/1.5.4/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /usr/local/apps/mutt/1.5.4/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /usr/local/apps/mutt/1.5.4/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" --- End /usr/local/apps/mutt/1.5.4/etc/Muttrc >How-To-Repeat: >Fix: }}}" Neil Watkiss 1730 Wishlist: Sort by any header mutt 1.5.4i enhancement mutt-dev new 2003-12-07T01:21:25-08:00 2005-08-25T10:35:16-07:00 "{{{ Package: mutt Version: 1.3.25-1 Severity: wishlist I would love to see an option to be able to, on the fly, choose to sort the message index by any (user defined) header. This could for instance be useful to sort a mailbox by spam score (by choosing ""sort by header"" and then ""X-Spam-Level""), sort support mailboxes by headers inserted by support ticket tracking systems, etc.. >How-To-Repeat: >Fix: }}}" Pål Løberg 1827 No flag in index to indicated a forwarded message mutt 1.4.2i enhancement mutt-dev new 2004-03-09T04:47:50-08:00 2005-08-26T09:41:09-07:00 "{{{ Package: mutt Version: 1.4.2i Severity: wishlist -- Please type your report below this line When a mutt user forwards a message, no flag appears in the flags column of the index to indicate that the message has been forwarded. This leaves the user to rely on his fallible memory for that information. It could look something like this (assuming index_format=""%3C %Z %-35.35s %-15.15F %> %[%b %d %a] "": 55 fs The World's Funniest Joke John Ashcroft Mar 09 Tue where the ""f"" indicates that the user has forwarded this message. Perhaps a ""b"" flag could also be used to indicate bounced messages. -- 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//bin/../lib/gcc-lib/i586-mandrake-linux-gnu/3.2.2/specs Configured with: ../configure --prefix=/usr --libdir=/usr/lib --with-slibdir=/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --enable-long-long --enable-__cxa_atexit --enable-languages=c,c++,ada,f77,objc,java --host=i586-mandrake-linux-gnu --with-system-zlib Thread model: posix gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.4.2i (2004-02-11) Copyright (C) 1996-2002 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.6.1oss (i686) [using ncurses 5.3] 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 SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/bash"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. --- Begin /home/dle/.mutt/muttrc set folder =~/.mailbox set spoolfile =+inbox # Mail folder. set mbox_type=""mbox"" set mbox=""=inbox"" set realname = ""Dave Edwards"" set from = dle set signature = ""~/.sig"" # file that contains my signature ignore * unignore From: unignore Subject: unignore To: unignore Reply-To: unignore Cc: unignore Date: unignore Organization: hdr_order Subject: From From: To: Cc: Date: set edit_hdrs unset use_from my_hdr From: Dave Edwards my_hdr Organization: bigStory my_hdr X-24th-Letter: X set user_agent macro index d ""=trash\n"" macro pager d ""=trash\n"" macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!elinks /usr/local/doc/mutt/html/manual.html\n"" ""Show Mutt documentation"" macro index ""!elinks /usr/local/doc/mutt/html/manual.html\n"" ""Show Mutt documentation"" macro pager ""!elinks /usr/local/doc/mutt/html/manual.html\n"" ""Show Mutt documentation"" mailboxes ! mailboxes =inbox =OSW =OPAG =SCO =alsa =Canopener =Chess \ =Claws =Google =Linux-Consult =Louise =Mum \ =OCLUG =OCLUG.sbd/board =OCLUG.sbd/events \ =OCLUG.sbd/novice =OCLUG.sbd/archive =OCLUG.sbd/www \ =OGo =OpenOfficeDoc =Zfolder set fast_reply=yes set hostname=sympatico.ca set use_8bitmime set abort_nosubject=ask-yes set alias_file=""~/.mutt/aliases"" set pager_index_lines=6 set attribution=""On %d, %n wrote:"" set beep set beep_new set mh_purge set check_new set charset=""iso-8859-1"" unset confirmappend unset collapse_unread # don't collapse threads with unread mails set edit_headers # put headers in editor when composing messages set fcc_attach # store attachments too when doing an Fcc set confirmcreate set copy=yes set date_format=""!%a, %b %d, %Y at %I:%M:%S%p %Z"" set index_format=""%3C %Z %-35.35s %-15.15F %> %[%b %d %a] "" set editor=""vim -u /home/dle/.vimrc-mail +9"" set forward_format=""Fwd: %s"" set mark_old unset move set pager=""builtin"" set postponed=""~/.mailbox/postponed"" set quit=ask-yes set record=""~/.mailbox/sent"" unset save_empty set smileys=""(>From )|(:[-^]?[][)(><}{|/DP])"" set sort=threads #date-received set to_chars="" "" source ~/.mutt/bindings source ~/.mutt/aliases source ~/.mutt/send-hooks source ~/.mutt/folder-hooks source ~/.mutt/colours source ~/.mutt/mailing-lists source ~/.mutt/gpg --- End /home/dle/.mutt/muttrc --- Begin /home/dle/.mutt/colours color attachment magenta default # attachments color body brightred default ""(ftp|http)://[^ ]+"" # point out URLs color body brightcyan default [-a-z_0-9.]+@[-a-z_0-9.]+ # e-mail addresses color bold brightblue default # boldface text color error brightwhite red # error messages color hdrdefault brightmagenta default # default color of message header color header brightyellow default ^(From|Subject): # From and Subject header color indicator brightyellow default # indicator bar color markers brightblue default # wrapped line markers (+) color message black green # status messages color normal default default # default color quoted default default # quoted text, 1st quote level color quoted1 default default # quoted text, 2nd quote level color quoted2 default default # quoted text, 3rd quote level color quoted3 default default # quoted text, 4th quoet level color search black yellow # matched search patterns in pager color signature default default # the signature (after sigdashes) color status default blue # status lines color tilde brightblue default # ~ used to pad blank lines color tree green default # thread tree in the index menu color underline brightgreen default # underlined text color index brightred default ~F # flagged messages color index brightgreen default ~N # new messages uncolor index brightmagenta default ""~f dle.sym"" # uncolor msgs from me uncolor index brightmagenta default ""~f erratico.sym"" # uncolor msgs from me mono bold bold mono body bold ""(ftp|http)://[^ ]+"" # point out URLs mono body bold [-a-z_0-9.]+@[-a-z_0-9.]+ # e-mail addresses mono header underline ^(From|Subject): mono quoted bold # quoted text, 1st quote level mono underline underline # vim: filetype=muttrc --- End /home/dle/.mutt/colours --- Begin /home/dle/.mutt/gpg # GPG Stuff # ~~~~~~~~~ unset pgp_autoencrypt # pgp encrypt every outgoing mail unset pgp_show_unusable # show unusable PGP keys in menu set pgp_autosign=yes # pgp sign every outgoing mail set pgp_sign_as=0x8E360320 set pgp_ignore_subkeys # ignore OpenPGP subkeys unset pgp_long_ids # display 64bit PGP key-ids set pgp_replyencrypt=yes # Encrypt replies on encrypted mail set pgp_replysign=yes # Sign replies on signed mail set pgp_replysignencrypted=yes# Sign replies on encrypted mail set pgp_retainable_sigs # retainable signatures unset pgp_show_unusable # show unusable PGP keys in menu unset pgp_strict_enc # allway use QP enc. with PGP unset fcc_clear # sent mail is stored encrypted and signed set pgp_timeout=3600 # forget PGP passphrase after X sec set pgp_verify_sig=yes # a macro for clearsigning macro compose S ""Fgpg --clearsign -u 8E360320"" # GnuPG configuration #set pgp_sign_micalg=pgp-sha1 # default for DSS keys set pgp_decode_command=""gpg %?p?--passphrase-fd 0? --no-verbose --batch --output - %f"" set pgp_verify_command=""gpg --no-verbose --batch --output - --verify %s %f"" set pgp_decrypt_command=""gpg --passphrase-fd 0 --no-verbose --batch --output - %f"" set pgp_sign_command=""gpg --no-verbose --batch --output - --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a? %f"" set pgp_clearsign_command=""gpg --no-verbose --batch --output - --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f"" set pgp_encrypt_only_command=""/usr/bin/pgpewrap gpg -v --batch --output - --encrypt --textmode --armor --always-trust --encrypt-to 0x8E360320 -- -r %r -- %f"" set pgp_encrypt_sign_command=""/usr/bin/pgpewrap gpg --passphrase-fd 0 -v --batch --output - --encrypt --sign %?a?-u %a? --armor --always-trust --encrypt-to 0x8E360320 -- -r %r --%f"" set pgp_import_command=""gpg --no-verbose --import -v %f"" set pgp_export_command=""gpg --no-verbose --export --armor %r"" set pgp_verify_key_command=""gpg --no-verbose --batch --fingerprint --check-sigs %r"" set pgp_list_pubring_command=""gpg --no-verbose --batch --with-colons --list-keys %r"" set pgp_list_secring_command=""gpg --no-verbose --batch --with-colons --list-secret-keys %r"" set pgp_getkeys_command="""" set pgp_good_sign=""^gpg: Good signature from "" # String/Regex set pgp_good_sign=""^gpg: Good signature from"" set pgp_sort_keys=address # (address, keyid, date, trust) reset pgp_sign_as # UserID/KeyID for signing # set pgp_create_traditional=yes # set pgp_encryptself # unset pgp_long_ids # unset pgp_replyencrypt # unset pgp_replysign # set pgp_sign_as="""" # set pgp_sign_micalg=""pgp-md5"" # set pgp_strict_enc #set pgp_default_version=""gpg"" # (Not really the default, but...) # vim: syntax=muttrc: --- Begin /usr/local/etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /usr/local/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" --- End /usr/local/etc/Muttrc >How-To-Repeat: >Fix: }}}" dle@… 1841 message-hook NOOP For Attached Message mutt 1.5.6i enhancement mutt-dev new 2004-03-30T13:30:16-08:00 2005-08-26T09:55:42-07:00 "{{{ Package: mutt Version: 1.5.6i Severity: normal -- Please type your report below this line Well, I've got message-hook mania, setting and unsetting stuff based on all sorts of criteria when viewing a message. I just noticed that when somebody forwards me a message as an attachment and I view it, the settings of the parent message hold, not of the child one (the one I'm viewing). Considering the fact that these types of attachments are first-class messages in almost all other ways, I find it particularly annoying that they aren't in this most obvious (and rather basic, when you think of it for a second) way. Thanks, - Dave BTW - My entire Mutt configuration directory is online: http://www.bigfatdave.com/dave/mutt/muttdir/ -- System Information System Version: Linux dave2 2.4.25+fuse #5 SMP Sun Mar 14 00:57:36 EST 2004 i686 unknown unknown GNU/Linux -- 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 Leyendo especificaciones de /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/specs Configurado con: ./configure --enable-version-specific-runtime-libs --enable-languages=c,c++ Modelo de hilos: posix gcc versión 3.2.3 - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.5.6i (2004-02-01) Copyright (C) 1996-2002 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.25+fuse (i686) [using ncurses 5.3] Opciones especificadas al compilar: -DOMAIN +DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP +USE_IMAP -USE_GSS +USE_SSL -USE_SASL -USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/bin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/deta/mutt_cvs/usr/share/mutt"" SYSCONFDIR=""/deta/mutt_cvs/usr/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER Para contactar a los desarrolladores mande un mensaje a . Para reportar un fallo use la utilería flea(1) por favor. --- Begin /home/dave/.muttrc source ~/.mutt/muttrc --- End /home/dave/.muttrc --- Begin /deta/mutt_cvs/usr/etc/Muttrc ignore ""from "" received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic ""!less /beta/mutt_cvs/usr/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro index ""!less /beta/mutt_cvs/usr/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" macro pager ""!less /beta/mutt_cvs/usr/doc/mutt/manual.txt\n"" ""Show Mutt documentation"" --- End /deta/mutt_cvs/usr/etc/Muttrc >How-To-Repeat: >Fix: }}}" lists+mutt_bugs_submit@… 1861 colors within $status_format not yet possible display enhancement mutt-dev new 2004-04-19T04:04:38-07:00 2007-04-09T22:42:50-07:00 "{{{ Package: mutt Version: 1.5.5.1-20040112+1 Severity: wishlist [NOTE: this bug report has been submitted to the debian BTS as Bug#244428. Please Cc all your replies to 244428@bugs.debian.org .] From: Grant Bowman Subject: mutt: colors within $status_format not yet possible Date: Sun, 18 Apr 2004 06:01:04 -0700 Hi Marco, Mutt is very capable with colors for many tasks. The capability to color each item is very useful and I use it alot. However there is one highly visible UI string that could use embedded color codes: $status_format. I didn't see any patch, hint in the mutt source code or description (googling) anywhere of how to get color (and perhaps bold codes) embedded within the string. Status lines are ideal places to use color to diferentiate and contrast different data elements that are more or less important. I'm on a roll now, having spent quite a bit of time to synchronize the configurations of irssi and vim to use colors (with similar semantic meanings) within their status strings to great effect. Keep up the good work, -- -- Grant Bowman -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.3-1-386 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 Versions of packages mutt depends on: ii exim4-daemon-light [mail-tr 4.30-8 Lightweight version of the Exim (v ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libidn11 0.4.1-1 GNU libidn library, implementation ii libncursesw5 5.4-3 Shared libraries for terminal hand ii libsasl2 2.1.15-6 Authentication abstraction library >How-To-Repeat: >Fix: }}}" Marco d'Itri 1867 Port patch-1.5.1-de.threads_config.1 to current dev tree? mutt 1.5.6i enhancement mutt-dev new 2004-05-02T19:33:58-07:00 2007-04-07T07:34:50-07:00 "{{{ Package: mutt Version: mutt-1.5.6.cvs-1mk Severity: wishlist -- Please type your report below this line A while ago, Daniel Eisenbud wrote a great mutt threading patch, named ""patch-1.5.1-de.threads_config.1"". It separated out the configuration of threading from the other sorting options, and generally improved the threading and sorting system. The patch was posted in the thread starting at . It would be sweet to have this patch ported to the current tree and integrated. I ported this patch myself a couple of times, and includes my latest incarnation below, but it seems to lose mail when I save messages to a folder, and I don't understand this code well enough yet to debug it. Thanks. --- cut here --- Index: commands.c =================================================================== RCS file: /home/roessler/cvs/mutt/commands.c,v retrieving revision 3.23 diff -u -d -r3.23 commands.c --- commands.c 12 Apr 2004 20:33:33 -0000 3.23 +++ commands.c 2 May 2004 18:30:20 -0000 @@ -498,56 +498,73 @@ int mutt_select_sort (int reverse) { - int method = Sort; /* save the current method in case of abort */ + int method = Sort, threadmethod = Threads, new; - switch (mutt_multi_choice (reverse ? - _(""Rev-Sort (d)ate/(f)rm/(r)ecv/(s)ubj/t(o)/(t)hread/(u)nsort/si(z)e/s(c)ore?: "") : - _(""Sort (d)ate/(f)rm/(r)ecv/(s)ubj/t(o)/(t)hread/(u)nsort/si(z)e/s(c)ore?: ""), - _(""dfrsotuzc""))) + new = mutt_multi_choice (reverse ? + _(""Rev-Sort (d)ate/(f)rm/(r)ecv/(s)ubj/t(o)/(t)hread/(u)nsort/si(z)e/s(c)ore?: "") : + _(""Sort (d)ate/(f)rm/(r)ecv/(s)ubj/t(o)/(t)hread/(u)nsort/si(z)e/s(c)ore?: ""), + _(""dfrsotuzc"")); + + switch (new) { - case -1: /* abort - don't resort */ - return -1; + case -1: /* abort - don't resort */ + return -1; - case 1: /* (d)ate */ - Sort = SORT_DATE; - break; + case 1: /* (d)ate */ + Sort = SORT_DATE; + break; - case 2: /* (f)rm */ - Sort = SORT_FROM; - break; - - case 3: /* (r)ecv */ - Sort = SORT_RECEIVED; - break; - - case 4: /* (s)ubj */ - Sort = SORT_SUBJECT; - break; - - case 5: /* t(o) */ - Sort = SORT_TO; - break; - - case 6: /* (t)hread */ - Sort = SORT_THREADS; - break; - - case 7: /* (u)nsort */ - Sort = SORT_ORDER; - break; - - case 8: /* si(z)e */ - Sort = SORT_SIZE; - break; + case 2: /* (f)rm */ + Sort = SORT_FROM; + break; + + case 3: /* (r)ecv */ + Sort = SORT_RECEIVED; + break; + + case 4: /* (s)ubj */ + Sort = SORT_SUBJECT; + break; + + case 5: /* t(o) */ + Sort = SORT_TO; + break; + + case 6: /* (t)hread */ + if ((Threads & SORT_MASK) == SORT_NOTHREADS) + { + Threads = SORT_THREADS; /* leave last- or first- if just toggling dir */ + Sort = SORT_DATE; + } + + if (reverse) + Threads |= SORT_REVERSE; + else + Threads &= ~SORT_REVERSE; + + break; + + case 7: /* (u)nsort */ + Sort = SORT_ORDER; + break; + + case 8: /* si(z)e */ + Sort = SORT_SIZE; + break; + + case 9: /* s(c)ore */ + Sort = SORT_SCORE; + break; + } - case 9: /* s(c)ore */ - Sort = SORT_SCORE; - break; + if (new != 6) + { + if (reverse) + Sort |= SORT_REVERSE; + Threads = SORT_NOTHREADS; } - if (reverse) - Sort |= SORT_REVERSE; - return (Sort != method ? 0 : -1); /* no need to resort if it's the same */ + return ((Sort != method || Threads != threadmethod) ? 0 : -1); /* no need to resort if it's the same */ } /* invoke a command in a subshell */ Index: curs_main.c =================================================================== RCS file: /home/roessler/cvs/mutt/curs_main.c,v retrieving revision 3.17 diff -u -d -r3.17 curs_main.c --- curs_main.c 12 Apr 2004 20:33:33 -0000 3.17 +++ curs_main.c 2 May 2004 18:30:20 -0000 @@ -106,11 +106,11 @@ void index_make_entry (char *s, size_t l, MUTTMENU *menu, int num) { format_flag flag = M_FORMAT_MAKEPRINT | M_FORMAT_ARROWCURSOR | M_FORMAT_INDEX; - int edgemsgno, reverse = Sort & SORT_REVERSE; + int edgemsgno, reverse = Threads & SORT_REVERSE; HEADER *h = Context->hdrs[Context->v2r[num]]; THREAD *tmp; - if ((Sort & SORT_MASK) == SORT_THREADS && h->tree) + if ((Threads & SORT_MASK) != SORT_NOTHREADS && h->tree) { flag |= M_FORMAT_TREE; /* display the thread tree */ if (h->display_subject) @@ -223,9 +223,8 @@ * If Sort is threaded, the latest message is first iff exactly one * of Sort and SortAux are reverse. */ - if (((Sort & SORT_REVERSE) && (Sort & SORT_MASK) != SORT_THREADS) || - ((Sort & SORT_MASK) == SORT_THREADS && - ((Sort ^ SortAux) & SORT_REVERSE))) + if ((Threads != SORT_NOTHREADS && (Threads & SORT_REVERSE)) ^ + (Sort & SORT_REVERSE)) return 0; else return (Context->vcount ? Context->vcount - 1 : 0); @@ -302,7 +301,7 @@ /* save the list of new messages */ if (oldcount && check != M_REOPENED - && ((Sort & SORT_MASK) == SORT_THREADS)) + && ((Threads & SORT_MASK) != SORT_NOTHREADS)) { save_new = (HEADER **) safe_malloc (sizeof (HEADER *) * (Context->msgcount - oldcount)); for (j = oldcount; j < Context->msgcount; j++) @@ -313,7 +312,7 @@ mutt_sort_headers (Context, (check == M_REOPENED)); /* uncollapse threads with new mail */ - if ((Sort & SORT_MASK) == SORT_THREADS) + if ((Threads & SORT_MASK) != SORT_NOTHREADS) { if (check == M_REOPENED) { @@ -384,7 +383,7 @@ } } - if ((Sort & SORT_MASK) == SORT_THREADS && menu->current < 0) + if ((Threads & SORT_MASK) != SORT_NOTHREADS && menu->current < 0) menu->current = mutt_parent_message (Context, current); if (menu->current < 0) @@ -451,7 +450,7 @@ if (option (OPTNEEDRESORT) && Context && Context->msgcount) resort_index (menu); - if (option (OPTREDRAWTREE) && Context && Context->msgcount && (Sort & SORT_MASK) == SORT_THREADS) + if (option (OPTREDRAWTREE) && Context && Context->msgcount && (Threads & SORT_MASK) != SORT_NOTHREADS) { mutt_draw_tree (Context); menu->redraw |= REDRAW_STATUS; @@ -851,7 +850,7 @@ else menu->current = 0; menu->redraw = REDRAW_INDEX | REDRAW_STATUS; - if ((Sort & SORT_MASK) == SORT_THREADS) + if ((Threads & SORT_MASK) != SORT_NOTHREADS) mutt_draw_tree (Context); menu->redraw = REDRAW_FULL; } @@ -911,6 +910,7 @@ { if (Context && Context->msgcount) { + set_option (OPTSORTSUBTHREADS); resort_index (menu); set_option (OPTSEARCHINVALID); } @@ -1124,7 +1124,7 @@ unset_option (OPTNEEDRESORT); - if ((Sort & SORT_MASK) == SORT_THREADS && CURHDR->collapsed) + if ((Threads & SORT_MASK) != SORT_NOTHREADS && CURHDR->collapsed) { mutt_uncollapse_thread (Context, CURHDR); mutt_set_virtual (Context); @@ -1344,7 +1344,7 @@ } } - if (CURHDRi->collapsed && (Sort & SORT_MASK) == SORT_THREADS) + if (CURHDRi->collapsed && (Threads & SORT_MASK) != SORT_NOTHREADS) { if (UNREAD (CURHDRi) && first_unread == -1) first_unread = i; @@ -1592,7 +1592,7 @@ CHECK_MSGCOUNT; CHECK_VISIBLE; - if ((Sort & SORT_MASK) != SORT_THREADS) + if ((Threads & SORT_MASK) == SORT_NOTHREADS) { mutt_error _(""Threading is not enabled.""); break; @@ -1624,7 +1624,7 @@ CHECK_MSGCOUNT; CHECK_VISIBLE; - if ((Sort & SORT_MASK) != SORT_THREADS) + if ((Threads & SORT_MASK) == SORT_NOTHREADS) { mutt_error _(""Threading is not enabled.""); break; Index: flags.c =================================================================== RCS file: /home/roessler/cvs/mutt/flags.c,v retrieving revision 3.3 diff -u -d -r3.3 flags.c --- flags.c 30 Jan 2003 23:48:36 -0000 3.3 +++ flags.c 2 May 2004 18:30:20 -0000 @@ -284,7 +284,7 @@ { THREAD *start, *cur = hdr->thread; - if ((Sort & SORT_MASK) != SORT_THREADS) + if ((Threads & SORT_MASK) == SORT_NOTHREADS) { mutt_error _(""Threading is not enabled.""); return (-1); Index: hdrline.c =================================================================== RCS file: /home/roessler/cvs/mutt/hdrline.c,v retrieving revision 3.11 diff -u -d -r3.11 hdrline.c --- hdrline.c 1 Feb 2004 17:10:43 -0000 3.11 +++ hdrline.c 2 May 2004 18:30:20 -0000 @@ -236,7 +236,7 @@ char fmt[SHORT_STRING], buf2[SHORT_STRING], ch, *p; int do_locales, i; int optional = (flags & M_FORMAT_OPTIONAL); - int threads = ((Sort & SORT_MASK) == SORT_THREADS); + int threads = ((Threads & SORT_MASK) != SORT_NOTHREADS); int is_index = (flags & M_FORMAT_INDEX); #define THREAD_NEW (threads && hdr->collapsed && hdr->num_hidden > 1 && mutt_thread_contains_unread (ctx, hdr) == 1) #define THREAD_OLD (threads && hdr->collapsed && hdr->num_hidden > 1 && mutt_thread_contains_unread (ctx, hdr) == 2) Index: init.c =================================================================== RCS file: /home/roessler/cvs/mutt/init.c,v retrieving revision 3.22 diff -u -d -r3.22 init.c --- init.c 12 Apr 2004 19:42:10 -0000 3.22 +++ init.c 2 May 2004 18:30:21 -0000 @@ -756,12 +756,6 @@ flags = SORT_REVERSE; } - if (mutt_strncmp (""last-"", s, 5) == 0) - { - s += 5; - flags |= SORT_LAST; - } - if ((i = mutt_getvaluebyname (s, map)) == -1) { snprintf (err->data, err->dsize, _(""%s: unknown sorting method""), s); @@ -1299,8 +1293,8 @@ if ((WithCrypto & APPLICATION_PGP)) map = SortKeyMethods; break; - case DT_SORT_AUX: - map = SortAuxMethods; + case DT_SORT_THREADS: + map = ThreadMethods; break; default: map = SortMethods; @@ -1318,10 +1312,8 @@ { p = mutt_getnamebyvalue (*((short *) MuttVars[idx].data) & SORT_MASK, map); - snprintf (err->data, err->dsize, ""%s=%s%s%s"", MuttVars[idx].option, - (*((short *) MuttVars[idx].data) & SORT_REVERSE) ? ""reverse-"" : """", - (*((short *) MuttVars[idx].data) & SORT_LAST) ? ""last-"" : """", - p); + snprintf (err->data, err->dsize, ""%s=%s%s"", MuttVars[idx].option, + (*((short *) MuttVars[idx].data) & SORT_REVERSE) ? ""reverse-"" : """", p); return 0; } s->dptr++; @@ -1746,6 +1738,9 @@ case DT_SORT_BROWSER: map = SortBrowserMethods; break; + case DT_SORT_THREADS: + map = ThreadMethods; + break; case DT_SORT_KEYS: if ((WithCrypto & APPLICATION_PGP)) map = SortKeyMethods; @@ -1757,10 +1752,8 @@ break; } p = mutt_getnamebyvalue (*((short *) MuttVars[idx].data) & SORT_MASK, map); - snprintf (tmp, sizeof (tmp), ""%s%s%s"", - (*((short *) MuttVars[idx].data) & SORT_REVERSE) ? ""reverse-"" : """", - (*((short *) MuttVars[idx].data) & SORT_LAST) ? ""last-"" : """", - p); + snprintf (tmp, sizeof (tmp), ""%s%s"", + (*((short *) MuttVars[idx].data) & SORT_REVERSE) ? ""reverse-"" : """", p); } else if (DTYPE (MuttVars[idx].type) == DT_BOOL) strfcpy (tmp, option (MuttVars[idx].data) ? ""yes"" : ""no"", sizeof (tmp)); Index: init.h =================================================================== RCS file: /home/roessler/cvs/mutt/init.h,v retrieving revision 3.47 diff -u -d -r3.47 init.h --- init.h 13 Apr 2004 08:02:12 -0000 3.47 +++ init.h 2 May 2004 18:30:21 -0000 @@ -44,7 +44,7 @@ #define DT_SORT_ALIAS 0x10 #define DT_SORT_BROWSER 0x20 #define DT_SORT_KEYS 0x40 -#define DT_SORT_AUX 0x80 +#define DT_SORT_THREADS 0x80 /* flags to parse_set() */ #define M_SET_INV (1<<0) /* default is to invert all vars */ @@ -2329,7 +2329,7 @@ ** messages from the current folder. The default is to pause one second, so ** a value of zero for this option suppresses the pause. */ - { ""sort"", DT_SORT, R_INDEX|R_RESORT, UL &Sort, SORT_DATE }, + { ""sort"", DT_SORT, R_INDEX|R_RESORT_BOTH, UL &Sort, SORT_DATE }, /* ** .pp ** Specifies how to sort messages in the \fIindex\fP menu. Valid values @@ -2362,7 +2362,7 @@ ** . unsorted (leave in order specified in .muttrc) ** .te */ - { ""sort_aux"", DT_SORT|DT_SORT_AUX, R_INDEX|R_RESORT_BOTH, UL &SortAux, SORT_DATE }, + { ""sort_aux"", DT_SORT, R_INDEX|R_RESORT_BOTH, UL &SortAux, SORT_DATE }, /* ** .pp ** When sorting by threads, this variable controls how threads are sorted @@ -2429,7 +2429,7 @@ ** message mode (Certain operations like composing a new mail, replying, ** forwarding, etc. are not permitted in this mode). */ - { ""status_format"", DT_STR, R_BOTH, UL &Status, UL ""-%r-Mutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---"" }, + { ""status_format"", DT_STR, R_BOTH, UL &Status, UL ""-%r-Mutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%?T?%T/?%s%?S?/%S?)-%>-(%P)---"" }, /* ** .pp ** Controls the format of the status line displayed in the \fIindex\fP @@ -2456,6 +2456,7 @@ ** .dt %s .dd current sorting mode ($$sort) ** .dt %S .dd current aux sorting method ($$sort_aux) ** .dt %t .dd number of tagged messages * + ** .dt %T .dd current threading method ($$thread) ** .dt %u .dd number of unread messages * ** .dt %v .dd Mutt version string ** .dt %V .dd currently active limit pattern, if any * @@ -2531,6 +2532,23 @@ ** .pp ** Note that $$indent_string is ignored when this option is set. */ + { ""threads"", DT_SORT|DT_SORT_THREADS, R_INDEX|R_RESORT_BOTH, UL &Threads, SORT_NOTHREADS }, + /* + ** .pp + ** Specifies how to thread messages in the \fIindex\fP menu. Valid values + ** are: + ** .pp + ** .ts + ** . off + ** . threads + ** . lthreads + ** . first-threads + ** . last-threads + ** .te + ** .pp + ** You may optionally use the reverse- prefix to specify reverse threading + ** order (example: set sort=reverse-last-threads). + */ { ""thread_received"", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTTHREADRECEIVED, 0 }, /* ** .pp @@ -2703,30 +2721,19 @@ { ""subject"", SORT_SUBJECT }, { ""from"", SORT_FROM }, { ""size"", SORT_SIZE }, - { ""threads"", SORT_THREADS }, { ""to"", SORT_TO }, { ""score"", SORT_SCORE }, { NULL, 0 } }; -/* same as SortMethods, but with ""threads"" replaced by ""date"" */ - -const struct mapping_t SortAuxMethods[] = { - { ""date"", SORT_DATE }, - { ""date-sent"", SORT_DATE }, - { ""date-received"", SORT_RECEIVED }, - { ""mailbox-order"", SORT_ORDER }, - { ""subject"", SORT_SUBJECT }, - { ""from"", SORT_FROM }, - { ""size"", SORT_SIZE }, - { ""threads"", SORT_DATE }, /* note: sort_aux == threads - * isn't possible. - */ - { ""to"", SORT_TO }, - { ""score"", SORT_SCORE }, +const struct mapping_t ThreadMethods[] = { + { ""off"", SORT_NOTHREADS }, + { ""threads"", SORT_THREADS }, + { ""lthreads"", SORT_LTHREADS }, + { ""last-threads"", SORT_LASTTHREADS }, + { ""first-threads"", SORT_FIRSTTHREADS }, { NULL, 0 } }; - const struct mapping_t SortBrowserMethods[] = { { ""alpha"", SORT_SUBJECT }, Index: score.c =================================================================== RCS file: /home/roessler/cvs/mutt/score.c,v retrieving revision 3.2 diff -u -d -r3.2 score.c --- score.c 11 Dec 2002 11:19:40 -0000 3.2 +++ score.c 2 May 2004 18:30:21 -0000 @@ -42,7 +42,7 @@ (SortAux & SORT_MASK) == SORT_SCORE) { set_option (OPTNEEDRESORT); - if ((Sort & SORT_MASK) == SORT_THREADS) + if ((Threads & SORT_MASK) != SORT_NOTHREADS) set_option (OPTSORTSUBTHREADS); } Index: sort.c =================================================================== RCS file: /home/roessler/cvs/mutt/sort.c,v retrieving revision 3.5 diff -u -d -r3.5 sort.c --- sort.c 12 Nov 2003 11:40:27 -0000 3.5 +++ sort.c 2 May 2004 18:30:21 -0000 @@ -25,44 +25,42 @@ #include #include -#define SORTCODE(x) (Sort & SORT_REVERSE) ? -(x) : x - -/* function to use as discriminator when normal sort method is equal */ -static sort_t *AuxSort = NULL; +#define SORTCODE(x) ((Sort & SORT_REVERSE) ? -(x) : (x)) -#define AUXSORT(code,a,b) if (!code && AuxSort && !option(OPTAUXSORT)) { \ +#define AUXSORT(code,a,b) if (!code && !option(OPTAUXSORT)) { \ set_option(OPTAUXSORT); \ - code = AuxSort(a,b); \ + if (!AuxSort || !(code = (*AuxSort)((a),(b)))) \ + code = SORTCODE ((*((HEADER **)(a)))->index - (*((HEADER **)(b)))->index); \ + if ((Sort ^ SortAux) & SORT_REVERSE) \ + code = -code; \ unset_option(OPTAUXSORT); \ -} \ -if (!code) \ - code = (*((HEADER **)a))->index - (*((HEADER **)b))->index; +} int compare_score (const void *a, const void *b) { HEADER **pa = (HEADER **) a; HEADER **pb = (HEADER **) b; - int result = (*pb)->score - (*pa)->score; /* note that this is reverse */ + int result = SORTCODE ((*pb)->score - (*pa)->score); /* note that this is reverse */ AUXSORT(result,a,b); - return (SORTCODE (result)); + return (result); } int compare_size (const void *a, const void *b) { HEADER **pa = (HEADER **) a; HEADER **pb = (HEADER **) b; - int result = (*pa)->content->length - (*pb)->content->length; + int result = SORTCODE ((*pa)->content->length - (*pb)->content->length); AUXSORT(result,a,b); - return (SORTCODE (result)); + return (result); } int compare_date_sent (const void *a, const void *b) { HEADER **pa = (HEADER **) a; HEADER **pb = (HEADER **) b; - int result = (*pa)->date_sent - (*pb)->date_sent; + int result = SORTCODE ((*pa)->date_sent - (*pb)->date_sent); AUXSORT(result,a,b); - return (SORTCODE (result)); + return (result); } int compare_subject (const void *a, const void *b) @@ -82,8 +80,9 @@ rc = 1; else rc = mutt_strcasecmp ((*pa)->env->real_subj, (*pb)->env->real_subj); + rc = SORTCODE (rc); AUXSORT(rc,a,b); - return (SORTCODE (rc)); + return (rc); } const char *mutt_get_name (ADDRESS *a) @@ -112,9 +111,9 @@ fa = mutt_get_name ((*ppa)->env->to); fb = mutt_get_name ((*ppb)->env->to); - result = mutt_strcasecmp (fa, fb); + result = SORTCODE (mutt_strcasecmp (fa, fb)); AUXSORT(result,a,b); - return (SORTCODE (result)); + return (result); } int compare_from (const void *a, const void *b) @@ -126,18 +125,18 @@ fa = mutt_get_name ((*ppa)->env->from); fb = mutt_get_name ((*ppb)->env->from); - result = mutt_strcasecmp (fa, fb); + result = SORTCODE (mutt_strcasecmp (fa, fb)); AUXSORT(result,a,b); - return (SORTCODE (result)); + return (result); } int compare_date_received (const void *a, const void *b) { HEADER **pa = (HEADER **) a; HEADER **pb = (HEADER **) b; - int result = (*pa)->received - (*pb)->received; + int result = SORTCODE ((*pa)->received - (*pb)->received); AUXSORT(result,a,b); - return (SORTCODE (result)); + return (result); } int compare_order (const void *a, const void *b) @@ -217,31 +216,32 @@ if (init && ctx->tree) mutt_clear_threads (ctx); - if ((Sort & SORT_MASK) == SORT_THREADS) + sortfunc = mutt_get_sort_func (Sort); + AuxSort = mutt_get_sort_func (SortAux); + if ((Threads & SORT_MASK) != SORT_NOTHREADS) { - AuxSort = NULL; - /* if $sort_aux changed after the mailbox is sorted, then all the - subthreads need to be resorted */ + /* if $sort or $sort_aux changed after the mailbox is sorted, then all the + * subthreads need to be resorted */ if (option (OPTSORTSUBTHREADS)) { - i = Sort; - Sort = SortAux; if (ctx->tree) ctx->tree = mutt_sort_subthreads (ctx->tree, 1); - Sort = i; unset_option (OPTSORTSUBTHREADS); } mutt_sort_threads (ctx, init); } - else if ((sortfunc = mutt_get_sort_func (Sort)) == NULL || - (AuxSort = mutt_get_sort_func (SortAux)) == NULL) + else if (!sortfunc || !AuxSort) { mutt_error _(""Could not find sorting function! [report this bug]""); mutt_sleep (1); return; } else + { + if (sortfunc == AuxSort) + AuxSort = NULL; qsort ((void *) ctx->hdrs, ctx->msgcount, sizeof (HEADER *), sortfunc); + } /* adjust the virtual message numbers */ ctx->vcount = 0; @@ -258,7 +258,7 @@ } /* re-collapse threads marked as collapsed */ - if ((Sort & SORT_MASK) == SORT_THREADS) + if ((Threads & SORT_MASK) != SORT_NOTHREADS) { top = ctx->tree; while ((thread = top) != NULL) Index: sort.h =================================================================== RCS file: /home/roessler/cvs/mutt/sort.h,v retrieving revision 3.2 diff -u -d -r3.2 sort.h --- sort.h 21 Jan 2003 12:33:41 -0000 3.2 +++ sort.h 2 May 2004 18:30:21 -0000 @@ -16,22 +16,25 @@ * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA. */ -#define SORT_DATE 1 /* the date the mail was sent. */ -#define SORT_SIZE 2 -#define SORT_SUBJECT 3 -#define SORT_FROM 4 -#define SORT_ORDER 5 /* the order the messages appear in the mailbox. */ -#define SORT_THREADS 6 -#define SORT_RECEIVED 7 /* when the message were delivered locally */ -#define SORT_TO 8 -#define SORT_SCORE 9 -#define SORT_ALIAS 10 -#define SORT_ADDRESS 11 -#define SORT_KEYID 12 -#define SORT_TRUST 13 -#define SORT_MASK 0xf -#define SORT_REVERSE (1<<4) -#define SORT_LAST (1<<5) +#define SORT_DATE 1 /* the date the mail was sent. */ +#define SORT_SIZE 2 +#define SORT_SUBJECT 3 +#define SORT_FROM 4 +#define SORT_ORDER 5 /* the order the messages appear in the mailbox. */ +#define SORT_RECEIVED 6 /* when the message were delivered locally */ +#define SORT_TO 7 +#define SORT_SCORE 8 +#define SORT_NOTHREADS 9 +#define SORT_THREADS 10 +#define SORT_LTHREADS 11 +#define SORT_LASTTHREADS 12 +#define SORT_FIRSTTHREADS 13 +#define SORT_ALIAS 14 +#define SORT_ADDRESS 15 +#define SORT_KEYID 16 +#define SORT_TRUST 17 +#define SORT_MASK 0x1f +#define SORT_REVERSE (1<<5) typedef int sort_t (const void *, const void *); sort_t *mutt_get_sort_func (int); @@ -45,10 +48,13 @@ WHERE short BrowserSort INITVAL (SORT_SUBJECT); WHERE short Sort INITVAL (SORT_DATE); WHERE short SortAux INITVAL (SORT_DATE); /* auxiallary sorting method */ +WHERE short Threads INITVAL (SORT_NOTHREADS); /* auxiliary sorting method */ WHERE short SortAlias INITVAL (SORT_ALIAS); +WHERE sort_t *AuxSort INITVAL (NULL); /* FIXME: This one does not belong to here */ WHERE short PgpSortKeys INITVAL (SORT_ADDRESS); #include ""mapping.h"" extern const struct mapping_t SortMethods[]; +extern const struct mapping_t ThreadMethods[]; Index: status.c =================================================================== RCS file: /home/roessler/cvs/mutt/status.c,v retrieving revision 3.1 diff -u -d -r3.1 status.c --- status.c 11 Dec 2002 11:19:40 -0000 3.1 +++ status.c 2 May 2004 18:30:21 -0000 @@ -27,12 +27,11 @@ #include #include -static char *get_sort_str (char *buf, size_t buflen, int method) +static char *get_sort_str (char *buf, size_t buflen, int method, const struct mapping_t *methods) { - snprintf (buf, buflen, ""%s%s%s"", + snprintf (buf, buflen, ""%s%s"", (method & SORT_REVERSE) ? ""reverse-"" : """", - (method & SORT_LAST) ? ""last-"" : """", - mutt_getnamebyvalue (method & SORT_MASK, SortMethods)); + mutt_getnamebyvalue (method & SORT_MASK, methods)); return buf; } @@ -51,6 +50,7 @@ * %s = current sorting method ($sort) * %S = current aux sorting method ($sort_aux) * %t = # of tagged messages [option] + * %T = current threading method ($threads) * %v = Mutt version * %V = currently active limit pattern [option] */ static const char * @@ -228,13 +228,18 @@ case 's': snprintf (fmt, sizeof (fmt), ""%%%ss"", prefix); snprintf (buf, buflen, fmt, - get_sort_str (tmp, sizeof (tmp), Sort)); + get_sort_str (tmp, sizeof (tmp), Sort, SortMethods)); break; case 'S': - snprintf (fmt, sizeof (fmt), ""%%%ss"", prefix); - snprintf (buf, buflen, fmt, - get_sort_str (tmp, sizeof (tmp), SortAux)); + if (!optional) + { + snprintf (fmt, sizeof (fmt), ""%%%ss"", prefix); + snprintf (buf, buflen, fmt, + get_sort_str (tmp, sizeof (tmp), SortAux, SortMethods)); + } + else if ((SortAux & SORT_MASK) == (Sort & SORT_MASK)) + optional = 0; break; case 't': @@ -244,6 +249,17 @@ snprintf (buf, buflen, fmt, Context ? Context->tagged : 0); } else if (!Context || !Context->tagged) + optional = 0; + break; + + case 'T': + if (!optional) + { + snprintf (fmt, sizeof (fmt), ""%%%ss"", prefix); + snprintf (buf, buflen, fmt, + get_sort_str (tmp, sizeof (tmp), Threads, ThreadMethods)); + } + else if ((Threads & SORT_MASK) == SORT_NOTHREADS) optional = 0; break; Index: thread.c =================================================================== RCS file: /home/roessler/cvs/mutt/thread.c,v retrieving revision 3.8 diff -u -d -r3.8 thread.c --- thread.c 10 Dec 2003 00:48:57 -0000 3.8 +++ thread.c 2 May 2004 18:30:21 -0000 @@ -24,6 +24,8 @@ #define VISIBLE(hdr, ctx) (hdr->virtual >= 0 || (hdr->collapsed && (!ctx->pattern || hdr->limited))) +static sort_t *SortFunc; + /* determine whether a is a descendant of b */ static int is_descendant (THREAD *a, THREAD *b) { @@ -80,7 +82,7 @@ static void linearize_tree (CONTEXT *ctx) { THREAD *tree = ctx->tree; - HEADER **array = ctx->hdrs + (Sort & SORT_REVERSE ? ctx->msgcount - 1 : 0); + HEADER **array = ctx->hdrs + (Threads & SORT_REVERSE ? ctx->msgcount - 1 : 0); while (tree) { @@ -88,7 +90,7 @@ tree = tree->child; *array = tree->message; - array += Sort & SORT_REVERSE ? -1 : 1; + array += Threads & SORT_REVERSE ? -1 : 1; if (tree->child) tree = tree->child; @@ -146,6 +148,11 @@ if (tmp->subtree_visible) { tmp->deep = 1; + /* setting subtree_visibile to 2 means that we've seen it at least + * twice, which means that it has at least two children which are + * the roots of visible subtrees (or it means that it itself is + * visible and has at least one such child, but for our purposes + * that's OK.) */ tmp->subtree_visible = 2; break; } @@ -226,8 +233,8 @@ void mutt_draw_tree (CONTEXT *ctx) { char *pfx = NULL, *mypfx = NULL, *arrow = NULL, *myarrow = NULL, *new_tree; - char corner = (Sort & SORT_REVERSE) ? M_TREE_ULCORNER : M_TREE_LLCORNER; - char vtee = (Sort & SORT_REVERSE) ? M_TREE_BTEE : M_TREE_TTEE; + char corner = (Threads & SORT_REVERSE) ? M_TREE_ULCORNER : M_TREE_LLCORNER; + char vtee = (Threads & SORT_REVERSE) ? M_TREE_BTEE : M_TREE_TTEE; int depth = 0, start_depth = 0, max_depth = 0, width = option (OPTNARROWTREE) ? 1 : 2; THREAD *nextdisp = NULL, *pseudo = NULL, *parent = NULL, *tree = ctx->tree; @@ -556,38 +563,24 @@ hash_destroy (&ctx->thread_hash, *free); } -int compare_threads (const void *a, const void *b) +static int compare_threads (const void *a, const void *b) { - static sort_t *sort_func = NULL; - - if (a || b) - return ((*sort_func) (&(*((THREAD **) a))->sort_key, - &(*((THREAD **) b))->sort_key)); - /* a hack to let us reset sort_func even though we can't - * have extra arguments because of qsort - */ - else - { - sort_func = NULL; - sort_func = mutt_get_sort_func (Sort); - return (sort_func ? 1 : 0); - } + return ((*SortFunc) ((void *) &(*((THREAD **) a))->sort_key, + (void *) &(*((THREAD **) b))->sort_key)); } THREAD *mutt_sort_subthreads (THREAD *thread, int init) { - THREAD **array, *sort_key, *top, *tmp; + THREAD **array, *sort_thread, *top; HEADER *oldsort_key; - int i, array_size, sort_top = 0; + int i, n, array_size, sort_top = 0; - /* we put things into the array backwards to save some cycles, - * but we want to have to move less stuff around if we're - * resorting, so we sort backwards and then put them back - * in reverse order so they're forwards - */ - Sort ^= SORT_REVERSE; - if (!compare_threads (NULL, NULL)) + SortFunc = mutt_get_sort_func (Sort); + if (!SortFunc) return (thread); + AuxSort = mutt_get_sort_func (SortAux); + if (AuxSort == SortFunc) + AuxSort = NULL; top = thread; @@ -627,7 +620,7 @@ if (thread->prev && (thread->parent ? thread->parent->sort_children : sort_top)) { /* put them into the array */ - for (i = 0; thread; i++, thread = thread->prev) + for (i = 0, thread = (thread->parent ? thread->parent->child : top); thread; i++, thread = thread->next) { if (i >= array_size) safe_realloc (&array, (array_size *= 2) * sizeof (THREAD *)); @@ -635,34 +628,38 @@ array[i] = thread; } - qsort ((void *) array, i, sizeof (THREAD *), *compare_threads); + n = i; + qsort ((void *) array, n, sizeof (THREAD *), *compare_threads); /* attach them back together. make thread the last sibling. */ - thread = array[0]; + thread = array[n - 1]; thread->next = NULL; - array[i - 1]->prev = NULL; + array[0]->prev = NULL; if (thread->parent) - thread->parent->child = array[i - 1]; + thread->parent->child = array[0]; else - top = array[i - 1]; + top = array[0]; - while (--i) + for (i = 1; i < n; i++) { - array[i - 1]->prev = array[i]; - array[i]->next = array[i - 1]; + array[i - 1]->next = array[i]; + array[i]->prev = array[i - 1]; } } if (thread->parent) { - tmp = thread; + /* keep track of the last sibling */ + sort_thread = thread; thread = thread->parent; if (!thread->sort_key || thread->sort_children) { - /* make sort_key the first or last sibling, as appropriate */ - sort_key = (!(Sort & SORT_LAST) ^ !(Sort & SORT_REVERSE)) ? thread->child : tmp; + /* make sort_thread the first sibling, if appropriate */ + if ((Threads & SORT_MASK) != SORT_LASTTHREADS + && (Threads & SORT_MASK) != SORT_LTHREADS) + sort_thread = thread->child; /* we just sorted its children */ thread->sort_children = 0; @@ -670,17 +667,12 @@ oldsort_key = thread->sort_key; thread->sort_key = thread->message; - if (Sort & SORT_LAST) - { - if (!thread->sort_key - || ((((Sort & SORT_REVERSE) ? 1 : -1) - * compare_threads ((void *) &thread, - (void *) &sort_key)) - > 0)) - thread->sort_key = sort_key->sort_key; - } - else if (!thread->sort_key) - thread->sort_key = sort_key->sort_key; + if (!thread->sort_key + || ((Threads & SORT_MASK) == SORT_LASTTHREADS + && compare_threads ((void *) &thread, (void *) &sort_thread) < 0) + || (((Threads & SORT_MASK) == SORT_FIRSTTHREADS + && compare_threads ((void *) &thread, (void *) &sort_thread) > 0))) + thread->sort_key = sort_thread->sort_key; /* if its sort_key has changed, we need to resort it and siblings */ if (oldsort_key != thread->sort_key) @@ -694,7 +686,6 @@ } else { - Sort ^= SORT_REVERSE; FREE (&array); return (top); } @@ -739,17 +730,10 @@ void mutt_sort_threads (CONTEXT *ctx, int init) { HEADER *cur; - int i, oldsort, using_refs = 0; + int i, using_refs = 0; THREAD *thread, *new, *tmp, top; LIST *ref = NULL; - /* set Sort to the secondary method to support the set sort_aux=reverse-* - * settings. The sorting functions just look at the value of - * SORT_REVERSE - */ - oldsort = Sort; - Sort = SortAux; - if (!ctx->thread_hash) init = 1; @@ -951,9 +935,6 @@ { ctx->tree = mutt_sort_subthreads (ctx->tree, init); - /* restore the oldsort order. */ - Sort = oldsort; - /* Put the list into an array. */ linearize_tree (ctx); @@ -1009,7 +990,7 @@ THREAD *cur; HEADER *tmp; - if ((Sort & SORT_MASK) != SORT_THREADS) + if ((Threads & SORT_MASK) == SORT_NOTHREADS) { mutt_error _(""Threading is not enabled.""); return (hdr->virtual); @@ -1064,7 +1045,7 @@ { THREAD *thread; - if ((Sort & SORT_MASK) != SORT_THREADS) + if ((Threads & SORT_MASK) == SORT_NOTHREADS) { mutt_error _(""Threading is not enabled.""); return (hdr->virtual); @@ -1119,7 +1100,7 @@ int min_unread_msgno = INT_MAX, min_unread = cur->virtual; #define CHECK_LIMIT (!ctx->pattern || cur->limited) - if ((Sort & SORT_MASK) != SORT_THREADS && !(flag & M_THREAD_GET_HIDDEN)) + if ((Threads & SORT_MASK) == SORT_NOTHREADS && !(flag & M_THREAD_GET_HIDDEN)) { mutt_error (_(""Threading is not enabled."")); return (cur->virtual); @@ -1274,7 +1255,7 @@ THREAD *threads[2]; int i, rc; - if ((Sort & SORT_MASK) != SORT_THREADS || !hdr->thread) + if ((Threads & SORT_MASK) == SORT_NOTHREADS || !hdr->thread) return (1); threads[0] = hdr->thread; @@ -1289,7 +1270,7 @@ threads[i] = threads[i]->child; } - if (Sort & SORT_REVERSE) + if (Threads & SORT_REVERSE) rc = threads[0]->message->msgno - (threads[1] ? threads[1]->message->msgno : -1); else rc = (threads[1] ? threads[1]->message->msgno : ctx->msgcount) - threads[0]->message->msgno; --- cut here --- -- System Information System Version: Linux puri.chappati.org 2.4.22-1.2188.nptl #1 Wed Apr 21 20:36:05 EDT 2004 i686 i686 i386 GNU/Linux RPM Packager: Manoj Kasichainula RedHat Release: Fedora Core release 1 (Yarrow) -- 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-redhat-linux/3.3.2/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.3.2 20031022 (Red Hat Linux 3.3.2-1) - CFLAGS -Wall -pedantic -O2 -march=pentium3 -msse2 -mfpmath=sse -- Mutt Version Information Mutt 1.5.6i (2004-02-01) Copyright (C) 1996-2002 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.22-1.2188.nptl (i686) [using ncurses 5.3] 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 +USE_SASL2 +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -BUFFY_SIZE -EXACT_ADDRESS +SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" Manoj Kasichainula 2025 [wishlist] Let fcc, copy-to-folder and save-to-folder save to multiple folder at once mutt wishlist enhancement mutt-dev new 2005-08-04T13:38:41-07:00 1969-12-31T16:00:00-08:00 "{{{ It would be nice to be able to save mails to multiple folders at the same time, either via fcc (maybe even automagical with multiple recepients) or just for convenience when moving or copying messages around. For syntax I could imagine that commata would be a good folder delimiter: To: fred@example.com, bob@example.com Fcc: =fred, =bob Maybe the blank after the comma is not very useful in the input line as blank works like tab there... >How-To-Repeat: >Fix: Wishlist. Sorry, no patch }}}" mutt@… 2076 wish: complete tilde patterns mutt 1.5.11 enhancement mutt-dev new 2005-09-19T07:48:01-07:00 2005-10-08T23:08:42-07:00 "{{{ Just a wish. I often forget which pattern is for enctypted messages, and which is for signed. (Answers: ~G and ~g) So, I just want function to complete patterns. i.e., Press T, ~, and to tag some messages. >How-To-Repeat: My situation: Searching for an encrypted message, I push ""l"" key, and...., oh well, what pattern should I use? ""~g"" or ""~G""? And press Ctrl-G and ""!less /usr/share/doc/mutt/manual.txt"" to search for ~G..., oh wait, what message was I searching for? >Fix: Here is my patch. }}}" ttakah@… 2077 wish: No way to see the status of commands (e.g. subscribe) mutt 1.5.11 enhancement mutt-dev new 2005-09-19T08:09:50-07:00 2005-10-08T23:17:48-07:00 "{{{ You can use *-hook, alternates, my_hdr, auto_view, ignore, subscribe and other commands on an running mutt. But you cannot see the status of the commands. Sometimes you may want to check which hooks you are using, but you cannot. >How-To-Repeat: >Fix: Here is my implementation. Usage: bind index _ status-commands I can add this ability to ""mutt -D"" if someone want. }}}" ttakah@… 2098 Integration of RSS agregation in mutt might be interesting mutt mutt-1.4 enhancement mutt-dev new 2005-10-02T16:09:32-07:00 2005-10-03T12:35:01-07:00 "{{{ I hope the class, the priority and all this is right, as it is a suggestion for a new feature. I recently tried the new RSS agregator in Thunderbird, I found it amazing. As some RSS feeds might be seen as mailing-list (while looking at the content), it's quite interesting to use a mailer to read those RSS feeds. I find Mutt so complete and so nice that I did not know anything missing, and two day ago, I discovered that. It's the only thing I find to be missing in mutt. If you don't know ThunderBird RSS agregator, it looks like that: http://www.insa-rennes.fr/~nlescoua/thunderbird-rss.png >How-To-Repeat: >Fix: }}}" nlsn@… 2122 Should encrypt messages to the Sender: key as well as to recipients crypto enhancement mutt-dev new 2005-10-28T11:13:00-07:00 2009-06-30T07:55:45-07:00 "{{{ Currently, GPG only encrypts messages to the To:, CC: or Bcc: but *not* to the From: of an email message. This means that any user that sends an encrypted mail to any other user will not be able to read the e-mail in the future in a default configuration (see workarounds for possible ways to prevent this) I don't see any reason for outgoing mail to not be encrypted to the sender's key so he is able to read it in the future and other software (i.e. PGP Desktop) does this by default. I suggest the attached (tested) patch be introduced to mutt to introduce this new behavior. >How-To-Repeat: Send a PGP/GPG encrypted mail to someone (without having 'encrypt-to' with your own GPG key in the gnupg.options file) and try to open the mail saved on the folder >Fix: The current work around to this issue is either adding 'encrypt-to YourKeyID' in gnupg.options or e-mailing to yourself (in Bcc: or To:) so that either a) gnupg encrypts to you by default or b) mutt tells gnupg to encrypt to you (adds you to the keylist) }}}" jfs@… 2333 wish: display multiple ?variables at once mutt 1.5.12 enhancement mutt-dev new 2006-07-06T17:05:28-07:00 2007-04-07T07:21:25-07:00 "{{{ Hi ALL! I'd wish Mutt ""set"" command to be able to display the value of several variables at once. Like example: | :set ?realname ?from | realname=""John Doe"" from=""johnny@example.com"" Usefull as poor-man's echo, as last statement in an ""identity"" macro, and such. The following should also be possible: | :set locale=old-value | [...] | :set ?locale locale=new-value ?locale | locale=""old-value"" locale=""new-value"" Usefull for tracking changes. Bye! Alain. >How-To-Repeat: >Fix: }}}" Alain Bench 2460 mutt does not write the maildir P flag maildir/mh enhancement mutt-dev new 2006-08-30T17:16:51-07:00 2009-06-30T07:57:09-07:00 "Maildir has the P flag for messages that are handed off to other users: Flag ""P"" (passed): the user has resent/forwarded/bounced this message to someone else. Mutt doesn't make use of this flag but it should at least write it, so that other clients that might use the flag have the info available. >How-To-Repeat: resent/forward/bounce a message. sync-mailbox. check the maildir flags for that message." Michael.Tatge@… 2595 mutt doesn't accept utf8 configuration files starting with EF BB BF charset 1.5.11 (2005-09-15) enhancement mutt-dev new 2006-12-06T00:58:26-08:00 2009-06-30T07:58:20-07:00 "{{{ since vers approx 1.4 utf8 coded configuration files are allowed in order to use utf8 coded strings. This works fine. But today's editors add the sequence EF BB BF at the beginning of the file which normally should be ignored. Mutt exits instead with a fatal error message. >How-To-Repeat: >Fix: }}}" getreu@… 2664 Mutt should honnor Mail-Copies-To header mutt enhancement mutt-dev new 2007-01-05T04:06:18-08:00 2007-01-05T08:35:39-08:00 "{{{ In mailing-lists, some users send their mail with: Mail-Copies-To: never Though it is not standard (but neither is Mail-Followup-To, AFAIK) and it is primarily designed for Usenet (but mailing-lists are very similar), Mutt should support this header, defined in . >How-To-Repeat: >Fix: Unknown }}}" vincent@… 2723 implement 'unbind' command mutt 1.5.16 enhancement mutt-dev new 2007-01-29T12:34:55-08:00 2007-08-19T08:35:03-07:00 "{{{ Hello. This is a request for enhancement submitted by an Ubuntu user. You can find the original bug report at https://bugs.launchpad.net/ubuntu/+source/mutt/+bug/16750/ ""To disable a keystroke in mutt, one uses bind [keys] [mode] noop A more natural syntax would be unbind [keys] [mode]"" There appears to be a patch that does this at http://home.uchicago.edu/~dgc/mutt/#unbind Thanks. >How-To-Repeat: >Fix: Unknown }}}" pandisv@… 2771 wish: add resent-headers on user's choise (patch) mutt 1.[45].* enhancement mutt-dev new 2007-02-16T10:38:15-08:00 2007-04-12T08:33:08-07:00 "It will be nice if mutt will conditionally (defined by new quadoption) append Resent-* headers to message which remailed. >Fix: suggested patch attached " bsd@… 2809 wish: collapse sub-thread mutt enhancement mutt-dev new 2007-03-01T03:16:26-08:00 1969-12-31T16:00:00-08:00 "{{{ There are several sub-thread function. , , and so on. But what I'm missing is this would be really useful particularly with ""monster threads"" that fill a few pages. >How-To-Repeat: >Fix: Unknown }}}" Michael.Tatge@… 2811 Bug#413014: mutt: Handling of e-mails with multiple Message-IDs mutt enhancement mutt-dev new 2007-03-01T11:35:02-08:00 2007-04-02T18:23:42-07:00 "{{{ Hi, the following was submitted as Debian bug #413014: ----- Forwarded message from Mark Brown ----- Date: Thu, 01 Mar 2007 18:48:20 +0000 From: Mark Brown Reply-To: Mark Brown , 413014@bugs.debian.org To: Debian Bug Tracking System Subject: Bug#413014: mutt: Handling of e-mails with multiple Message-IDs Package: mutt Version: 1.5.13-1.1 Severity: minor Some broken mail processing software (I'm thinking particularly of crm114 here, though other things could do the same) when processing e-mail that contains a Message-ID header so that it also contains a Message-Id header. mutt, presumably in order to improve interoperability, will accept either spelling of the header name and appears to accept the last one. Unfortunately in the case of crm114 what it's doing is trying to add a comment to the Message-ID; what it actually ends up doing is creating a Message-Id field consisting only of a comment. This means that mutt winds up thinking there is no Message-ID at all, breaking threading. It would help matters if mutt were to ignore empty Message-I[dD] headers without assuming they were the only instance of that heaeder. Obviously, the problematic messages broken and the software generating them needs to be fixed: this is just a suggestion for an interoperability enhancement. ----- End forwarded message ----- Christoph -- cb@df7cb.de | http://www.df7cb.de/ >Fix: Unknown }}}" Christoph Berg 2171 previous-thread doesn't jumps to first message if parent not available mutt 1.5.19 defect mutt-dev new 2006-01-29T14:18:52-08:00 2010-08-05T21:37:15-07:00 "{{{ 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 . 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 }}}" Mike.Dornberger@… 2521 "Reply to mail with subject starting with ""t"" removes the ""t""" mutt 1.5.20 defect mutt-dev new 2006-10-10T07:25:15-07:00 2010-02-20T19:21:11-08:00 "{{{ The default reply_regexp is ""^(re([\[0-9\]+])*|aw):[ \t]*"" but at least the regexp libraries I use dont interpret \t as TAB within []'s. >How-To-Repeat: >Fix: set reply_regexp = '^(re|sv|vs):[[:space:]]*' or something like that... }}}" Tom Danielsen (tom@… 3171 mutt: Incorrect attribution line when replying to mail with multiple From addresses mutt 1.5.19 defect mutt-dev new 2009-01-26T15:11:14-08:00 2009-01-26T15:11:14-08:00 "Forwarding from http://bugs.debian.org/472397 --- When replying to a mail with multiple From addresses (such as this mail), mutt generates an attribution line which only mentions the first name listed in From. It should attribute all the authors of the quoted mail. Ideally, it would join two author names with ""and"", and join three or more author names with commas and add an ""and"" before the last. However, the exact form of the attribution doesn't matter as much; it just needs to attribute all authors of the quoted mail. " antonio@… 3324 mutt: smime_keys fails if tmpdir is set mutt 1.5.20 defect mutt-dev new 2009-09-02T17:06:10-07:00 2009-09-02T17:06:10-07:00 "Forwarding from http://bugs.debian.org/542817 {{{ Hi! In my .muttrc I have set tmpdir with the following entry away from /tmp (causes mail loss if suspend fails while a message is in the pipe). This setting seems to confise smime_keys. <===== set tmpdir=""$HOME/Mail/tmp"" ====> <===== LANG=""C"" smime_keys add_p12 christoph.p12 NOTE: This will ask you for two passphrases: 1. The passphrase you used for exporting 2. The passphrase you wish to secure your private key with. Enter Import Password: MAC verified OK Enter PEM pass phrase: Verifying - Enter PEM pass phrase: Couldn't open =tmp/smime/cert_tmp.0: No such file or directory at /usr/bin/smime_keys line 518. ====> }}}" antonio@… 3329 imap_check_subscribed reports new mail spuriously mutt 1.5.20 defect mutt-dev new 2009-09-06T13:05:05-07:00 2009-09-06T13:05:05-07:00 "Forwarding from http://bugs.debian.org/539335 {{{ I tried setting imap_check_subscribed to see how well it would work. It worked fairly well, but it seems to spuriously report new mail in =Sent (my $record folder) and =Archive (where I save all my read mail). Switching to one of those folders and hitting tab indicates that I have no unread mail in those folders, as expected. }}}" antonio@… 3332 Failures to send result in duplicate messages in record folder mutt 1.5.21 defect mutt-dev new 2009-09-09T01:37:47-07:00 2011-05-24T10:29:35-07:00 "Forwarding from http://bugs.debian.org/539232 {{{ I set ""record"" to save sent messages in my Sent folder. If I try to send a message, and it fails to send (most commonly, because I typo my password or hit enter before providing a password), I will still end up with a copy of the message in my Sent folder. When I then send the message correctly, I end up with another copy. This seems wrong, though I don't know the best way to solve it. }}}" antonio@… 3391 g key feedback the same as r mutt 1.5.20 defect mutt-dev new 2010-03-10T21:24:15-08:00 2010-04-02T15:37:41-07:00 "When we reply with r, we are shown the To: bob@... line and hit RET. When we hit g to group reply, we are shown the exact same things as ""r"". We wonder ""am I just sending to the To: and not the Cc:'s?"". It is not until we are thru with editing and about to send that we see indeed the Cc:s have not been forgot about. Therefore with g, you should say To: ... ""and others"", or ""..."" at least. Or say To: bob and 3 others. Or list them all, if it fits on one line, else ""..."" You get the idea. Thanks." jidanni 3486 """Attach:"" pseudo-header cannot handle filenames with newline" mutt 1.5.21 defect mutt-dev new 2011-01-01T11:34:49-08:00 2011-01-01T11:34:49-08:00 "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" antonio@… 3487 Display problems for mbox-files > 2GiB mutt 1.5.21 defect mutt-dev new 2011-01-01T11:45:54-08:00 2013-04-22T01:32:34-07:00 "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. }}}" antonio@… 3488 mail-key function is broken when crypt_use_gpgme is set mutt 1.5.21 defect mutt-dev new 2011-01-01T11:48:56-08:00 2011-01-01T11:48:56-08:00 "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. }}}" antonio@… 3490 IMAP: ignores \Recent flag but rolls its own replacement IMAP 1.5.21 defect brendan new 2011-01-01T11:57:20-08:00 2011-06-25T19:39:43-07:00 "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. }}}" antonio@… 3491 hangs when IP address changes mutt 1.5.21 defect mutt-dev new 2011-01-01T12:01:51-08:00 2012-04-29T12:10:11-07:00 "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). }}} " antonio@… 3492 mutt uses ncurses even in non-interactive mode mutt 1.5.21 defect mutt-dev new 2011-01-01T12:05:59-08:00 2011-01-01T12:05:59-08:00 "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 }}}" antonio@… 3495 q and x in help menu should only appear once mutt 1.5.21 defect mutt-dev new 2011-01-03T04:47:58-08:00 2011-01-03T07:02:58-08:00 "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: x abort 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... }}}" antonio@… 3643 Man pages for pgpewrap and pgpring and other doc fixes doc defect mutt-dev new 2013-05-20T08:15:47-07:00 2013-05-20T08:15:47-07:00 Hi, this is only unimportant patch, that adds some missing options in doc and adds man pages for binaries pgpewrap and pgpring. hhorak 408 [PATCH] more flag data in collapsed thread view mutt 1.3.13i enhancement mutt-dev new 2001-01-01T19:07:10-08:00 2010-09-15T07:08:56-07:00 "{{{ Package: mutt Version: 1.3.13i Severity: wishlist -- Please type your report below this line It would be nice if hidden messages could have their flags propagated through to the thread leader message's flag display. Eg. if one invisible message in a thread has the ! flag set, this should be indicated in the flags displayed for the visible message. My implementation displays one set of characters if *all* messages have a particular attribute and another set if only one or some of the messages have a particular attribute. See the documentation patch for more details. I have modified and extended the _mutt_traverse_thread function to count the occurrence of attributes in a thread. The code below works for me, but needs cleaning up. I have intentionally left it messy so that it is as near as possible to the existing code. (ie. I haven't rewritten the whole lot in a neater way.) Index: mutt.h =================================================================== RCS file: /home/roessler/cvs/mutt/mutt.h,v retrieving revision 2.88 diff -u -r2.88 mutt.h --- mutt.h 2000/12/31 11:24:19 2.88 +++ mutt.h 2001/01/01 10:01:50 @@ -158,6 +158,9 @@ #define M_THREAD_GET_HIDDEN (1<<2) #define M_THREAD_UNREAD (1<<3) #define M_THREAD_NEXT_UNREAD (1<<4) +#define M_THREAD_GET_NEW (1<<5) +#define M_THREAD_GET_OLD (1<<6) +#define M_THREAD_GET_FLAGGED (1<<7) enum { Index: hdrline.c =================================================================== RCS file: /home/roessler/cvs/mutt/hdrline.c,v retrieving revision 2.23 diff -u -r2.23 hdrline.c --- hdrline.c 2000/10/17 15:10:51 2.23 +++ hdrline.c 2001/01/01 10:01:51 @@ -253,12 +268,18 @@ int optional = (flags & M_FORMAT_OPTIONAL); int threads = ((Sort & SORT_MASK) == SORT_THREADS); int is_index = (flags & M_FORMAT_INDEX); -#define THREAD_NEW (threads && hdr->collapsed && hdr->num_hidden > 1 && mutt_thread_contains_unread (ctx, hdr) == 1) -#define THREAD_OLD (threads && hdr->collapsed && hdr->num_hidden > 1 && mutt_thread_contains_unread (ctx, hdr) == 2) + int selforchild; + int temp; +/*#define THREAD_NEW (threads && hdr->collapsed && hdr->num_hidden > 1 && mutt_thread_contains_unread (ctx, hdr) == 1)*/ +/*#define THREAD_OLD (threads && hdr->collapsed && hdr->num_hidden > 1 && mutt_thread_contains_unread (ctx, hdr) == 2)*/ +#define THREAD_NEW (threads && hdr->collapsed && hdr->num_hidden > 1 && ( temp = _mutt_traverse_thread (ctx, hdr, M_THREAD_GET_NEW) ) ) +#define THREAD_FLAGGED (threads && hdr->collapsed && hdr->num_hidden > 1 && ( temp = _mutt_traverse_thread (ctx, hdr, M_THREAD_GET_FLAGGED) ) ) +#define THREAD_OLD (threads && hdr->collapsed && hdr->num_hidden > 1 && ( temp = _mutt_traverse_thread (ctx, hdr, M_THREAD_GET_OLD) ) ) size_t len; hdr = hfi->hdr; ctx = hfi->ctx; + selforchild = mutt_get_hidden(ctx, hdr) + 1/*self*/; dest[0] = 0; switch (op) @@ -630,12 +651,12 @@ #endif snprintf (buf2, sizeof (buf2), - ""%c%c%c"", (THREAD_NEW ? 'n' : (THREAD_OLD ? 'o' : + ""%c%c%c"", (THREAD_NEW ? (((temp+!hdr->read)==selforchild) ? 'N' : 'n') : (THREAD_OLD ? (((temp+hdr->old)==selforchild) ? 'O' : 'o' ) : ((hdr->read && (ctx && ctx->msgnotreadyet != hdr->msgno)) ? (hdr->replied ? 'r' : ' ') : (hdr->old ? 'O' : 'N')))), hdr->deleted ? 'D' : (hdr->attach_del ? 'd' : ch), hdr->tagged ? '*' : - (hdr->flagged ? '!' : + (hdr->flagged ? '!' : THREAD_FLAGGED ? '.' : (Tochars && ((i = mutt_user_is_recipient (hdr)) < mutt_strlen (Tochars)) ? Tochars[i] : ' '))); mutt_format_s (dest, destlen, prefix, buf2); break; Index: init.h =================================================================== RCS file: /home/roessler/cvs/mutt/init.h,v retrieving revision 2.112 diff -u -r2.112 init.h --- init.h 2000/12/21 09:19:41 2.112 +++ init.h 2001/01/01 10:01:53 @@ -808,7 +815,8 @@ ** .dt %Y .dd `x-label' field, if present, and (1) not at part of a thread tree, ** (2) at the top of a thread, or (3) `x-label' is different from ** preceding message's `x-label'. - ** .dt %Z .dd message status flags + ** .dt %Z .dd message status flags. Three flag positions are shown. \fIFor unthreaded + ** entries:\fP the first character indicates whether a message is replied to ('r'), new ('N'), old ('O'), or none of these (' '). The second character indicates if a message is to be deleted ('D') or else PGP flags. The third character indicates is a message is tagged ('*'), flagged ('!'), or else contains one of $$to_chars. \fIFor threaded entires:\fP the first character indicates whether all messages are new ('N') or only some ('n') or whether all entries are old ('O') or only some ('o'). The second character indicates whether the displayed message (ie. the thread leader) is to be deleted ('D') or else PGP flags. The third character indicates whether the displayed message is flagged ('!') or if some hidden message is flagged ('.') or else one of $$to_chars. ** .dt %{fmt} .dd the date and time of the message is converted to sender's ** time zone, and ``fmt'' is expanded by the library function ** ``strftime''; a leading bang disables locales Index: thread.c =================================================================== RCS file: /home/roessler/cvs/mutt/thread.c,v retrieving revision 2.13 diff -u -r2.13 thread.c --- thread.c 2000/05/10 17:16:43 2.13 +++ thread.c 2001/01/01 10:02:08 @@ -746,7 +746,7 @@ { HEADER *roothdr = NULL, *top; int final, reverse = (Sort & SORT_REVERSE), minmsgno; - int num_hidden = 0, new = 0, old = 0; + int num_hidden = 0, new = 0, old = 0, ping = 0; /* ping is the number of flagged messages in the thread */ int min_unread_msgno = INT_MAX, min_unread = cur->virtual; #define CHECK_LIMIT (!ctx->pattern || cur->limited) @@ -766,15 +766,19 @@ if (!cur->read && CHECK_LIMIT) { if (cur->old) - old = 2; + old ++; else - new = 1; + new ++; if (cur->msgno < min_unread_msgno) { min_unread = cur->virtual; min_unread_msgno = cur->msgno; } } + if (cur->flagged && CHECK_LIMIT /*what is CHECK_LIMIT??*/) + { + ping ++; + } if (cur->virtual == -1 && CHECK_LIMIT) num_hidden++; @@ -836,12 +840,16 @@ } + if (cur->flagged && CHECK_LIMIT /*what is CHECK_LIMIT??*/) + { + ping ++; + } if (!cur->read && CHECK_LIMIT) { if (cur->old) - old = 2; + old ++; else - new = 1; + new ++; if (cur->msgno < min_unread_msgno) { min_unread = cur->virtual; @@ -879,6 +887,13 @@ return (final); else if (flag & M_THREAD_UNREAD) return ((old && new) ? new : (old ? old : new)); + else if (flag & M_THREAD_GET_FLAGGED) + return ping; + else if (flag & M_THREAD_GET_NEW) + return new; + else if (flag & M_THREAD_GET_OLD) + return old; + /*return ((old && new) ? new : (old ? old : new));*/ else if (flag & M_THREAD_GET_HIDDEN) return (num_hidden+1); else if (flag & M_THREAD_NEXT_UNREAD) -- Mutt Version Information Mutt 1.3.13i (2000-12-31) Copyright (C) 1996-2000 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: SunOS 5.8 [using ncurses 5.0] 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/local/bin/ispell"" SENDMAIL=""/usr/lib/sendmail"" MAILPATH=""/var/mail"" SHAREDIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" James Devenish 627 wanted: way to force interactive mode mutt enhancement mutt-dev new 2001-05-29T21:19:53-07:00 2010-09-15T07:09:43-07:00 "{{{ Package: mutt Version: 1.3.18-1 Severity: wishlist [NOTE: this bug report has been submitted to the debian BTS as Bug#99104. Please Cc all your replies to 99104@bugs.debian.org.] From: Joey Hess Subject: wanted: way to force interactive mode Date: Mon, 28 May 2001 21:48:19 -0400 With the -e switch, mutt can be used for a lot of useful, automated mailbox munging tasks. Unfortunatly, none of these tasks work if mutt's standard input is not connected to a tty. If stdin is anything else, mutt enters noninteractive mail sending mode. This means that none of the handy things I have recipies to make mutt do with mutt -e commands work in cron jobs. I would like a new flag to be added, that forces mutt to enter interactive mode even if there is no controlling terminal. -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux silk 2.4.4 #2 Fri May 11 22:25:05 EDT 2001 i686 Locale: LANG=C, LC_CTYPE=C Versions of packages mutt depends on: ii exim 3.22-4 Exim Mailer ii exim [mail-transport-agen 3.22-4 Exim Mailer ii libc6 2.2.3-3 GNU C Library: Shared libraries an ii libncurses5 5.2.20010318-1 Shared libraries for terminal hand ii libsasl7 1.5.24-6 Authentication abstraction library >How-To-Repeat: >Fix: }}}" Marco d'Itri 973 encrypt mail with more keys than recipient list (think mailinglist) crypto enhancement mutt-dev new 2002-01-13T10:05:15-08:00 2010-02-11T12:30:45-08:00 "{{{ Package: mutt Version: 1.3.25-2 [NOTE: this bug report has been submitted to the debian BTS as Bug#128945. Please Cc all your replies to 128945@bugs.debian.org.] From: Martin Schulze Subject: Sending mail encrypted with additional keys Date: Sat, 12 Jan 2002 23:34:47 +0100 Package: mutt Version: 1.3.25-2 Severity: wishlist I'd like to send a mail to a list and encrypt it with five keys. One of these is my own key, so that's already handled. It would be nice if mutt would support this by specifying 'additional keys' in the PGP menu or something. As a proof, here's the reason behind this. I'm working on security for Debian and I have received a confidential mail about a root hole that could be easily exploited. Rather than sending unencrypted mail I'd like to inform the maintainer of the affected package and copy that mail to our internal security list, hence need to encrypt it for all members. Currently there only seem to be dirty methods making this possible: 1. Temporarily add more ``encrypt-to'' statements to .gnupg/options 2. Modify ``pgp_encrypt_only_command'' and ``pgp_encrypt_only_command'' temporarily from within Mutt. It is already long... is there a way to *edit* it rather than setting it to a new value? 3. Using a specially crafted .muttrc.dsp for the security team. 4. Bcc the mail to four unknown addresses and select the key of another member of the Security Team for each of them. Who cares about bounces... However, I'd rather have a way to select additional GnuPG keys in Mutt in order to encrypt the message with them as well. Regards, Joey -- It's time to close the windows. Please always Cc to me when replying to me on the lists. >How-To-Repeat: >Fix: }}}" Marco d'Itri 1484 mutt: patch for reminder if attachment mentioned in body is missing mutt enhancement mutt-dev new 2003-02-24T22:53:33-08:00 2011-05-31T21:26:02-07:00 "{{{ Package: mutt Version: 1.5.3-3 Severity: wishlist [NOTE: this bug report has been submitted to the debian BTS as Bug#182069. Please Cc all your replies to 182069@bugs.debian.org .] From: Bernard Blackham Subject: mutt: patch for idiot-proofing with attachments Date: Sun, 23 Feb 2003 03:10:15 +0800 This patch checks if the body of an email contains a magic configurable keyword (default is ""attach""), and if so, checks if there really are any attachments, and if not, alerts the user. This is to stop the abundance of ""Please find attached"" ... ""Oops, here tis"" emails. The default setting (abort_noattach) is ask/yes. Setting this to ""no"", would turn off this sanity check, as if the patch were never there (this may be preferable), which may be more preferable - so to use it you need to explictly enable it. Patch attached. (No, really! It is! ;) It drops cleanly into debian/patches in 1.5.3-3. diff -ur mutt-1.5.3.orig/globals.h mutt-1.5.3/globals.h --- mutt-1.5.3.orig/globals.h 2002-09-10 04:05:44.000000000 +0800 +++ mutt-1.5.3/globals.h 2003-02-23 02:53:21.000000000 +0800 @@ -32,6 +32,7 @@ WHERE char *AliasFile; WHERE char *AliasFmt; +WHERE char *AttachKeyword; WHERE char *AttachSep; WHERE char *Attribution; WHERE char *AttachFormat; diff -ur mutt-1.5.3.orig/init.h mutt-1.5.3/init.h --- mutt-1.5.3.orig/init.h 2002-12-10 02:09:21.000000000 +0800 +++ mutt-1.5.3/init.h 2003-02-23 02:53:21.000000000 +0800 @@ -107,6 +107,14 @@ struct option_t MuttVars[] = { /*++*/ + { ""abort_noattach"", DT_QUAD, R_NONE, OPT_ATTACH, M_ASKYES }, + /* + ** .pp + ** If set to \fIyes\fP, when composing messages containing the word + ** specified by $attach_keyword (default is ""attach"") and no attachments + ** are given, composition will be aborted. If set to \fIno\fP, composing + ** messages as such will never be aborted. + */ { ""abort_nosubject"", DT_QUAD, R_NONE, OPT_SUBJECT, M_ASKYES }, /* ** .pp @@ -222,6 +230,13 @@ ** .dt %|X .dd pad to the end of the line with character ""X"" ** .de */ + { ""attach_keyword"", DT_STR, R_NONE, UL &AttachKeyword, UL ""attach"" }, + /* + ** .pp + ** If $abort_attach is not set to no, then the body of the message + ** will be scanned for this keyword, and if found, you will be prompted + ** if there are no attachments. This is case insensitive. + */ { ""attach_sep"", DT_STR, R_NONE, UL &AttachSep, UL ""\n"" }, /* ** .pp diff -ur mutt-1.5.3.orig/mutt.h mutt-1.5.3/mutt.h --- mutt-1.5.3.orig/mutt.h 2002-12-07 00:37:21.000000000 +0800 +++ mutt-1.5.3/mutt.h 2003-02-23 02:53:21.000000000 +0800 @@ -295,7 +295,8 @@ OPT_SUBJECT, OPT_MIMEFWDREST, OPT_FORWEDIT, - OPT_MAX + OPT_MAX, + OPT_ATTACH }; /* flags to ci_send_message() */ diff -ur mutt-1.5.3.orig/send.c mutt-1.5.3/send.c --- mutt-1.5.3.orig/send.c 2002-12-12 06:45:38.000000000 +0800 +++ mutt-1.5.3/send.c 2003-02-23 02:55:41.000000000 +0800 @@ -1027,6 +1027,34 @@ } int +mutt_search_attach_keyword(char* filename) +{ + /* searches for the magic keyword ""attach"" within a file */ + int found = 0; + char* inputline = malloc(1024); + char* lowerKeyword = malloc(strlen(AttachKeyword)+1); + FILE *attf = fopen(filename, ""r""); + int i; + for (i=0; i <= strlen(AttachKeyword); i++) { + lowerKeyword[i] = tolower(AttachKeyword[i]); + } + while (!feof(attf)) { + fgets(inputline, 1024, attf); + for (i=0; i < strlen(inputline); i++) { + inputline[i] = tolower(inputline[i]); + } + if (strstr(inputline, lowerKeyword)) { + found = 1; + break; + } + } + free(inputline); + free(lowerKeyword); + fclose(attf); + return found; +} + +int ci_send_message (int flags, /* send mode */ HEADER *msg, /* template to use for new message */ char *tempfile, /* file specified by -i or -H */ @@ -1452,6 +1480,21 @@ goto main_loop; } + if (mutt_search_attach_keyword(msg->content->filename) && + !msg->content->next && + query_quadoption(OPT_ATTACH, _(""No attachments, cancel sending?"")) != M_NO) + { + /* if the abort is automatic, print an error message */ + if (quadoption (OPT_ATTACH) == M_YES) { + char errorstr[512]; + if (snprintf(errorstr, 512, + ""Message contains magic keyword \""%s\"", but no attachments. Not sending."", AttachKeyword)==-1) + errorstr[511] = 0; // terminate if need be. our string shouldnt be this long. + mutt_error _(errorstr); + } + goto main_loop; + } + if (msg->content->next) msg->content = mutt_make_multipart (msg->content); >How-To-Repeat: >Fix: }}}" Marco d'Itri 1812 pgp-hook cannot be auto accepted mutt 1.3.28i enhancement mutt-dev new 2004-02-20T05:54:50-08:00 2012-12-30T19:49:06-08:00 "{{{ Package: mutt Version: 1.3.28-2.2 Severity: wishlist -- Please type your report below this line I send pgp encrypted mail to someone. Every time I try this, mutt shows me a dialog with only one entry, asking me to choose the key to use. I hoped to get rid of that dialog using the pgp-hook command in the config file. This didn't quite work, since I still have to press enter, this time to the question ""use this key?"" I checked the documentation and the source, and found that this question cannot be disabled. I wrote a patch to add it as a quadoption, with the default the same as it is now. I included it in the report (it is a patch against the source I got from apt-get source mutt in debian unstable.) I didn't quite understand what R_NONE does, so it may need to be a different value. I compiled the code with this patch (it gave quite a number of warnings by the way, not related to this patch, using gcc 3.3) and that resulted in a valid executable, and it seemed to behave reasonable at a little testing as well. However, with a nonexisting key in the hook, and the value set to ""yes"", it didn't ask me to enter a keyID at all, which surprised me. Perhaps some more testing is needed. The specifications below are not what I used to compile mutt, by the way, but they are what I use to run it normally (Debian stable) Thanks, Bas Wijnen diff -rup mutt-1.5.5.1/init.h mutt-shevek/init.h --- mutt-1.5.5.1/init.h 2003-11-05 10:41:32.000000000 +0100 +++ mutt-shevek/init.h 2004-02-19 19:56:02.000000000 +0100 @@ -117,6 +117,12 @@ struct option_t MuttVars[] = { ** check only happens after the \fIfirst\fP edit of the file). When set ** to \fIno\fP, composition will never be aborted. */ + { ""accept_pgphook"", DT_QUAD, R_NONE, OPT_ACCEPTPGPHOOK, M_ASKYES }, + /* + ** .pp + ** If set to \fIyes\fP, pgp-hook keys will be accepted without question. + ** Setting this to \fIno\fP effectively disables the pgp-hook command. + */ { ""alias_file"", DT_PATH, R_NONE, UL &AliasFile, UL ""~/.muttrc"" }, /* ** .pp diff -rup mutt-1.5.5.1/mutt.h mutt-shevek/mutt.h --- mutt-1.5.5.1/mutt.h 2003-11-05 10:41:32.000000000 +0100 +++ mutt-shevek/mutt.h 2004-02-19 19:44:14.000000000 +0100 @@ -289,6 +289,7 @@ enum #endif OPT_SUBJECT, OPT_VERIFYSIG, /* verify PGP signatures */ + OPT_ACCEPTPGPHOOK, /* accept a key from a pgp-hook */ /* THIS MUST BE THE LAST VALUE. */ OPT_MAX diff -rup mutt-1.5.5.1/pgp.c mutt-shevek/pgp.c --- mutt-1.5.5.1/pgp.c 2003-11-05 10:41:33.000000000 +0100 +++ mutt-shevek/pgp.c 2004-02-19 19:49:35.000000000 +0100 @@ -1055,7 +1055,7 @@ char *pgp_findKeys (ADDRESS *to, ADDRESS { int r; snprintf (buf, sizeof (buf), _(""Use keyID = \""%s\"" for %s?""), keyID, p->mailbox); - if ((r = mutt_yesorno (buf, M_YES)) == M_YES) + if ((r = query_quadoption (OPT_ACCEPTPGPHOOK, buf)) == M_YES) { if (is_numerical_keyid (keyID)) { -- 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 cc Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs gcc version 2.95.4 20011002 (Debian prerelease) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.3.28i (2002-03-13) 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.20 (i586) [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_GNUTLS +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 +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=""/usr/bin/ispell"" SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/share/mutt"" SYSCONFDIR=""/etc"" EXECSHELL=""/bin/sh"" MIXMASTER=""mixmaster"" To contact the developers, please mail to . To report a bug, please use the flea(1) utility. patch-1.5.tlr.mx_open_append.2 patch-1.3.28.cvs.indexsegfault patch-1.3.27.bse.xtitles.1 patch-1.3.26.appoct.3 patch-1.3.15.sw.pgp-outlook.1 patch-1.3.27.admcd.gnutls.19 Md.use_editor Md.paths_mutt.man Md.muttbug_no_list Md.use_etc_mailname Md.muttbug_warning Md.gpg_status_fd patch-1.3.24.rr.compressed.1 patch-1.3.25.cd.edit_threads.9.1 patch-1.3.23.1.ametzler.pgp_good_sign >How-To-Repeat: >Fix: }}}" Bas Wijnen 2192 mutt save does not use alias names? mutt Mutt 1.4.2.1i (2004-02-12) enhancement mutt-dev new 2006-03-03T07:12:13-08:00 2010-08-09T00:38:25-07:00 "{{{ A potential switcher from elm (yes I am a dinosaur). There is only one thing I can't figure out... In elm, if you have alias bob bob.barker@home.com and bob sends you mail.. when you save that mail it is saved by default a a folder using the alias name (bob), not bob.barker. I can find no such config value to tickle for mutt that will permit the same. So far every attempt I have made to save mail in mutt ignores the concept that I have aliases defined for these people because I want to save the typing. Outgoing mail to pp with aliases seems to work fine. >How-To-Repeat: >Fix: Unknown }}}" zimcomm@… 2939 next-unread-mailbox does not add much new functionality mutt enhancement mutt-dev new 2007-08-07T00:04:24-07:00 2009-08-31T09:05:01-07:00 "Currently ''$next-unread-mailbox'' will change to the next mailbox with '''new''' mail, but not old unread (as the name implies). If I have ''$mark_old'' set and I exit mutt for some reason I found no easy way to jump to folders containing unread mail. ''$next-unread-mailbox'' could (should?) do this. Thanks for reading, Andrei" amp 2976 "Mutt writes unsolicited ""Lines"" and ""Content-Length"" headers" mutt enhancement mutt-dev new 2007-11-02T07:13:58-07:00 2009-06-12T16:30:39-07:00 "This annoyed me since the first day that I started using mutt: The unsolicted ""Lines"" and ""Content-Length"" headers that mutt adds to existing mailbox files. These should be kept up to date if they are already present, perhaps added to newly created messages, but not added to existing mailbox files. " rtc 3147 Allow the user to set the pager tabshift display enhancement mutt-dev new 2009-01-05T13:43:13-08:00 2011-04-12T22:34:41-07:00 "When you frequently receive code that is indented with TAB (as it *should*) this is painful to have a tab stop every 8 chars. This should be user configurable. The attached patch does this." rixed 3159 Changing attachment type not possible for multiple attachments at once mutt enhancement mutt-dev new 2009-01-25T14:07:34-08:00 2009-01-25T14:07:34-08:00 "Forwarding from http://bugs.debian.org/434236 --- Hi, mutt seems to fail to be able to change the encoding of multiple attachments at once. Since I need to send hundreds of attachments at once it is very important for me. Selecting multiple file to attach is possible by just pressing t in the file browser. I can also mark all attachments using shift+t (t changes To:) and I can also press ; to operate an all marked attachments and Ctrl+t so change the encoding. Nevertheless this affects only the current attachment and not all. Jens " antonio@… 3175 mutt should display keyid for which it wants the password crypto enhancement mutt-dev new 2009-01-27T12:15:14-08:00 2009-02-16T07:28:15-08:00 "Forwarding from http://bugs.debian.org/140430 ---- Hi! If one has more than one secret key it's hard to guess just from the indexpage which mantry an encrypted received mail wants to have: Enter PGP passphrase: It would be more than helpful if at least the keyid and the main uid of that key will be shown, too. As the people that use more than one secret key are rather few this I set this just to Severity: minor but it should be treated higher because it's rather annoying to have to ^Forget the passphrase and reenter the one for the real needed key." antonio@… 3211 [-- Autoview using %s --] should have a format string mutt enhancement mutt-dev new 2009-03-31T14:36:34-07:00 2009-04-01T12:55:13-07:00 "Some of my mailcap entries are quite long. They show up in the mutt pager like this: [-- Autoview using w3m -cols 70 -o frame=1 -o graphic_char=1 -o ignore_null_img_alt=1 -o color=0 -o follow_locale=1 -dump file://'/tmp/mutt.html' --] I'd really like to tell mutt to show me only: [-- Autoview using w3m --] That would be my personal preference, but I can imagine other preferences. Can we make a format string for this?" agriffis 3248 mutt should not retry every time to verify a signature if the previously failed mutt 1.5.19 enhancement mutt-dev new 2009-06-12T16:29:57-07:00 2009-06-12T16:29:57-07:00 "Forwarding from http://bugs.debian.org/488835 {{{ Hello Maintainer, please forward this wishlist bug to upstream: I have set ""autoverify=yes"" and I like to see mutt caching results of FAILED verifications for a couple of time like 15 minutes or such. It is realy annoying, if a keyserver is temporary not availlable and mutt must wait every time for gpg and its 300 seconds timeout... If I try to ^C the process, gpg screw up the TUI with weird characters and force me to use after each interrupted gpg actions to ^l. }}}" antonio@… 3295 postponed email marked new (make this configurable) mutt 1.5.20 enhancement mutt-dev new 2009-07-14T11:13:37-07:00 2009-07-24T04:19:07-07:00 "Forwarding from http://bugs.debian.org/535994 {{{ When I postpone an email, it is flagged as new. I find this annoying because in my mind ""new"" emails are ones that I've not read, and this isn't true about postponed emails. Furthermore this is distracting because my status_format configuration variable includes %b (number of mailboxes with new mail) and postponed emails marked new are included in this count. Thus, after postponing an email, %b increases by one, effectively notifying me I've just postponed an email; this is telling me something I already know. Can mutt be configured so new emails are not marked as new? }}} " antonio@… 3327 make tag-prefix available in the pager mutt 1.5.20 enhancement mutt-dev new 2009-09-06T12:07:12-07:00 2009-09-06T12:07:12-07:00 "Forwarding from http://bugs.debian.org/539675 {{{ Hi, The tag-prefix function works fine in the index, but it does not work at all in the pager. I tried using a macro, key binding, and the push and exec commands in the pager - none of them work. For example, :exec tag-prefix gives the error message, tag-prefix: no such function Here is how I would like to use tag-prefix in the pager, 1. I make a first pass over incoming mail in the index. I tag all spam, and then at the end of the first pass, I use tag-prefix to dispose of the spam. 2. I then make a second pass over incoming mail in the pager. I tag all non-spam, and dispose of each message as I read it, as appropriate to each message. At the end of the pass, I would like to use tag-prefix to dispose of the tagged non-spam. }}}" antonio@… 3328 mutt should handle unencoded whitespace in Q-coded strings mutt 1.5.20 enhancement mutt-dev new 2009-09-06T13:00:13-07:00 2009-10-21T14:21:46-07:00 "Forwarding from http://bugs.debian.org/497171 {{{ Hi, a Mail with Subject: =?us-ascii?Q?Ein neuer?= gets displayed as ""=?us-ascii?Q?Ein neuer?="" in mutt. While this is technicall correct (unencoded spaces are not allowed in Q-encoded strings), mutt should be a little more tolerant here since a lot of software generates that kind of . I'd love to see Subject: Ein neuer on such input. Greetings Marc }}}" antonio@… 3375 Please support globbing in attachment selection mutt 1.5.20 enhancement mutt-dev new 2010-01-31T10:29:26-08:00 2010-02-01T09:30:45-08:00 "Forwarding from http://bugs.debian.org/552149 --- {{{ I often want to attach several files to a mail. It would help if mutt supported globbing in the prompt for an attachment filename, so I could say /path/to/*.patch. }}} Cheers Antonio" antonio@… 3388 [FR] handle MIME misencoded headers mutt 1.4 enhancement mutt-dev new 2010-02-27T09:06:01-08:00 2010-02-27T09:09:36-08:00 Back in 2003, Kirill Shutemov has posted the attached patch to work around message headers broken wrt RFC2047: https://bugzilla.altlinux.org/3369 (in Russian). Would you please consider its inclusion in 1.4 and or 1.5? gvy 3436 Possibility to sort by the subject's number of occurrences in the current mailbox user interface 1.5.20 enhancement mutt-dev new 2010-08-02T09:41:44-07:00 2010-08-02T09:41:44-07:00 "One main criteria to recognize spam is that the more or less same mail appears more than once. The more often a mail appears, the more likely it is spam. Those multiple occurrences of one spam mail often share the same subject. So IMHO while sorting by subject already helps a lot when skimming through spam folders, sorting by the subject's number of occurrences in that folder would be even better to quickly e.g. delete or feed the most obvious spams." xtaran 3446 "Make ""mark_old"" a quad option" mutt enhancement mutt-dev new 2010-08-13T15:14:08-07:00 2010-11-05T22:37:39-07:00 "(just almost c&p from[1], reporting in bugzilla as suggeted[2]) Hi, The attached patch makes the ""mark_old"" option to be a quad option. I find this useful because I don't always want to mark mails as old, just sometimes. And in fact, I only want mutt to ask me about it only on certain mailboxes. So making it a quad option lets me use mutt this way (this patch + a folder hook to set that option on some mailboxes) After writing the patch, of course ;), I found that there was a third party patch that does this (and more things)[3]. I didn't find any reason why that patch was not applied, so I thought perhaps it was because for some of the other things that patch does and this patch could be applied anyways. This is my first time writing a patch for mutt so, even in a so simple patch, I can have done something fundamentally wrong or something like that. My apologies if that is the case :) Now about the patch itself. There's one thing that I really doubt: the change to pop.c. I dont know what the correct thing to do is. I'm not sure if checking for ==M_YES is ok, or checking for != M_NO, or.. I don't know. I've tried this with local mail only (so I didn't try the change to pop.c I guess) and have checked the patch with ""check_sec.sh"". If the patch looks ok I can send a v2 perhaps changing the text to ""Mark new unread mails as old?"" and, if needed, rebase on top of current HEAD too ? Thanks a lot, Rodrigo PS: I'm not subscribed to mutt-dev anymore, please let me know if I need to be. [1]: http://marc.info/?l=mutt-dev&m=127585905107686&w=2 [2]: http://marc.info/?l=mutt-dev&m=128165837701038&w=2 [3]: http://www.schrab.com/aaron/mutt/" rata 3452 "Make ""Re: "" prepending to subject when replying optional" mutt enhancement mutt-dev new 2010-09-17T07:12:21-07:00 2010-09-23T08:10:19-07:00 "Quoting RFC2822: The ""Subject:"" field is the most common and contains a short string identifying the topic of the message. When used in a reply, the field body MAY start with the string ""Re: "" (from the Latin ""res"", in the matter of) followed by the contents of the ""Subject:"" field body of the original message. If this is done, only one instance of the literal string ""Re: "" ought to be used since use of other strings or more than one instance can lead to undesirable consequences. Attached patch adds a boolean configuration option ""reply_prefix"", defaulting to on. If this flag is turned off, original subject will be used, unaltered." pnl 3478 "Naming the gnupg signature filename instead of ""noname"" filename" mutt 1.5.20 enhancement mutt-dev new 2010-12-12T02:57:25-08:00 2010-12-14T16:35:56-08:00 "Hi, When I sign and send an email with mutt, the signature file is automatically named ""noname"". I would prefer something like that ""signature.asc"". I found a solution to resolve this minor problem: By googling a bit, I found the vk.pgp_verbose_mime patch (here is the original patch: http://www.doorstop.net/projects ) which add the pgp_mime_signature_filename variable. I adapted it to my current version of mutt (~)1.5.21-r1 (the latest unstable version of mutt on Gentoo Linux) and I wrote an overlay. After patching, compiling and installing, it works perfectly. To use the feature offered by this patch, just add these two lines in your .muttrc file : set pgp_mime_signature_filename="""" set pgp_mime_signature_description="""" It would be great to add it directly to mutt sources (the patch is very small and simple, but useful) JC Please find here the mails thread sent on gentoo-users ML: http://groups.google.com/group/linux.gentoo.user/msg/2a54398b522c0d04 And the bug report I filed on the Gentoo bugtracker: https://bugs.gentoo.org/show_bug.cgi?id=348477" schplaf 3513 mutt: unable to attach a folder mutt 1.5.21 enhancement mutt-dev new 2011-04-27T15:44:30-07:00 2012-01-19T14:42:41-08:00 "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. }}}" antonio@… 3598 move question asked in Czech but response expected in English mutt 1.5.21 1.6 defect mutt-dev infoneeded_new 2012-11-08T01:19:04-08:00 2012-12-22T20:04:29-08:00 "Hi, I'm using Mutt 1.5.21 on OpenBSD 5.2 I set LANG=cs_CZ.ISO8859-2 I have set move=ask-no I't getting question about moving messages in Czech, (ne/ano), but I have to press y (yes) to go through this question. " navratil 579 Mailbox loading should be interruptable mutt 1.3.17i 2.0 enhancement mutt-dev new 2001-05-03T00:53:18-07:00 2007-04-07T14:34:19-07:00 "It would be nice if mutt allowed a key to be bound to a function which aborted loading of a mailbox and left mutt in the (no mailbox open) state. Often when I skim mailboxes I make an off-by-one error and open some huge mailbox instead of the one I wanted. Waiting a few seconds is not intolerable, but having a key to abort the loading and get on with what I was trying to do would be a great feature. I'm not sure which context this binding should go under." aaronl@… 919 Feature request with implementation: IMAP folder attributes UNSEEN and MESSAGES in folder_format IMAP 1.3.24i 2.0 enhancement mutt-dev new 2001-12-17T09:20:08-08:00 2008-10-31T12:35:51-07:00 "{{{ Package: mutt Version: 1.3.24i Severity: wishlist -- Please type your report below this line Here's something I've been wanting from Mutt: IMAP folder attributes UNSEEN and MESSAGES for the browser. Patch is against stock 1.3.24i. I'd be very glad if something like this made its way to the official version. The implementation could probably be more efficient (querying all the attributes from the server in a single go), but it doesn't seem to be too slow for me. --- ./doc/manual.sgml 2001/12/16 20:04:34 1.1 +++ ./doc/manual.sgml 2001/12/16 19:57:09 @@ -3572,7 +3572,9 @@ %F file permissions %g group name (or numeric gid, if missing) %l number of hard links -%N N if folder has new mail, blank otherwise +%M blank for non-IMAP mailboxes; IMAP: number of messages +%N N if folder has new mail, blank otherwise (IMAP: number of RECENT messages +%U blank for non-IMAP mailboxes; IMAP: number of UNSEEN messages %s size in bytes %t * if the file is tagged, blank otherwise %u owner name (or numeric uid, if missing) --- ./imap/imap.c 2001/12/16 13:27:17 1.1 +++ ./imap/imap.c 2001/12/16 13:34:57 @@ -1127,9 +1127,9 @@ return result; } -/* returns count of recent messages if new = 1, else count of total messages. +/* returns count of recent messages if new = 1, count of unseen if new > 1, + * else count of total messages * (useful for at least postponed function) - * Question of taste: use RECENT or UNSEEN for new? * 0+ number of messages in mailbox * -1 error while polling mailboxes */ @@ -1180,7 +1180,7 @@ mutt_bit_isset(idata->capabilities,STATUS)) { snprintf (buf, sizeof (buf), ""STATUS %s (%s)"", mbox, - new ? ""RECENT"" : ""MESSAGES""); + (new > 1 ? ""UNSEEN"" : (new ? ""RECENT"" : ""MESSAGES""))); } else /* Server does not support STATUS, and this is not the current mailbox. --- ./buffy.h 2001/12/16 13:18:42 1.1 +++ ./buffy.h 2001/12/16 13:19:28 @@ -24,6 +24,8 @@ #endif /* BUFFY_SIZE */ struct buffy_t *next; short new; /* mailbox has new mail */ + short unseen; /* mailbox has unseen mail */ + short messages; /* total messages in mailbox */ short notified; /* user has been notified */ short magic; /* mailbox type */ short newly_created; /* mbox or mmdf just popped into existence */ --- ./buffy.c 2001/12/16 13:19:31 1.1 +++ ./buffy.c 2001/12/16 13:26:07 @@ -365,10 +365,16 @@ #ifdef USE_IMAP case M_IMAP: - if ((tmp->new = imap_mailbox_check (tmp->path, 1)) > 0) - BuffyCount++; - else - tmp->new = 0; + tmp->new = imap_mailbox_check (tmp->path, 1); + tmp->unseen = imap_mailbox_check (tmp->path, 2); + if (tmp->new > 0 || tmp->unseen > 0) + BuffyCount++; + else { + tmp->new = 0; + tmp->unseen = 0; + } + if ((tmp->messages = imap_mailbox_check (tmp->path, 0)) <= 0) + tmp->messages = 0; break; #endif --- ./browser.c 2001/12/16 13:30:07 1.1 +++ ./browser.c 2001/12/16 13:47:21 @@ -237,6 +237,24 @@ mutt_format_s (dest, destlen, fmt, """"); break; + case 'M': +#ifdef USE_IMAP + if (mx_is_imap (folder->ff->desc)) + { + if (!optional) + { + snprintf (tmp, sizeof (tmp), ""%%%sd"", fmt); + snprintf (dest, destlen, tmp, folder->ff->messages); + } + else if (!folder->ff->messages) + optional = 0; + break; + } +#endif + snprintf (tmp, sizeof (tmp), ""%%%sc"", fmt); + snprintf (dest, destlen, tmp, ' '); + break; + case 'N': #ifdef USE_IMAP if (mx_is_imap (folder->ff->desc)) @@ -254,7 +272,25 @@ snprintf (tmp, sizeof (tmp), ""%%%sc"", fmt); snprintf (dest, destlen, tmp, folder->ff->new ? 'N' : ' '); break; - + + case 'U': +#ifdef USE_IMAP + if (mx_is_imap (folder->ff->desc)) + { + if (!optional) + { + snprintf (tmp, sizeof (tmp), ""%%%sd"", fmt); + snprintf (dest, destlen, tmp, folder->ff->unseen); + } + else if (!folder->ff->unseen) + optional = 0; + break; + } +#endif + snprintf (tmp, sizeof (tmp), ""%%%sc"", fmt); + snprintf (dest, destlen, tmp, ' '); + break; + case 's': if (folder->ff->st != NULL) { @@ -300,7 +336,7 @@ } static void add_folder (MUTTMENU *m, struct browser_state *state, - const char *name, const struct stat *s, int new) + const char *name, const struct stat *s, int new, int unseen, int messages) { if (state->entrylen == state->entrymax) { @@ -324,6 +360,8 @@ } (state->entry)[state->entrylen].new = new; + (state->entry)[state->entrylen].messages = messages; + (state->entry)[state->entrylen].unseen = unseen; (state->entry)[state->entrylen].name = safe_strdup (name); (state->entry)[state->entrylen].desc = safe_strdup (name); #ifdef USE_IMAP @@ -407,7 +445,7 @@ tmp = Incoming; while (tmp && mutt_strcmp (buffer, tmp->path)) tmp = tmp->next; - add_folder (menu, state, de->d_name, &s, (tmp) ? tmp->new : 0); + add_folder (menu, state, de->d_name, &s, (tmp) ? tmp->new : 0, (tmp) ? tmp->unseen : 0, (tmp) ? tmp->messages : 0); } closedir (dp); browser_sort (state); @@ -431,14 +469,14 @@ #ifdef USE_IMAP if (mx_is_imap (tmp->path)) { - add_folder (menu, state, tmp->path, NULL, tmp->new); + add_folder (menu, state, tmp->path, NULL, tmp->new, tmp->unseen, tmp->messages); continue; } #endif #ifdef USE_POP if (mx_is_pop (tmp->path)) { - add_folder (menu, state, tmp->path, NULL, tmp->new); + add_folder (menu, state, tmp->path, NULL, tmp->new, tmp->unseen, tmp->messages); continue; } #endif @@ -452,7 +490,7 @@ strfcpy (buffer, NONULL(tmp->path), sizeof (buffer)); mutt_pretty_mailbox (buffer); - add_folder (menu, state, buffer, &s, tmp->new); + add_folder (menu, state, buffer, &s, tmp->new, tmp->unseen, tmp->messages); } while ((tmp = tmp->next)); browser_sort (state); --- ./browser.h 2001/12/16 13:35:45 1.1 +++ ./browser.h 2001/12/16 13:42:38 @@ -31,6 +31,8 @@ char *desc; unsigned short new; + unsigned short unseen; + unsigned short messages; #ifdef USE_IMAP char delim; --- ./init.h 2001/12/16 20:03:37 1.1 +++ ./init.h 2001/12/16 20:02:41 @@ -533,7 +533,9 @@ ** .dt %F .dd file permissions ** .dt %g .dd group name (or numeric gid, if missing) ** .dt %l .dd number of hard links - ** .dt %N .dd N if folder has new mail, blank otherwise + ** .dt %M .dd blank for non-IMAP folders; IMAP: number of messages + ** .dt %N .dd N if folder has new mail, blank otherwise (IMAP: number of RECENT messages) + ** .dt %U .dd blank for non-IMAP folders; IMAP: number of UNSEEN messages ** .dt %s .dd size in bytes ** .dt %t .dd * if the file is tagged, blank otherwise ** .dt %u .dd owner name (or numeric uid, if missing) -- 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 20011006 (Debian prerelease) - CFLAGS -Wall -pedantic -g -O2 -- Mutt Version Information Mutt 1.3.24i (2001-11-29) 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.0 (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 SENDMAIL=""/usr/sbin/sendmail"" MAILPATH=""/var/mail"" PKGDATADIR=""/usr/local/share/mutt"" SYSCONFDIR=""/usr/local/etc"" EXECSHELL=""/bin/sh"" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. >How-To-Repeat: >Fix: }}}" ntyni+mutt@… 920 Feature request with implementation: wildcards in 'mailboxes' list for IMAP folders IMAP 1.3.24i 2.0 enhancement mutt-dev new 2001-12-17T09:36:50-08:00 2007-04-12T09:57:05-07:00 "Here's a way to enable wildcards in IMAP folder names for the 'mailboxes' variable. The wildcards are expanded by the IMAP server (LIST or LSUB, depending on the corresponding option), when the folder is checked for the first time. The 'imap_passive' option is honoured. I'd be very glad if something like this made its way to the official release. Patch against stock 1.3.24i: {{{ --- ./doc/manual.sgml 2001/12/16 21:26:08 1.1 +++ ./doc/manual.sgml 2001/12/16 21:29:54 @@ -1235,6 +1235,11 @@ name=""$folder""> and ) should be executed before the User defined headers