http://blog.gmane.org/gmane.mail.mutt.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.mail.mutt.devel/19837 <pre>#3585: Updated Italian translation ----------------------------+----------------------------------------------- Reporter: marco | Owner: mutt-dev Type: enhancement | Status: new Priority: minor | Milestone: Component: user interface | Version: HEAD Keywords: | ----------------------------+----------------------------------------------- Translations have been fixed and converted to UTF-8; some of them still need to be checked further. </pre> Mutt 2012-05-25T20:36:32 http://comments.gmane.org/gmane.mail.mutt.devel/19835 <pre>New changeset in mutt: http://dev.mutt.org/hg/mutt/rev/0488deb39a35 changeset: 6205:0488deb39a35 branch: HEAD tag: tip user: Brendan Cully &lt;brendan&lt; at &gt;kublai.com&gt; date: Thu May 24 22:02:57 2012 -0700 summary: Remove AM_C_PROTOTYPES from configure.ac (closes #3579) </pre> Brendan Cully 2012-05-25T07:00:02 http://comments.gmane.org/gmane.mail.mutt.devel/19833 <pre>#3584: 1.5.21 To/CC/Bc fields does not preserve values (in RFC comments) ---------------------------------------+------------------------------------ Reporter: jaalto | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: mutt | Version: 1.5.21 Keywords: rfc, standards, violation | ---------------------------------------+------------------------------------ == Problem == Mutt does not preserve the contents of fields To/CC/Bcc as is. An example: To: John Doe (Head of HR department) &lt;jdoe&lt; at &gt;example.com&gt; CC: Joe Average (HR Assistant) &lt;jave&lt; at &gt;example.com&gt; After composing this message in editor, back to "send screen", the parts in parenthesis have been stripped: To: John Doe &lt;jdoe&lt; at &gt;example.com&gt; CC: Joe Average &lt;jave&lt; at &gt;example.com&gt; == severity == This is a serious defect in software that affects use daily; these fields are very </pre> Mutt 2012-05-24T07:09:02 http://comments.gmane.org/gmane.mail.mutt.devel/19832 <pre>New changeset in mutt: http://dev.mutt.org/hg/mutt/rev/0fb6d7579fd1 changeset: 6204:0fb6d7579fd1 branch: HEAD tag: tip user: Brendan Cully &lt;brendan&lt; at &gt;kublai.com&gt; date: Wed May 23 23:29:37 2012 -0400 summary: Support passwords of up to 127 characters. </pre> Brendan Cully 2012-05-24T07:00:01 http://comments.gmane.org/gmane.mail.mutt.devel/19831 <pre>Folks, OpenSSL 1.0.1 introduced support for TLSv1.1 and TLSv1.2. These are not used by mutt. This patch fixes that. Counter-intuitively, the OpenSSL folks have TLSv1_client_method() negotiate *only* TLSv1.0, and SSLv23_client_method() remains the only method which can negotiate different versions. This is true at least as of 1.0.1c (the latest release at time of writing). The attached patch uses SSLv23_client_method() and SSL_CTX_set_options() to then disable SSLv2 and SSLv3. This mail is sent with such a patched mutt, and you should thus see that the initial Received: header uses the cipher: TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256 Regards, -Phil </pre> Phil Pennock 2012-05-23T19:57:57 http://comments.gmane.org/gmane.mail.mutt.devel/19830 <pre>#3583: mutt-1.5.21: extract-keys does not extract PGP keys from S/MIME signed mail ---------------------------------+------------------------------------------ Reporter: matthias&lt; at &gt;… | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: mutt | Version: Keywords: | ---------------------------------+------------------------------------------ {{{ 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 </pre> Mutt 2012-05-23T18:54:06 http://comments.gmane.org/gmane.mail.mutt.devel/19829 <pre>#3582: smtp_auth_sasl: error base64-decoding server response ------------------------+--------------------------------------------------- Reporter: tczengming | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: mutt | Version: 1.5.21 Keywords: | ------------------------+--------------------------------------------------- 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&lt; at &gt;smtp.163.com:25/"' to&lt; at &gt;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_CO</pre> Mutt 2012-05-22T06:24:15 http://comments.gmane.org/gmane.mail.mutt.devel/19826 <pre>#3581: Folder-history ignores -f folder from CLI --------------------+------------------------------------------------------- Reporter: Wastl | Owner: mutt-dev Type: defect | Status: new Priority: minor | Milestone: Component: mutt | Version: HEAD Keywords: | --------------------+------------------------------------------------------- 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 &lt;up- arrow&gt; 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. </pre> Mutt 2012-05-18T12:07:29 http://comments.gmane.org/gmane.mail.mutt.devel/19825 <pre>#3580: mutt -H $draft ignores recipient arguments on CLI -------------------------+-------------------------------------------------- Reporter: adam.spiers | Owner: mutt-dev Type: defect | Status: new Priority: minor | Milestone: 1.6 Component: mutt | Version: 1.5.21 Keywords: | -------------------------+-------------------------------------------------- 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 </pre> Mutt 2012-05-17T22:16:58 http://comments.gmane.org/gmane.mail.mutt.devel/19821 <pre>#3579: Automake 1.12 prevents mutt HEAD from configuring ----------------------+----------------------------------------------------- Reporter: sinecure | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: mutt | Version: 1.5.21 Keywords: | ----------------------+----------------------------------------------------- The new automake removed AM_C_PROTOTYPES. Removing that line from configure.ac (as shown in the `hg diff` below) allows the `./prepare` command to complete. {{{ diff -r 41a8d7dceb6c configure.ac --- a/configure.ac Sun Apr 29 22:15:19 2012 -0700 +++ b/configure.ac Fri May 11 16:17:15 2012 -0400 &lt; at &gt;&lt; at &gt; -30,7 +30,6 &lt; at &gt;&lt; at &gt; AC_PROG_CC AC_ISC_POSIX -AM_C_PROTOTYPES if test "x$U" != "x"; then AC_MSG_ERROR(Compiler not ANSI compliant) fi }}} </pre> Mutt 2012-05-11T20:29:11 http://comments.gmane.org/gmane.mail.mutt.devel/19815 <pre>I recently started using Mac OS X again, and installed HomeBrew [1] to be able to automate the upgrade of various software components not already included. When installing the requisite programs to build mutt from HEAD, automake 1.12 was installed. Unfortunately, this new version of automake caused mutt not to prepare! The output of my attempt to prepare follows. #v+ dave&lt; at &gt;pooh:~/usr/src/mutt/mutt$ cat ../configure-mutt.sh #!/bin/sh # For FreeBSD, append '=/usr/local' to the --with-sasl line. # For Mac OS X, append '=/usr/local' to the --with-tokyocabinet line. ./prepare \ --prefix=$HOME/usr \ --with-homespool=Maildir \ --enable-debug \ --enable-hcache \ --with-tokyocabinet=/usr/local \ --with-curses \ --enable-smtp \ --enable-imap \ --with-ssl \ --with-sasl #v- Note: This prepare command has worked in the past on Mac OS X. Next, I make sure my sources are up to date, and try to prepare. #v+ dave&lt; at &gt;pooh:~/usr/src/mutt/mutt$ hg pull -u pulling from http://dev.mutt.org/hg/mutt searching for cha</pre> David J. Weller-Fahy 2012-05-11T01:49:54 http://comments.gmane.org/gmane.mail.mutt.devel/19813 <pre>Hi, first i have to say thanks for Mutt(1), i've used it for years. Now i'm getting older and am currently on the «plain and antique» trip and am therefore slowly extending nail(1), as of Heirloom. Anyway, while doing some work on Mail-Followup-To: stuff i took mutt(1) as reference and found that it reacts strange in respect to interaction with the standardized Reply-To: field. You can very well repeat this with having one or two entries in Reply-To:, alone and ditto in conjunction with one+ entries in Mail-Followup-To:; and see how nice it gets when there was data in Cc:. What i planned for my pfffff was that i join Reply-To:'s with Mail-Followup-To:'s, keeping the stuff in Cc: around. (Basic idea: editing later is possible.) Basic thought: Reply-To:'s are often somewhat automatic, whereas Mail-Followup-To:, though never beyond draft, is used and added to mails by hand (examples can be found at least in last days of OpenBSD-ports). I just yet stumbled over that problem so the brain is behind (with the r</pre> Steffen Daode Nurpmeso 2012-05-10T15:17:18 http://comments.gmane.org/gmane.mail.mutt.devel/19812 <pre>2 new changesets in mutt: http://dev.mutt.org/hg/mutt/rev/41a8d7dceb6c changeset: 6203:41a8d7dceb6c branch: HEAD tag: tip user: Brendan Cully &lt;brendan&lt; at &gt;kublai.com&gt; date: Sun Apr 29 22:15:19 2012 -0700 summary: gnutls: catch gnutls_init failures http://dev.mutt.org/hg/mutt/rev/aadaeb69cbd0 changeset: 6202:aadaeb69cbd0 branch: HEAD user: Brendan Cully &lt;brendan&lt; at &gt;kublai.com&gt; date: Sun Apr 29 22:14:22 2012 -0700 summary: give user time to read SASL init error message </pre> Brendan Cully 2012-04-30T07:00:01 http://comments.gmane.org/gmane.mail.mutt.devel/19806 <pre>#3578: arbitrary MAILDIR outside HOME impossible ---------------------+------------------------------------------------------ Reporter: jidanni | Owner: mutt-dev Type: defect | Status: new Priority: minor | Milestone: Component: mutt | Version: 1.5.21 Keywords: | ---------------------+------------------------------------------------------ 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. </pre> Mutt 2012-04-26T19:29:26 http://comments.gmane.org/gmane.mail.mutt.devel/19800 <pre>#3577: send-hook should not be executed if the mail is not going to be sent -------------------------+-------------------------------------------------- Reporter: Y_Plentyn | Owner: mutt-dev Type: enhancement | Status: new Priority: minor | Milestone: Component: mutt | Version: Keywords: | -------------------------+-------------------------------------------------- Forwarding from http://bugs.debian.org/641457 : {{{ I have a hook like this: send-hook '~s keyword' "push '&lt;edit-subject&gt;&lt;kill-line&gt;Thank you&lt;enter&gt;'" 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 b</pre> Mutt 2012-04-22T15:21:30 http://comments.gmane.org/gmane.mail.mutt.devel/19799 <pre>#3576: Makes new connection to the SMTP server for every mail, even when sending several in one action -----------------------+---------------------------------------------------- Reporter: Y_Plentyn | Owner: mutt-dev Type: defect | Status: new Priority: minor | Milestone: Component: mutt | Version: Keywords: | -----------------------+---------------------------------------------------- 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 }}} </pre> Mutt 2012-04-22T14:51:04 http://comments.gmane.org/gmane.mail.mutt.devel/19798 <pre>#3575: smime_keys.pl fails on filenames with spaces -----------------------+---------------------------------------------------- Reporter: Y_Plentyn | Owner: mutt-dev Type: defect | Status: new Priority: minor | Milestone: Component: crypto | Version: Keywords: | -----------------------+---------------------------------------------------- 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&lt; at &gt;ak-online.be renewed.p12". Unfortunately 'smime_keys add_p12 "cacert kandre&lt; at &gt;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]: &gt;&gt;&gt;&gt; snip &lt;&lt;&lt;&lt; 156: my $cmd = "$opensslbin pkcs12 -in $ARGV[1]</pre> Mutt 2012-04-22T14:23:25 http://comments.gmane.org/gmane.mail.mutt.devel/19796 <pre>#3574: SegFault on verifying gpg key for a message -----------------------+---------------------------------------------------- Reporter: Y_Plentyn | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: mutt | Version: Keywords: | -----------------------+---------------------------------------------------- Forwarding from http://bugs.debian.org/668583 : {{{ Hi, Simply reading debian mailing list, then, when reading this message: http://lists.debian.org/debian-devel/2012/04/msg00245.html mutt segfaulted during the verification of the signature. The bug is totally reproductible and segfault each time. But, maybe the keyring that I have locally can change the behavior (I have the Martin's pubkey). thank you. In attachment: - a tarball with the message. - my config file with personal data anonymized - a _full_ coredump }}} Comment of the forwarder: This seems to be an issue</pre> Mutt 2012-04-22T10:45:38 http://comments.gmane.org/gmane.mail.mutt.devel/19794 <pre>#3573: Run Script When New Mail Arrives ------------------------------------------------+--------------------------- Reporter: stormdragon2976 | Owner: mutt-dev Type: enhancement | Status: new Priority: major | Milestone: Component: mutt | Version: Keywords: sound,script,new mail notification | ------------------------------------------------+--------------------------- 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</pre> Mutt 2012-04-19T15:33:52 http://comments.gmane.org/gmane.mail.mutt.devel/19791 <pre>Incorporating Thomas Dickey's suggestions and corrections. :) curs_main.c | 81 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ globals.h | 3 ++ init.h | 30 ++++++++++++++++++++++ main.c | 3 ++ mutt.h | 1 + mutt_menu.h | 3 ++ pager.c | 7 +++++ status.c | 2 + 8 files changed, 130 insertions(+), 0 deletions(-) # HG changeset patch # User David Champion &lt;dgc&lt; at &gt;uchicago.edu&gt; # Date 1334407343 18000 # Node ID 7016e467e1b4902db1f54146242b9db1758aedd7 # Parent f467353f5657d9504dc5924fefc804fadc586f57 Terminal status line support, based on the xterm title patch. Christoph Berg took the xterm title patch from the mutt mailing list and maintained it for Debian: * Changes made: - 2007-01-27 myon: using %P caused a segfault, updated status.c to catch menu==NULL. - 2007-02-20 myon: make the note about the xterm_set_titles defaults a comment. - 2008-08-02 myon: move set_xterm_* prototypes into the proper header file (cleaner code, no function</pre> David Champion 2012-04-14T12:44:08 http://comments.gmane.org/gmane.mail.mutt.devel/19788 <pre>This update incorporates Thomas Dickey's advice concerning "xt". curs_main.c | 81 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ globals.h | 3 ++ init.h | 30 ++++++++++++++++++++++ main.c | 3 ++ mutt.h | 1 + mutt_menu.h | 3 ++ pager.c | 7 +++++ status.c | 2 + 8 files changed, 130 insertions(+), 0 deletions(-) # HG changeset patch # User David Champion &lt;dgc&lt; at &gt;uchicago.edu&gt; # Date 1334366508 18000 # Node ID 2491e0d4f51693ba0f5caab7455174eccfe2501e # Parent f467353f5657d9504dc5924fefc804fadc586f57 Terminal status line support, based on the xterm title patch. Christoph Berg took the xterm title patch from the mutt mailing list and maintained it for Debian: * Changes made: - 2007-01-27 myon: using %P caused a segfault, updated status.c to catch menu==NULL. - 2007-02-20 myon: make the note about the xterm_set_titles defaults a comment. - 2008-08-02 myon: move set_xterm_* prototypes into the proper header file (cleaner code, no funct</pre> David Champion 2012-04-14T01:23:01 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.mail.mutt.devel