Re: mutt 1.11.1 released
On Tue, Dec 04, 2018 at 04:20:02PM -0800, Will Yardley wrote: On Tue, Dec 04, 2018 at 06:00:48PM -0600, Derek Martin wrote: On Sat, Dec 01, 2018 at 01:22:24PM -0800, Kevin J. McCarthy wrote: > I'm pleased to announce the release of version 1.11.1 (the "A Chorus > Line" release). Instructions for downloading are at > <http://www.mutt.org/download.html>. I'm amused by the release name... Any reason for it? Have other releases had fun names that I missed? =8^) I think because it's a 'chorus line' of 1s... Yes, it was meant to be a reference to the Broadway musical "A Chorus Line"'s melody "One". :-) There haven't been other release names. I just thought this one was special and deserved something. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Sending via command line and $record
On Sat, Dec 01, 2018 at 11:31:38PM +, Dave Woodfall wrote: Is there a way to make sure that all mail sent via CLI saves a copy in =Sent? The only way I can see at the moment is by using a separate startup file. Does adding -e 'set record="=Sent"' to the command line help? -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
mutt 1.11.1 released
Hi Mutt Users, I'm pleased to announce the release of version 1.11.1 (the "A Chorus Line" release). Instructions for downloading are at <http://www.mutt.org/download.html>. This release fixes a crash bug involving the new $imap_qresync feature. Special thanks to ilf for reporting this to me quickly and working with me to figure out the problem. Thanks also to everyone else who reported issues and helped on parts of this release. -Kevin signature.asc Description: PGP signature
Re: Group reply To-vs-Cc recipients
On Thu, Nov 29, 2018 at 03:41:12PM -0800, Ian Zimmerman wrote: I am curious to know in what context "someone" felt it would make a difference. The ticket number is 98, but I thought mutt-users would be a better place to have a discussion. I can't speak for the reporter, but my understanding was the desire to preserve the distinction between primary recipients, towards whom the conversation is directly relevant, and others who may be just being kept in the loop. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Group reply To-vs-Cc recipients
Someone opened a ticket asking about Mutt's group reply behavior. By default (i.e. ignoring Mail-Followup-To, $reply_self, $reply_to, etc.), the To recipients are added to the Cc list of the reply. The ticket reporter thought it made more sense for To recipients to remain in the To list of the reply. Apparently, Thunderbird does this, but not sure about other clients. Have no fear, I have no intention of changing default behavior. But I'm curious about opinions on this list. Is this "established proper" behavior, or is this something reasonable to have an option for? Thank you! -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
mutt 1.11.0 released
Hello Mutt Users, I'm pleased to announce the release of version 1.11.0. Instructions for downloading are at <http://www.mutt.org/download.html>. The tarball can also be obtained directly at <http://ftp.mutt.org/pub/mutt/>. Please take the time to verify the signature file against my key. This release has several new larger features, and a number of small fixes and feature improvements. Please see the UPDATING file, or for more details, the release notes at <http://www.mutt.org/relnotes/1.11/>. As always, a huge thanks to all the people who contributed towards this release. It's very exciting to see the growth of people submitting patches, features, tickets, helping testing, and working on translation. This release is because of you. -Kevin signature.asc Description: PGP signature
Re: OT: culprit in MIME recoding and breaking signatures
On Thu, Nov 22, 2018 at 10:40:22PM -0800, Ian Zimmerman wrote: The winner appears to be Perl, namely the Mail::Audit module (and whatever other modules it relies on). I had a couple of scripts that did gentle transformations of incoming mails. Congratulations on tracking this down. This is a very unpleasant surprise, I have thought of Perl and the more popular CPAN modules as the good old workhorse which would always do the job efficiently and reliably - if not always legibly :) I intentionally preferred Perl for this task over some combination of procmail, formail, sed and pcregrep which would have worked. My world is crumbling :( I'm a bit surprised too. Although it has fallen out of favor, I have used and relied on Perl for a long time too, and it never let me down. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: segfault causes system freeze
On Fri, Nov 23, 2018 at 07:30:00AM +0100, steve wrote: I think it's when I just go back from editing with vim to the pager. Also, are you using IMAP? Yes I do via offlineimap. It sounds like this may be triggered by offlineimap updating while you are in the middle of composing the message. NeoMutt checks for new mail in the pager too, but it looks like in 1.7.2 they botched the redraw-data updates, setting "max" before the index data structures were updated. It looks like this is fixed in the latest version link posted by Jörg. However, I think it would be tricky to get Debian/Ubuntu to patch this for a non-security issue. Your best bet would be to update. Another workaround might be turning off $pager_index_lines. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: segfault causes system freeze
On Thu, Nov 22, 2018 at 04:19:43PM +0100, steve wrote: I would guess that one of the thread chains is broken. Does the crash happen everytime in the same mailbox? That's a question I also asked myself. I don't know for now. I'll have to investigate a bit more. The problem is that it doesn't happen so often. I'm not familiar with the changes NeoMutt may have made to their version, but if you can duplicate with a recent Mutt, I may be able investigate further. However, I do have a couple questions that may (or may not) be relevant. Do you always see the crashes in the pager, or is it random? Also, are you using IMAP? -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: /var/mail/$USER read-only
On Wed, Nov 07, 2018 at 09:25:31PM -0500, benfi...@gmail.com wrote: > My linux mail box is /var/mail/$USER, previously I had read and deleted mails > from this mailbox, now I get an error message from mutt, telling me the > mailbox > is read-only. It may be that something is wrong with your mutt_dotlock program. Did you configure --with-mailpath=/var/mail? What are the permissions of /var/mail? Is your mutt_dotlock setgid? Also you may want to check for a stale lockfile in the /var/mail directory. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Help testing 1.11 BETA tarball
Hi Everyone, The 1.11 release is coming up in about three weeks. This time I'm trying something different and have prepared a BETA tarball to get testing/feedback in advance. The translation files haven't been updated yet, but the tarball is at: . The long list of changes is at the bottom of this email, but there are three main features I'd like to especially note for testing/feedback: 1. IMAP CONDSTORE and QRESYNC support. If your IMAP server supports QRESYNC, please enable $imap_qresync and $imap_condstore. (Alas, Gmail users should not do this. It doesn't support QRESYNC and enabling CONDSTORE actually appears to slow Gmail down.) In theory, QRESYNC should make it much faster to open mailboxes, after the initial sync. I've tried to test this with FastMail and Dovecot, but I don't really use IMAP daily. It would be nice to hear from others whether the feature works for you. How do you test for support? Enable 'mutt -d 2', connect to the server and disconnect. Then peek in ~/.muttdebug0: grep for 'CAPABILITY' and then for 'QRESYNC' inside those lines. 2. Inotify mailbox monitoring. This is enabled by default (but can be turned off with --disable-filemonitor). This should allow Mutt to notice mailbox changes much faster. Note that standard polling still occurs via $mail_check and $timeout, so inotify overflows shouldn't result in Mutt failing to notice new mail. 3. Dynamic $index_format content using patterns. See <https://muttmua.gitlab.io/mutt/manual-dev.html#index-format-hook> for an explanation and examples. This is fairly general purpose, but can be used to dynamically format dates for instance. I just added this, so would appreciate some testing. How to compile == On Debian-derived distros, I recommend % sudo apt build-dep mutt % sudo apt install libkyotocabinet-dev Here's the configuration I use, as a starting point. If you use another header cache backend, you'll need to fiddle with the last few arguments: % ./configure \ --prefix=/usr/local \ --with-mailpath=/var/mail \ --enable-debug \ --enable-fcntl \ --enable-gpgme \ --enable-hcache \ --enable-imap \ --enable-smtp \ --enable-pop\ --enable-sidebar\ --enable-compressed \ --with-curses \ --with-gnutls \ --with-sasl \ --with-gss \ --with-idn2 \ --with-mixmaster\ --without-gdbm \ --without-bdb \ --without-qdbm \ --without-tokyocabinet \ --with-kyotocabinet You may need to use --with-idn instead, if your system doesn't have a new IDN2 installed. Also, note that you may want to remove your old header cache files when updating, especially if you compiled with a different backend. The longer list of updates: === (though I may have missed a few things) * inotify mailbox monitoring on Linux * OAUTHBEARER support for IMAP, SMTP and POP See https://gitlab.com/muttmua/mutt/commit/798f749eeeb98ed04028521a2eb3e505c1a83574 * manually updates mailbox statistics, like $mail_check_stats when set * Thread limited views, e.g. ~(pattern), now show new mail as it arrives. * -z and -Z options now work for IMAP mailboxes * IMAP CONDSTORE and QRESYNC support. Set $imap_condstore and/or $imap_qresync to try them out. Note that GMail doesn't support QRESYNC and enabling CONDSTORE can actually make it slower, so please don't enable for GMail. * $abort_noattach now skips quoted lines (as defined by $quote_regexp and $smileys). * The initial IMAP message downloading can be aborted with Ctrl-C. * composes a message to the sender of the selected message. (This also works from the attachment menu) * Address book queries now support multibyte (multicolumn) output * pgpring has been renamed to mutt_pgpring. * Cert prompts now show sha-256 and sha-1 * Non-threaded $sort_aux "reverse-" settings now actually work * Gnu info formatted documentation is generated. * index-format-hook and the new %@name@ expando for $index_format all dynamic index formats using pattern matching. See https://muttmua.gitlab.io/mutt/manual-dev.html#index-format-hook Thanks everyone! -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: muttedit updates (was: Composing blocks checking for new)
On Mon, Nov 05, 2018 at 05:26:07PM -0800, Kevin J. McCarthy wrote: > Setting $resume_draft_files treats the -H filename just like resuming a > postponed draft. This means send-hook's are not evaluated. If you rely > on that to turn on $text_flowed, you may want to add that to the command > line, or perhaps go back to just 'unset signature'. Or move the setting to a send2-hook instead, which is evaluated for resumed files. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: muttedit updates (was: Composing blocks checking for new)
On Tue, Nov 06, 2018 at 08:08:47AM +1100, Cameron Simpson wrote: > On 04Nov2018 09:22, Kevin J. McCarthy wrote: > >On Sat, Nov 03, 2018 at 09:53:07AM +1100, Cameron Simpson wrote: > >> My composition mode always opens the composition in a new tmux session (or > >> screen > > > >Thank you for the detailed write up. I always enjoy reading these kinds > >of posts: nuggets of wisdom from long-time users. > > > >> mutt -e 'set editor=vim-flowed' -e 'unset signature' -H "$filename" > > > >Instead of "-e 'unset signature'", you may want to try "-e 'set > >resume_draft_files'" which turns off even more undesired processing, > >like user-defined headers. > > Thank you, I've applied this suggestion. Hmm... it looks like $text_flowed was somehow turned off. I hope this wasn't due to my suggestion. :-/ Setting $resume_draft_files treats the -H filename just like resuming a postponed draft. This means send-hook's are not evaluated. If you rely on that to turn on $text_flowed, you may want to add that to the command line, or perhaps go back to just 'unset signature'. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Composing blocks checking for new
On Sat, Nov 03, 2018 at 09:53:07AM +1100, Cameron Simpson wrote: > My composition mode always opens the composition in a new tmux session (or > screen Thank you for the detailed write up. I always enjoy reading these kinds of posts: nuggets of wisdom from long-time users. > mutt -e 'set editor=vim-flowed' -e 'unset signature' -H "$filename" Instead of "-e 'unset signature'", you may want to try "-e 'set resume_draft_files'" which turns off even more undesired processing, like user-defined headers. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Test number two - spaces
On Sun, Oct 28, 2018 at 08:55:00AM -0700, Ian Zimmerman wrote: > Perhaps there is a little clue here. Some kind of load balancing seems > to be in effect at osuosl, different hosts (silver, whitealder, > fraxinus, ash) are involved each time. Possibly different amavis > configuration on some of the hosts handling the outbound traffic. Yes, > I suspect amavis more than the other pieces; it should be the only piece > that takes apart the MIME structure. My Received headers match what you posted for the "Test number two" email, and all the signatures verify for me. In fact, I don't recall seeing any failing signatures on this list, before or after the switch to OSUOSL. I would suspect something between OSUOSL and your spoolfile is causing the problem. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: reply-to indicator?
On Tue, Oct 16, 2018 at 11:09:20AM -0700, Ian Zimmerman wrote: > mutt seems to show a "C" flag in the index when my address is in the Cc > list. Is there anything similar for the Reply-To header? I don't think so. > Would it be easy for me (a competent C coder) to hack such a feature > in? Yes. Start in hdr_format_str() [hdrline.c]. The Reply-To header is already parsed and stored in the envelope. You can see it being used for the '%A' option. Alternatively, if you just wanted another flag shown for %T or %Z, you could modify mutt_user_is_recipient() and add a new state/Tochars flag. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Hang on startup
On Mon, Oct 15, 2018 at 02:56:37PM -0400, Ben Boeckel wrote: > I've been experiencing this for a while and I'd like to get to the > bottom of it. When starting `mutt`, sometimes it hangs for a long time > before drawing the UI (input is appropriately buffered though). Is there > some network call done on startup or other I/O (`strace` shows that it > is in the middle of a `poll` call when it is hanging) that might be > timing out? Currently using 1.10.1, but I've been seeing it for a while > now, so it isn't new behavior. Mutt performs a DNS lookup using gethostname() and getaddrinfo() to try to find out the host's FQDN. If you are hanging, it could be this is not configured correctly. Adding a line to /etc/hosts with a FQDN may help: 127.0.1.1 rotor.yourdomain rotor See also https://muttmua.gitlab.io/mutt/manual-dev.html#hostname although setting that does not change the startup behavior because the muttrc is processed afterwards. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: I need some clarification of what 'reply-hook' does please
On Mon, Oct 15, 2018 at 07:46:00PM +0100, Chris Green wrote: > When the documentation says "reply-hook is matched against the message > you are replying to," does that mean I can use it to hook all messages > sent to just one of my 'alternates' addresses? > > I want to execute an action only when I am replying to an E-Mail which > has been sent to 'c...@isbd.net' and not one sent to any of my other > addresses. Will reply-hook do this for me? Yes, pattern operators will be matched against the message you are replying to. They will be matched using the order specified in your muttrc, so you should apply default settings first, and then more specific overrides afterwards: reply-hook ~A 'unset bar' # Default bar off reply-hook '~t ^cl@\.net$' 'set bar' # Except for this address -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Message-ID with "+" in
On Sun, Sep 30, 2018 at 02:48:55PM -0400, Ben Fitzgerald wrote: > / ~i "CAJxpU5h8mE6UcYStOyUzH_T490R\+hOp5dTo\+crvozc5wsnh...@mail.gmail.com" Try doubling the \: / ~i "CAJxpU5h8mE6UcYStOyUzH_T490R\\+hOp5dTo\\+crvozc5wsnh...@mail.gmail.com" -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Check PGP sigs only when I need to
On Wed, Sep 26, 2018 at 03:51:45PM -0700, Ian Zimmerman wrote: > Well I thought about that. But I really want to check the sig _when I > am already on the message_. How do I make mutt re-read the message and > check the sig in my macro? set crypt_verify_sig=no macro pager ,cs \ "set crypt_verify_sig=yes\ set crypt_verify_sig=no" "manual-check-signature" -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: IMAP mailboxes in the sidebar
On Mon, Sep 17, 2018 at 05:44:34AM -0700, Felix Finch wrote: > It does show those two in teh sidebar. But "mailboxes" is only for > incoming mail: > > This command specifies folders which can receive mail and which > will be checked for new messages periodically. > > I want all the mailboxes available, as determined by Lookout, in the > sidebar, but only INBOX needs to be checked for new mail. Sorry, that's how the sidebar is built - it piggybacks on the 'mailboxes' list for determining what to display. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: IMAP mailboxes in the sidebar
On Sun, Sep 16, 2018 at 11:48:18AM -0700, Felix Finch wrote: > Ubuntu 18.04, Mutt 1.9.4. > > set sidebar_format="%B%?F? [%F]?%* %?N?%N/?%S" > set sidebar_new_mail_only=no > set sidebar_visible=yes > > The sidebar shows only INBOX. All other mailboxes are absent. The > same mutt sidebar is fine for local maildirs with a different muttrc. Forgive me for asking what may be a stupid question, but have you *listed* all the mailboxes in question with a 'mailboxes' command in your muttrc? If so, is there any chance you have something running under a hook that is calling unmailboxes? What happens if you add 'mailboxes foo' to your muttrc? Alternatively you could try enabling $imap_check_subscribed and make sure all the relevant mailboxes are subscribed to. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: IMAP mailboxes in the sidebar
On Sun, Sep 16, 2018 at 07:22:55PM -0500, Arturo wrote: > Well I had a similar issue. IIRC, INBOX was always there regardless for me, > but I had to use the full path to get anything else to work. There was a > bug (since fixed) in NeoMutt where it wasnt' expanding = or + to > the full path. Sounds like the same issue to me here in Mutt. > > https://github.com/neomutt/neomutt/issues/485 The commit there was pulled over _from_ Mutt into NeoMutt, and is in Mutt versions 1.8.1 and later. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: imap unread count in folder view?
On Sun, Sep 16, 2018 at 01:24:57PM -0400, Ben Fitzgerald wrote: > any way to get the number of unread messages in the > view? > > I'm happy to have the unread count in the cache, it doesn't have to > be the server's count. Check out %n in $folder_format. The behavior of %N changed in 1.7.0. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Mailing list status
On Sun, Sep 02, 2018 at 08:09:21PM +0100, Nuno Silva wrote: > On 2018-03-12, Kevin J. McCarthy wrote: > > The new mailing list server uses GNU mailman. There are likely a few > > things that need to be tweeked. Please let me know about any issues. > > The web archive for this list at marc.info[0] stopped being updated > after the mailing list move. Same goes for mutt-dev[1]. Whoops, I didn't notice either. I assumed when I ported the subscriber lists over, marc.info would be included, but looks like I forgot to double-check that. > It seems that there are web archives for mutt-users and mutt-dev at > mutt.org[2,3]. Out of curiosity, why aren't these listed in the mutt > website[4]? It was a bonus I didn't ask for or expect, so I just didn't put it on my list of things to update. However, given the marc.info gap, I'll do so. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: pipe message with folder name
On Mon, Aug 20, 2018 at 06:46:07PM -0700, Kevin J. McCarthy wrote: > On Mon, Aug 20, 2018 at 09:24:40PM -0400, Ben Fitzgerald wrote: > > My idea for solving this would be to save both the Message-ID *and* the > > folder > > the message resides in. Then I could, from emacs: > > You could set an environment variable in Mutt and then access that from > the script. [*] which btw requires 1.8.0 or greater. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: pipe message with folder name
On Mon, Aug 20, 2018 at 09:24:40PM -0400, Ben Fitzgerald wrote: > My idea for solving this would be to save both the Message-ID *and* the folder > the message resides in. Then I could, from emacs: You could set an environment variable in Mutt and then access that from the script. folder-hook . 'set visual=^;setenv MYCURFOLDER $visual' However, the value of $MYCURFOLDER will contain Mutt mailbox shortcuts, such as '='. If you don't want that you'll have to temporarily unset $folder: folder-hook . 'set my_folder=$folder;set folder="XXX";set visual=^' folder-hook . 'setenv MYCURFOLDER $visual' folder-hook . 'set folder=$my_folder' -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: view of threads | display most recent mail date and sender
On Mon, Jul 30, 2018 at 03:18:56PM +0200, Karlo Kuna wrote: > when thread is collapsed displayed sender and date are of the first > message in the thread and not the last. Mutt is displaying the _top_ message in the thread. When you collapse a thread, the message showing is not a representation of the thread, it is the top message itself. An operation on that visible message (viewing, copying, saving) is performed only on the top message, not the entire thread. First/last only make sense in the scope of an order such as date-received, where first could in fact be something other than top. But in this case $sort=thread, and $sort_aux affects the order between threads/subthreads - not the threading algorithm itself. There is no configuration which will make Mutt display a different message besides the top when the thread is collapsed. I belabor this point, because it's important to understand how this differs from, say Gmail, which flattens out threads, provides a representation of the thread in the index, and whose operations on those representations affect the entire thread. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: -z option not working for imap?
On Tue, Jul 17, 2018 at 02:01:48PM -0500, Hokan wrote: > the -z option (quit if no messages) works for local mailboxes, but I > can't get it to work with imap mailboxes. Am I missing something, or > does it just not work with imap? I've never poked in that part of the code before, but I can confirm it is not implemented for IMAP. I'm not sure why, but I'll put it on my list to take a look at. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
mutt 1.10.1 released
Hi Mutt Users, I've just released version 1.10.1. Instructions for downloading can be found at <http://www.mutt.org/download.html>. This is a bug fix release, and includes a few important security fixes. I strongly recommend IMAP and POP users upgrade as soon as possible. This release merits special thanks to a couple security researchers. Jeriko One discovered a host of vulnerabilities in the IMAP and POP code. His bug reports were detailed, and included demonstration code and suggested fixes. Marcus Brinkmann discovered an issue with encrypted email spoofing, and reported the issue to GnuPG and Mutt. There is a new option $pgp_check_gpg_decrypt_status_fd to check for this. If you have any issues, please check your configuration against contrib/gpg.rc. Also, thanks is due to Richard Russon. An unfortunately timed absence left me scrambling to get the fixes in. Richard kindly shared his patches and delayed his release until today, to give me time to prepare the release. Lastly, a big thanks to everyone who helped work on this release! -Kevin signature.asc Description: PGP signature
GnuPG CVE-2018-12020 and Mutt
Hi Mutt Users, GnuPG just released an important security fix involving injection into the status-fd channel. The details are at <https://lists.gnupg.org/pipermail/gnupg-announce/2018q2/000425.html>. If you are using the suggested values in contrib/gpg.rc, it should NOT be necessary to switch to using GPGME (despite what they said in their email). Specifically make sure you have "--no-verbose" in $pgp_decode_command, $pgp_verify_command, and $pgp_decrypt_command. There are a couple other (non-critical) issues Marcus Brinkmann found and reported to Mutt. They are mitigated by the new GnuPG release, and by fixes in Mutt's stable branch. I will release a new stable version in the next couple weeks. -Kevin signature.asc Description: PGP signature
Re: Slowness when coloring the index
On Fri, May 25, 2018 at 04:33:36PM +0200, Ralf Hildebrandt wrote: > That's working OK, but it's quite slow. It seems that mutt is fetching > the whole body (instead of just the headers). Yes, it is. ~h is a very bad idea to use for index coloring. If possible you should use the 'spam' command and '~H' instead <https://muttmua.gitlab.io/mutt/manual-dev.html#spam> You can do the same kind of thing for other headers too: <http://www.8t8.us/blog/2016/07/03/caching-additional-headers-in-mutt.html> -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Mutt and EFAIL
I've received a few questions about EFAIL and whether this release has any related changes, so I hope you'll forgive me for sending a second mutt-announce email today. For those unaware, https://efail.de/ disclosed an attack on OpenPGP and S/MIME emails this past week. The researchers reported mutt-1.7.2 was not successfully attacked. So, the short answer is no, mutt-1.10.0 has no changes made as a result of EFAIL, and the pgp/smime configuration variable changes in this release are unrelated. I am neither a security researcher nor a cryptographer, but here are my current takeaways and suggestions: * If you are using a version of mutt before 1.6.0 and rely on OpenPGP encryption, please upgrade. 1.6.0 introduced $pgp_decryption_okay, which scans the GnuPGP status output for a successful decryption code. * Please make sure you update your config to the values suggested in contrib/gpg.rc (again, in particular $pgp_decryption_okay). * Opening a decrypted email in an external browser should be considered unsafe. Part of the attack was due to HTML injection. * I don't believe autoviewing dumped HTML via lynx, elinks, etc is an issue. However, the researchers did not specifically test that. -Kevin signature.asc Description: PGP signature
mutt 1.10.0 released
Hi Mutt Users, I'm pleased to announce the release of version 1.10.0. Instructions for downloading are at <http://www.mutt.org/download.html>. This release has several new features, a few performance improvements, and of course bug fixes. Please see the UPDATING file or the release notes at <http://www.mutt.org/relnotes/1.10/>. Thanks to everyone for helping keep Mutt development and releases going. This cycle (since 1.9), a chunk of my time was spent migrating to git, gitlab, and other new infrastructure. So I'm especially grateful to everyone who helped with patches, tickets, testing, and even offering their computer for debugging! -Kevin signature.asc Description: PGP signature
Re: A mutt mailcap problem
On Fri, May 18, 2018 at 07:53:05PM +0200, mimosinnet wrote: > text/html; xdg-open %s &; test=test -n "$DISPLAY"; needsterminal; > > I wonder if some setting in chromium/chrome has been changed. Does adding "nametemplate=%s.html" to the mailcap entry help? -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: 怎么从mutt-users@mutt.org里把自己的邮箱删掉？
On Thu, May 17, 2018 at 09:36:46AM +0800, xiaoxiao198502 wrote: > 怎么从mutt-users@mutt.org里把自己的邮箱删掉？ mailto:mutt-users-requ...@mutt.org?subject=unsubscribe -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Option to disable S/MIME signature check?
On Tue, May 15, 2018 at 03:27:15PM -0400, Todd Zullinger wrote: > Kevin J. McCarthy wrote: > > On Tue, May 15, 2018 at 09:40:38AM +0200, W. Martin Borgert wrote: > >> Is there an option in mutt to do this? Hopefully a run time > >> option, not a compile time option... > > > > The compile-time configuration is the cleanest way to turn it off. > > However, you could try set smime_verify_command="" (along with > > smime_verify_opaque_command and smime_decrypt_command). > > Out of curiosity, is it correct that --disable-smime only > applies when building without gpgme? It looks like with > --enable-gpgme, smime will be available via gpgme? Yes, if you turn on gpgme it will be available through that. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Option to disable S/MIME signature check?
On Tue, May 15, 2018 at 09:40:38AM +0200, W. Martin Borgert wrote: > Is there an option in mutt to do this? Hopefully a run time > option, not a compile time option... The compile-time configuration is the cleanest way to turn it off. However, you could try set smime_verify_command="" (along with smime_verify_opaque_command and smime_decrypt_command). Alternatively, you could set crypt_verify_sig=ask-yes, but that affects both PGP and S/MIME. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: A mutt mailcap problem
On Sat, May 12, 2018 at 11:15:26AM +1000, Brian Salter-Duke wrote: > I select the attachments with 'v', move the cursor down to the > quoted-printable text/html line and hit enter. Now using Mutt 1.8.0 > that menu does not come up. Instead of hitting enter, try typing m . -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)
On Mon, Apr 30, 2018 at 05:27:26PM +1000, Erik Christiansen wrote: > Here, declares: "Mutt also supports the Mail-Followup-To header. > When you send a message to a list of recipients which includes one or > several subscribed mailing lists, and if the $followup_to option is set, > Mutt will generate a Mail-Followup-To header which contains all the > recipients to whom you send this message, but not your address." The key word above is "subscribed". And this is what distinguishes the "subscribe" command from the "lists" command. The documentation for $followup_to further elaborates: The header will contain only the list's address for subscribed lists, and both the list address and your own email address for unsubscribed lists. So, using the "subscribe" command will generate only the list address in the MFT header. Using the "lists" command will generate both the list address and your own email address. The fact that this has tripped up at least a couple long-time users means the documentation is not clear enough about this. I'll add something to the "Handling Mailing Lists" section to help clarify this. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)
On Thu, Apr 26, 2018 at 08:50:35PM +, Mihai Lazarescu wrote: > > > On April 26, 2018 8:24:16 PM UTC, Ian Zimmerman wrote: > > On 2018-04-25 10:24, Will Yardley wrote: > > > > > Kind of thread drift, but I actually wonder if Mutt shouldn't move > > > away from Mail-Followup-To, as it never became a standard, and is > > not > > > really adopted by (m)any other commonly used mail clients. > > > > It is supported by Gnus. I don't know of any others, and I wonder the > > same thing, because it seems to create at least some mischief. > > Seems also supported by Thunderbird > https://wiki.mozilla.org/Thunderbird:Help_Documentation:Mail-Followup-To_and_Mail-Reply-To > and Roundcube https://github.com/roundcube/roundcubemail/issues/1937 I always thought $followup_to was a pretty nice feature. While I sympathize with Matthias, the mischief was the result of misconfiguration, and Mutt requires nothing if not attention to the documentation and configuration. However, if there is a strong majority of mutt-users subscribers that agree with $followup_to defaulting to 'no', I'll make the change. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)
On Fri, Apr 27, 2018 at 07:48:40AM -0700, Ian Zimmerman wrote: > On 2018-04-27 06:33, Matthias Apitz wrote: > > > Hmm, someone set Reply-To in the headers of your mail too. > > That was the list manager, and that's what I call munging. I don't believe so. I have reply_goes_to_list set to 'Poster', which is not supposed to add (or remove) any such header. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)
On Wed, Apr 25, 2018 at 07:31:20PM +0200, Matthias Apitz wrote: > El día Wednesday, April 25, 2018 a las 10:24:45AM -0700, Will Yardley > escribió: > > > On Wed, Apr 25, 2018 at 09:28:02AM -0700, Kevin J. McCarthy wrote: > > > On Wed, Apr 25, 2018 at 05:56:43PM +0200, Matthias Apitz wrote: > > > > On Wednesday, 25 April 2018 17:17:54 CEST, Patrick Shanahan > > > > > which he did and does regularily: > > > > > "Mail-Followup-To: Matthias Apitz , > > > > > mutt-users@mutt.org" > > > > > > > > I do not set this in my mutt. > > > > > > Try adding mutt-users to your 'subscribe' lists, instead of 'lists'. ^ ^ ^ For mailing lists that you are subscribed to, you should use the 'subscribe' command, not the 'lists' command. > $ grep mutt-users ~/.muttrc > send-hook mutt-users@mutt.org 'my_hdr From: Matthias Apitz > ' > send-hook mutt-users@mutt.org 'my_hdr Reply-To: Matthias > Apitz ' > lists asterisk-us...@lists.digium.com biblio-progresis...@yahoogrupos.com.mx > b...@berklix.org commun...@lists.openmoko.org digikam-us...@kde.org > ekiga-devel-l...@gnome.org ekiga-l...@gnome.org > enlightenment-us...@lists.sourceforge.net > fgcuba-muc-inter...@listen.einewelthaus.de freebsd-...@freebsd.org > freebsd-curr...@freebsd.org freebsd-hack...@freebsd.org > freebsd-i...@freebsd.org freebsd-j...@freebsd.org freebsd-mob...@freebsd.org > freebsd-multime...@freebsd.org freebsd-...@freebsd.org > freebsd-po...@freebsd.org freebsd-questi...@freebsd.org > freebsd-...@freebsd.org free...@es.freebsd.org gnomemeeting-l...@gnome.org > gphoto-u...@lists.sourceforge.net gpsd-us...@lists.berlios.de > kde-free...@freebsd.kde.org kde-free...@kde.org l-chix...@glove.org.ve > linu...@listas.softwarelibre.cu evolution-l...@gnome.org > local-openmoko-sp...@projects.openmoko.org mplayer-us...@mplayerhq.hu > mutt-users@mutt.org openmoko-ker...@lists.openmoko.org > ubuntu-ph...@lists.launchpad.net betatesters-m10_ubu...@bq.com > chromium-os-disc...@chromium.org x...@freebsd.org gnupg-us...@gnupg.org Try changing the above line to use the 'subscribe' command (or at least move mutt-users@mutt.org to a separate 'subscribe' command if you aren't subscribed to all of those). Otherwise Mutt is interpreting it as a mailing list, but not one that you are subscribed too, and is adding your address in the Mail-Followup-To header. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: breaking long header lines into 2 (or more) lines
On Wed, Apr 25, 2018 at 05:56:43PM +0200, Matthias Apitz wrote: > On Wednesday, 25 April 2018 17:17:54 CEST, Patrick Shanahan > > which he did and does regularily: > > "Mail-Followup-To: Matthias Apitz , > > mutt-users@mutt.org" > > I do not set this in my mutt. Try adding mutt-users to your 'subscribe' lists, instead of 'lists'. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
mutt 1.9.5 released
Hi Mutt Users, I'm pleased to announce the release of version 1.9.5. Instructions for downloading can be found at http://www.mutt.org/download.html. This is a bug fix release. Fixes include: * GPGME S/MIME non-detached signature handling. * A compilation issue with ncurses-6.1 when tinfow is split out. Hopefully the fix doesn't impact anyone: please let me know of any issues. * Regular expression crashes and weird behavior problems on MacOS (and possibly other BSDs). This was most noticeable with the recent Xcode 9.3 release, but the issue has existed for a while. * GSSAPI authentication issues, which may have affected Exchange users. We've changed behavior to match the RFC. If you are negatively impacted by this, please let me know. All of these issues were fixed because of people taking the time to report, help me debug, or even sending in a patch. You have my great thanks. -Kevin signature.asc Description: PGP signature
Re: mutt.org web
On Fri, Apr 06, 2018 at 09:47:23AM -0500, Hokan wrote: > http://mutt.org/ looks fine to me. On the other hand, > http://www.mutt.org/ shows the page you described. Thanks for the heads-up. I've notified OSUOSL about the issue - there must be a slight misconfiguration in their virtual hosting. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Sidebar closes after save and delete
On Thu, Mar 22, 2018 at 06:07:59PM -0700, Rem Roberti wrote: > please remove this email from the feed - rem is deceased I've just unsubscribed the address for them. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Sidebar closes after save and delete
On Tue, Mar 20, 2018 at 10:38:49AM +, David Woodfall wrote: > I've noticed since I've been using the sidebar that it closes when > deleting or saving a message in index and pager. > > I managed to fix the delete problem by changing the macro to: > > s=Trash":set sidebar_visible" > > But this doesn't work with for some reason. It looks > like something is closing it after my macro has finished. Check to see if you've bound something to that is inadvertently triggering. My guess is something in one of your macros is leaving that keybinding in the input buffer. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: GPGME error
On Thu, Mar 15, 2018 at 10:03:22AM +, Darac Marjal wrote: > I managed to see it read "[setting sender] mailbox ...". That was > enough for me to find the function "void mutt_gpgme_set_sender()". > > I can see that this function sets the sender for gpgme (presumably so it > knows who to sign as), but my question is why is the message "[setting > sender] mailbox: %s" displayed using mutt_error()? Hi Darac, Thanks for the report. As you guessed, it shouldn't be using mutt_error() here. I don't think the message has much utility, given how quickly it flies by, so I will change it to use a debug statement instead. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: what does the leading - mean in the attachment view?
On Wed, Mar 14, 2018 at 01:29:41PM +0800, Yubin Ruan wrote: > Just out of curious: in the attachment view (of the compose view), there are > some attachments with a - before them: > > --- > - I1 /path/to/file1 [text/plain, 7 bit, us-ascii, 13] > - A1 /path/to/file2 [text/plain, 7 bit, us-ascii, 13] > > what does that - mean? It's the %u in $attach_format. It will show '-' if the attachment will be unlinked after sending. This is usually the case for tempfiles. If you invoke 'G' , it converts an attachment to a tempfile and sets the unlink flag. 'u' toggles the state of the flag. Use with extreme caution on non-tempfiles. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Mailing list status
On Tue, Mar 13, 2018 at 02:39:47PM -0700, Kevin J. McCarthy wrote: > OSUOSL is making some adjustments to the lists right now (to fix the > errant http://mutt.org/mailman) links. I think they have accidentally > goofed up the list ids and headers in the process. I've let them know > about the problem - sorry for the confusion. Replying to myself to check the headers. Please pardon the noise. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Is it possible to redraw screen after doing a charset change?
On Tue, Mar 13, 2018 at 02:20:19PM +, David Woodfall wrote: > I have a couple of binds to change charset between UTF-8/ISO-8859-1. > The problem is that I need to exit from the pager and then reopen the > message to see the changes, so I added those commands to the macro, > which works fine. > > However, this doesn't work in the index, so is there a way to redraw > the screen after a charset change? I don't see anything in the manual > about it. I think the mailbox may need to be reopened for mutt to reprocess the headers, because they are stored in memory. In version 1.8.0 and higher, the function can be used to save your place, and the value in $mark_macro_prefix to restore it: macro index ,r "a^'a" -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Mailing list status
On Mon, Mar 12, 2018 at 10:01:08PM +, Nuno Silva wrote: > It looks like the "nomail" subscription setting was lost in this > transition. > > I have been subscribed that way for some time and today, for the first > time ever, I received a few emails from this mailing list. Sorry about that. Yes, the 'nomail' and 'digest' options were lost, and I have no way to retrieve them. I'll have to ask for your forgiveness and request you manually re-enable those settings for your account. Subscription settings can be edited at: https://lists.osuosl.org/mailman/listinfo/mutt-users Note, however, that the website and mailman are not integrated yet. Some of the mailman links in emails point to <http://mutt.org/mailman...> prefixes which currently don't work. Please use the above osuosl.org URL for now. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Mailing list status
Hi Everyone, Last Friday night, our mailing list and website server suffered a catastrophic failure. Fortunately, for the past couple months I have already been working on moving our mailing lists to OSUOSL. I had planned a couple more steps to transition smoothly, but given the failure have accelerated things. The new mailing list server uses GNU mailman. There are likely a few things that need to be tweeked. Please let me know about any issues. It is likely that emails sent to the list since Friday night will not make it through, and will need to be resent. Sorry for the inconvenience. Please let me offer a huge thank you to GBNet for donating their time and servers to Mutt for many, many years, and also express my appreciation to OSUOSL for working with me to transition to their hosting services. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature -- Mutt-users mailing list Mutt-users@mutt.org http://mutt.org/mailman/listinfo/mutt-users
mutt 1.9.4 released
Hi Mutt Users, I've just released version 1.9.4, available at ftp.mutt.org/pub/mutt/ via FTP or HTTP access. Due to technical reasons, I'm currently unable to edit our website, but will update the download page as soon as I can. Please feel encouraged to verify the signature of the release files with my key. This version fixes a couple of possible large value issues; one for year numbers and another for mbox message content-length. Thanks to Joseph Bisch for reporting these issues. Also, this version restores the flea and muttbug scripts, with stub versions pointing to gitlab. We've finished migrating to gitlab, and have turned off our trac instance. Thanks to everyone who reported issues, sent patches, and helped with this release. -Kevin signature.asc Description: PGP signature
Re: Remove Subject prefixing (when answering/forwarding) possible?
On Wed, Feb 28, 2018 at 07:05:19PM +0100, Matthias Apitz wrote: > El día Wednesday, February 28, 2018 a las 10:00:29AM -0800, Kevin J. McCarthy > escribió: > > > Looks like the example might be wrong in the manual, unless there are > > regexp library differences. Because ']' is first in the character > > class (after the negation), it shouldn't need to be escaped. This works > > for me: > > subjectrx '\[[^]]*\]:? *' '%L%R' > > > > If that works for you all, I'll fix up the manual example. > > The man page for muttrc should be checked/fixed to. On 1.8.0 I saw no > hint about 'subjectrx'. Thanks Matthias, I'll fix that up. Also, my apologies Christian for obliviously repeating what you had already pointed out as the problem. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Remove Subject prefixing (when answering/forwarding) possible?
On Wed, Feb 28, 2018 at 09:28:41AM -0700, Akkana Peck wrote: > Todd Zullinger writes: > > http://www.mutt.org/doc/manual/#display-munging > > > > subjectrx was added in 1.8.0, it seems. > > That's wonderful! Something I've been wishing for for a long time. > > But the example in the manual doesn't work for me in 1.9.3 > (on Debian testing, but I think that's back to being normal mutt, > not neomutt, right?). This line in muttrc: > subjectrx '\[[^\]]*\]? *' '%L%R' Looks like the example might be wrong in the manual, unless there are regexp library differences. Because ']' is first in the character class (after the negation), it shouldn't need to be escaped. This works for me: subjectrx '\[[^]]*\]:? *' '%L%R' If that works for you all, I'll fix up the manual example. Thanks! -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Mutt compiled with SASL suddenly not working
On Sat, Feb 24, 2018 at 09:12:25AM -0600, Russ Urquhart wrote: > I’ve been using mutt for sometime now (1.5.23). Compiled with SASL it > has worked with out issue. Are you still using 1.5.23? It might be worth trying the most recent version. There have been a couple fixes to SASL in the 1.7 and 1.8 releases that might (or might not) affect you. > Here are some specifics from my muttrc file: > > set > smtp_authenticators="external:anonymous:plain:otp:skey:digest-md5:scram:ntlm:gssapi:browserid-aes128:eap-aes128” Is there any particular reason for this list, and the order it occurs in? For example, you are listing "external" first, which is not an ordinary authentication mechanism. This is followed by "anonymous", which doesn't seem to be a likely method you'd want to use. "otp" also seems highly unlikely... If this is "always the way it's been", you might want to try commenting that line out and seeing if it just works. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
mutt 1.9.3 released
Hi Mutt Users, I've just released version 1.9.3. Instructions for downloading can be found at http://www.mutt.org/download.html. This is a bug fix release, fixing a problem with large IMAP UIDs and with resuming S/MIME encrypted drafts. Additionally, the flea (muttbug) program has been removed from this release. We have migrated over to gitlab for code hosting and issues, and encourage everyone to report issues at https://gitlab.com/muttmua/mutt/issues instead. Thanks to everyone who reported issues, sent patches, and helped test! -Kevin signature.asc Description: PGP signature
Re: Mapping macros in other minor modes
On Wed, Dec 27, 2017 at 01:06:25PM -0600, Tim Chase wrote: > Is there a way to remap keys in the ":" command-line and in the help > viewer? The command line uses the "editor" map, while the help uses the "pager" map. To change the editor map, you could use bind editor \Cp history-up bind editor \Cn history-down For the help, you could put bind pager k previous-line bind pager j next-line -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: why :command does not work
On Mon, Dec 18, 2017 at 09:09:49PM +0800, Yubin Ruan wrote: > Yes. Many thanks! Are there any other options other than :exec? I mean, any > other options after a : , such as :look-for-some-command ... Other commands are listed at https://dev.mutt.org/doc/manual.html#commands is a function; others are described at https://dev.mutt.org/doc/manual.html#functions Functions are typically executed via key-bindings, but can also be run via the push or exec command (or using hooks, macros, etc). -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
mutt 1.9.2 released
Hi Mutt Users, I've just released version 1.9.2. Instructions for downloading the release are at http://www.mutt.org/download.html. This is a bug fix release, fixing a problem with S/MIME encryption that could end up removing the recipient certificate from the store. On a side note, the Mutt team is starting to transition our infrastructure. We are now using Git, and our source code repository can be found at https://gitlab.com/muttmua/mutt. Thanks to everyone who submitted patches, reported bugs, and helped test. -Kevin signature.asc Description: PGP signature
Re: Trash Folder Creation
On Tue, Dec 05, 2017 at 02:06:55PM -0600, Hokan wrote: > Is this new behaviour a bug? If not, how can I automate creation of the > monthly trash folder? It sounds like a bug. The trash folder has gone through a few changes after being integrated into mutt. It is still supposed to prompt for creation if the mailbox doesn't exist, and does so in my testing, but sounds like something is not working for you. If possible, please capture a debug log at level 3, and open a ticket. I'll try to take a closer look. Thank you! -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Mutt - Neomutt and Debian Stretch
[Apologies if this turns out to be a dup. The email I sent yesterday appears to have been eaten by a grue.] On Thu, Aug 03, 2017 at 05:21:54PM -0700, Kevin J. McCarthy wrote: > On Thu, Aug 03, 2017 at 10:24:37PM +, Antonio Radici wrote: > > On Wed, Jul 26, 2017 at 09:44:29AM -0700, Kevin J. McCarthy wrote: > > > On Sat, Jul 01, 2017 at 08:17:02AM +, Antonio Radici wrote: > > > > From your statement above I understand your point clearly, I think a > > > > solution > > > > can be found and Debian tooling provides various alternatives, I will > > > > discuss > > > > the various options with a couple of people more expert than me on > > > > Debian > > > > packaging and I will come back to you, this can take up to 2 weeks in > > > > the worst > > > > case. > > > > > > Have you had a chance to do this yet? > > > > Yes, and this is why you haven't seen new releases to the Debian package > > (despite we had new releases in Neomutt). This is going to be fixed in > > August, I > > replied on the bug that you opened. > > Thank you for the update Antonio. I appreciate your work on resolving > this issue. This afternoon, Antonio uploaded the mutt-1.9.1 tarball as the Debian unstable mutt package, resolving the ticket I submitted. I'm sure this change will not be without controversy, but I just wanted to say thank you to Antonio for doing this. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: layout hack: blank 2nd line
On Sun, Oct 08, 2017 at 07:11:05PM +0800, Kevin J. McCarthy wrote:
> You could try the following patch. Unfortunately, it will affect other
> screens besides the index. I can't remember off the top of my head if
> any places make assumptions that the status has one row, but a very
> quick check seemed to be okay.
Sorry, that wasn't quite right. The help and message windows get
affected, so their rows needs to be reset. Hopefully this version is
something closer to working.
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
# HG changeset patch
# User Kevin McCarthy
# Date 1507462637 -28800
# Sun Oct 08 19:37:17 2017 +0800
# Node ID 6ce7a3f576b96df6f4a67f4d69b5247ae45968a9
# Parent ba4a3cb944c59ca53adfc3f99cf67dc2c22d7b6a
[mq]: hack
diff --git a/curs_lib.c b/curs_lib.c
--- a/curs_lib.c
+++ b/curs_lib.c
@@ -570,28 +570,32 @@
void mutt_reflow_windows (void)
{
if (option (OPTNOCURSES))
return;
dprint (2, (debugfile, "In mutt_reflow_windows\n"));
- MuttStatusWindow->rows = 1;
+ MuttStatusWindow->rows = 2;
MuttStatusWindow->cols = COLS;
MuttStatusWindow->row_offset = option (OPTSTATUSONTOP) ? 0 : LINES - 2;
MuttStatusWindow->col_offset = 0;
memcpy (MuttHelpWindow, MuttStatusWindow, sizeof (mutt_window_t));
if (! option (OPTHELP))
MuttHelpWindow->rows = 0;
else
+ {
+MuttHelpWindow->rows = 1;
MuttHelpWindow->row_offset = option (OPTSTATUSONTOP) ? LINES - 2 : 0;
+ }
memcpy (MuttMessageWindow, MuttStatusWindow, sizeof (mutt_window_t));
+ MuttMessageWindow->rows = 1;
MuttMessageWindow->row_offset = LINES - 1;
memcpy (MuttIndexWindow, MuttStatusWindow, sizeof (mutt_window_t));
MuttIndexWindow->rows = MAX(LINES - MuttStatusWindow->rows -
MuttHelpWindow->rows - MuttMessageWindow->rows, 0);
MuttIndexWindow->row_offset = option (OPTSTATUSONTOP) ? MuttStatusWindow->rows :
MuttHelpWindow->rows;
signature.asc
Description: PGP signature
Re: layout hack: blank 2nd line
On Fri, Oct 06, 2017 at 04:41:34AM -0700, Claus Assmann wrote:
> I hacked an old mutt version to have a blank line between
> the status (on top) and the list of mails, e.g., it looks
> like this:
>
> Mbox: =admin (-) [[rest of status line]]
>
> 214 2016 Mar 01 Charlie Root( 33) esmtp.org daily insecurity output
> 215 2016 Mar 01 Cron Daemon ( 21) Cron mailq
>
>
> How to get that blank line between the status and the rest in new
> mutt versions? My hack doesn't apply anymore when the code was
> changed for the sidebar stuff :-(
>
> Is there an option/trick or does it require a source code change?
> In the latter case: does someone have a patch? I tried but so
> far failed to hack the new code :-(
You could try the following patch. Unfortunately, it will affect other
screens besides the index. I can't remember off the top of my head if
any places make assumptions that the status has one row, but a very
quick check seemed to be okay.
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
# HG changeset patch
# User Kevin McCarthy
# Date 1507460859 -28800
# Sun Oct 08 19:07:39 2017 +0800
# Node ID 57c3a7afe0cf478f298fe28e9ef1d2f4085cbd9a
# Parent ba4a3cb944c59ca53adfc3f99cf67dc2c22d7b6a
[mq]: hack
diff --git a/curs_lib.c b/curs_lib.c
--- a/curs_lib.c
+++ b/curs_lib.c
@@ -570,17 +570,17 @@
void mutt_reflow_windows (void)
{
if (option (OPTNOCURSES))
return;
dprint (2, (debugfile, "In mutt_reflow_windows\n"));
- MuttStatusWindow->rows = 1;
+ MuttStatusWindow->rows = 2;
MuttStatusWindow->cols = COLS;
MuttStatusWindow->row_offset = option (OPTSTATUSONTOP) ? 0 : LINES - 2;
MuttStatusWindow->col_offset = 0;
memcpy (MuttHelpWindow, MuttStatusWindow, sizeof (mutt_window_t));
if (! option (OPTHELP))
MuttHelpWindow->rows = 0;
else
signature.asc
Description: PGP signature
Re: tls_socket_read problem
On Fri, Sep 15, 2017 at 06:12:01PM +0800, Yubin Ruan wrote: > I am currently backing mutt with a sock5 proxy (using proxychain). But when I > leave my computer for a while, not touch anything, there would be error: > tls_socket_read (The TLS connection was non-properly terminated.) > > and I have to pick up the connection again. > > So, is there any option for long/permenant connection? You could try decreasing $imap_keepalive. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
mutt 1.9.0 released
Hi Mutt Users, I'm pleased to announce the release of version 1.9.0. Instructions for downloading are at http://www.mutt.org/download.html. The release is signed with my gpg key, and I always recommend you take the time to verify the signature. This release has several new features, which are the result of some large internal changes. More information can be found in the UPDATING file[1] or the (new!) release notes page[2]. Thank you to everyone who helped with this release. Your testing, bug reports, patches, translation, and encouragement are what make these happen. -Kevin [1] http://www.mutt.org/doc/UPDATING [2] http://www.mutt.org/relnotes/1.9/ signature.asc Description: PGP signature
Re: After change-folder listing the attachments folder does not work
On Fri, Sep 01, 2017 at 07:51:54AM +0200, Kai Weber wrote: > BTW, with either NeoMutt or Mutt 1.8.3 I get > >Error in /home/kai/.config/mutt/muttrc, line 13: header_cache:unknown > variable >source: errors in /home/kai/.config/mutt/muttrc By default, Mutt has a minimal configuration. I would recommend first running: apt-get build-dep mutt How you configure is a personal opinion, but here are some options you may want to pass to configure: ./configure \ --prefix=/usr/local \ --with-mailpath=/var/mail \ --enable-debug \ --enable-fcntl \ --enable-hcache \ --enable-gpgme \ --enable-imap \ --enable-smtp \ --enable-pop\ --enable-sidebar\ --enable-compressed \ --with-curses \ --with-gnutls \ --with-gss \ --with-idn \ --with-mixmaster\ --with-sasl \ --without-gdbm \ --without-bdb \ --without-qdbm I like the newer kyotocabinet header cache, so I also would install the libkyotocabinet-dev package and add to configure: --without-tokyocabinet \ --with-kyotocabinet -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: After change-folder listing the attachments folder does not work
On Thu, Aug 31, 2017 at 11:31:13PM +0200, Kai Weber wrote: > On 08-31-17, Kevin J. McCarthy wrote: > > > In an off-list reply, Kai mentioned he's running the Debian neomutt > > package. > > Which was a mistake... Yes, sorry I meant that as an explanation of why I was asking you to try the mutt-1.8.3 tarball, not as an accusation. > > Kai, would you be willing to try compiling the mutt-1.8.3 tarball or > > mercurial tip and see if the bug is present there? > > Mutt 1.8.3 tarball works. > NeoMutt Github master works > Debian NeoMutt/Mutt package NeoMutt 20170609 (1.8.3) does not work > > So, I have to file a bug against the Debian package? It sounds like a good idea. However, there is currently a freeze in the Debian mutt package, until Debian bug #870635 is resolved. You may want to wait until their next upload and see what happens. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: After change-folder listing the attachments folder does not work
On Thu, Aug 31, 2017 at 10:34:26PM +0200, Kai Weber wrote: > On 08-31-17, Ian Zimmerman wrote: > > > I strongly suspect this is related to the following discussion: > > > > https://github.com/neomutt/neomutt/issues/609 > > > > You could try neomutt, where my proposed patch has been integrated. > > I just build the Github master and it works. In an off-list reply, Kai mentioned he's running the Debian neomutt package. Kai, would you be willing to try compiling the mutt-1.8.3 tarball or mercurial tip and see if the bug is present there? -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: After change-folder listing the attachments folder does not work
On Thu, Aug 31, 2017 at 01:18:40PM -0700, Ian Zimmerman wrote: > On 2017-08-31 12:49, Kevin J. McCarthy wrote: > > > I understand it was probably easy to forget, while in the midst of > > dissing the "ultra-conservative" mutt devs and community, that I fixed > > your patch and at least gave it serious consideration. > > The real reason it was easy to forget was the time that had passed. But > you're right, I should have attributed you despite that. I'm flawed > like everyone. Okay, fair enough. I admit I'm being a bit of an ass. For that I also apologize. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: After change-folder listing the attachments folder does not work
On Thu, Aug 31, 2017 at 12:07:41PM -0700, Ian Zimmerman wrote: > On 2017-08-31 10:56, Kevin J. McCarthy wrote: > > > > I strongly suspect this is related to the following discussion: > > > > > > https://github.com/neomutt/neomutt/issues/609 > > > > Look like "your" patch contained my fixes, posted in > > <20150608225607.gd8...@zaogao.lan> on mutt-dev. Thanks for the (lack > > of) attribution. Very classy. > > I apologize. > > Let's change it to "my proposal". That OK with you? I don't really care what you call it on this mailing list; the attribution was deserved in the commit. I understand it was probably easy to forget, while in the midst of dissing the "ultra-conservative" mutt devs and community, that I fixed your patch and at least gave it serious consideration. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: After change-folder listing the attachments folder does not work
On Thu, Aug 31, 2017 at 09:07:08AM -0700, Ian Zimmerman wrote: > On 2017-08-31 09:16, Kai Weber wrote: > > > I have a quite common multi account setup with multiple folders for my > > account. I use folder-hooks to switch various settings based on the > > folder I change into. > > > > I have some macros to go directly to one folder: > > > >macro index ,i "=personal/INBOX" > > > > If I use this macro to go to a folder, when composing a mail adding > > attachments does not work as expected: > > I strongly suspect this is related to the following discussion: > > https://github.com/neomutt/neomutt/issues/609 Look like "your" patch contained my fixes, posted in <20150608225607.gd8...@zaogao.lan> on mutt-dev. Thanks for the (lack of) attribution. Very classy. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: After change-folder listing the attachments folder does not work
On Thu, Aug 31, 2017 at 09:16:46AM +0200, Kai Weber wrote:
> I have a quite common multi account setup with multiple folders for my
> account. I use folder-hooks to switch various settings based on the folder I
> change into.
>
> I have some macros to go directly to one folder:
>
>macro index ,i "=personal/INBOX"
>
> If I use this macro to go to a folder, when composing a mail adding
> attachments does not work as expected:
>
> 1. Use the macro to go into a folder
> 2. Start composing a mail
> 3. try to add attachments by pressing "a"
> 4. If it says Attach file ('?' for list): press "?"
> 5. Error message is: No such file or directory =personal
>
> It seems, does also change to the directory =personal while
> switching folders by browsing through the mailbox list does not change the
> directory and stays in my $HOME directory.
Browsing folders using '?' does change some state: it records the most
recent directory so the next browsing starts in the same place. Just
entering the folder name and hitting enter doesn't do that.
I'll have to dig in a bit to see the problem, but some repeatable
instructions would help. Does this happen if you start mutt, hit ",i",
and then compose a message.
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
Re: mutt 1.5.23 && openssl 1.1.0d
On Sat, Aug 26, 2017 at 10:24:59PM +0200, Matthias Apitz wrote: > El día sábado, agosto 26, 2017 a las 01:02:02p. m. -0700, Kevin J. McCarthy > escribió: > > I've take a look at releases going pretty far back, and they all seem to > > leave @LIBTOOL@ unsubstituted. I'm not sure that mutt makes use of > > libtool when building libintl.a for the --with-included-gettext > > configure option. > > > > I couldn't view the URL you posted due to a permission error. Is this > > interfering with your build? > > Sorry for the perm error of the above link. Is now fixed and world wide > readable. Looks like everything went okay except for the documentation. That can be turned off with --disable-doc if you like. I looked a bit more, and the LIBTOOL shouldn't be used. It's not enabled in the MUTT_AM_GNU_GETTEXT invocation in configure.ac, so it should be fine. The intl/Makefile.in is pulled from gettext, I believe, so has extra stuff in it that we don't use. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: mutt 1.5.23 && openssl 1.1.0d
On Sat, Aug 26, 2017 at 10:23:21AM -0700, Kevin J. McCarthy wrote: > On Sat, Aug 26, 2017 at 11:48:41AM +0200, Matthias Apitz wrote: > > I used 1.8.3 and there is a small problem in the congigure engine: In > > mutt-1.8.3/intl/Makefile the @LIBTOOL@ is not replaced by something > > excuteable: > > > > grep '^LIBTOOL' /home/guru/head/sisis-pap/src/mutt/mutt-1.8.3/*/Makefile > > /home/guru/head/sisis-pap/src/mutt/mutt-1.8.3/intl/Makefile:LIBTOOL = > > @LIBTOOL@ > > > > full log is here: http://www.unixarea.de/mutt.log > > Thanks Matthias. Probably some bit rot. I'll take a look. I've take a look at releases going pretty far back, and they all seem to leave @LIBTOOL@ unsubstituted. I'm not sure that mutt makes use of libtool when building libintl.a for the --with-included-gettext configure option. I couldn't view the URL you posted due to a permission error. Is this interfering with your build? -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: mutt 1.5.23 && openssl 1.1.0d
On Sat, Aug 26, 2017 at 11:48:41AM +0200, Matthias Apitz wrote: > I used 1.8.3 and there is a small problem in the congigure engine: In > mutt-1.8.3/intl/Makefile the @LIBTOOL@ is not replaced by something > excuteable: > > grep '^LIBTOOL' /home/guru/head/sisis-pap/src/mutt/mutt-1.8.3/*/Makefile > /home/guru/head/sisis-pap/src/mutt/mutt-1.8.3/intl/Makefile:LIBTOOL = > @LIBTOOL@ > > full log is here: http://www.unixarea.de/mutt.log Thanks Matthias. Probably some bit rot. I'll take a look. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: mutt 1.5.23 && openssl 1.1.0d
On Thu, Aug 24, 2017 at 06:12:43PM +0200, Matthias Apitz wrote: > We compile the above combination and I learned that some ssl calls in mutt > are outdated/wrong, see below. Is this fixed in a more recent version of > mutt? Thx Yes, this should be fixed for mutt 1.7.2 and later. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: crash if regcomp failed
On Sun, Aug 06, 2017 at 10:11:44PM +0800, JiaZhouyang wrote: > I'm new to Mutt, I analyzed the source code and found a potential bug that > may cause crash. > > In mutt-1.8.3/pager.c:1737:4, if "regcomp” failed, "regexec" would cause a > crash since "SearchRE" is null. > > I think it's unsafe to assume that the library function would be correct. It > would be better if we could handle the error properly. > > Attached please find the patch against version mutt-1.8.3. Hopefully, it can > solve this potential bug. Thank you for the patch Zhouyang! In the future, please send patches like this to the mutt-dev mailing list instead. I will apply and push your patch up later today. -Kevin -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Mutt - Neomutt and Debian Stretch
On Thu, Aug 03, 2017 at 10:24:37PM +, Antonio Radici wrote: > On Wed, Jul 26, 2017 at 09:44:29AM -0700, Kevin J. McCarthy wrote: > > On Sat, Jul 01, 2017 at 08:17:02AM +, Antonio Radici wrote: > > > From your statement above I understand your point clearly, I think a > > > solution > > > can be found and Debian tooling provides various alternatives, I will > > > discuss > > > the various options with a couple of people more expert than me on Debian > > > packaging and I will come back to you, this can take up to 2 weeks in the > > > worst > > > case. > > > > Have you had a chance to do this yet? > > Yes, and this is why you haven't seen new releases to the Debian package > (despite we had new releases in Neomutt). This is going to be fixed in > August, I > replied on the bug that you opened. Thank you for the update Antonio. I appreciate your work on resolving this issue. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Mutt - Neomutt and Debian Stretch
On Wed, Jul 26, 2017 at 09:44:29AM -0700, Kevin J. McCarthy wrote: > So please submit your proposal, and I do expect something soon, but > don't expect my cooperation unless you are willing to ship something > _much_, _much_ closer to my upstream tarball. As an update, I have filed bug 870635 in the Debian bug tracker. <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870635> -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Mutt - Neomutt and Debian Stretch
On Sat, Jul 01, 2017 at 08:17:02AM +, Antonio Radici wrote: > From your statement above I understand your point clearly, I think a solution > can be found and Debian tooling provides various alternatives, I will discuss > the various options with a couple of people more expert than me on Debian > packaging and I will come back to you, this can take up to 2 weeks in the > worst > case. Have you had a chance to do this yet? > Iwould say let's proceed as follow: > > * I will investigate the possible options and I will come back to both you > and > Richard with one or more proposals for the future of the package in > Debian. > > * I know your views and I will try my best to make sure that they are > satisfied in the proposals. My understanding is that the original mutt > targz + extra feature would be OK for you as long as those features are > cleanly split in patches Yes, this would technically satisfy the problem, but... > * You let me know whether code formatting changes can be included (in one > way > or another), or whether there is a future for inclusion for those changes, > this will greatly reduce the diff between the packages. I haven't replied to this, because every time I thought about it, the answer was "no". So it seemed a better idea to wait and see how things went. It's been a few weeks, and my viewpoint hasn't changed. I don't see what I possibly have to gain by cooperating on this. All it would do is make it easier for you to try to combine Mutt with a fork and still call your package "mutt". I believe you ethically and legally already need to change your source tarball back to Mutt's if you want to name your package thus. Technically, separating out the NeoMutt patches would be satisfactory, but I would rather you make a decision which project you want to ship, or ship two packages, not ship a bastardization. You talk about "user expectations", but I've spent plenty of effort cleaning up and merging external patches, fixing bugs and security issues, and creating new features. I've seen nothing but even greater distance from Debian's package in return; culminating in you completely switching your source tarball out. Enough! So please submit your proposal, and I do expect something soon, but don't expect my cooperation unless you are willing to ship something _much_, _much_ closer to my upstream tarball. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Mutt - Neomutt and Debian Stretch
On Fri, Jun 30, 2017 at 09:55:33PM +, Antonio Radici wrote: > On Fri, Jun 30, 2017 at 10:54:16AM -0700, Kevin J. McCarthy wrote: > > As you know, the same thing happened with 1.6.2, when you first started > > incorporating NeoMutt. Your NeoMutt patches included half implemented > > features from 1.7.0 development, and was broken. > > I will be happy to understand what we are trying to achieve and mediate > between > the parts if possible. Is it about having a package that contains *only* the > mutt source code as you release it? It was never like this even before 1.6.*, > when we had extra patches on the top of mutt, what should I do with > patches/features which are (and were) expected on the top of mutt? Starting with a vanilla mutt tarball and adding a set of patches, broken out by bug fix or feature, is fairly standard practice. It's easy to see what is changed, and I think is still fair to call mutt. If you take a vanilla mutt tarball and add a 30k+ line "blob patch" called "neomutt", I don't think it's fair to call that mutt anymore. If you don't even package a vanilla mutt tarball, but take the tarball from a completely different project, it most definitely is not mutt. I think it comes down to accountability. If you know the changes you are making, then there is something of a guarantee the result is a *Debian* packaged version of *Mutt*. Debian may have made some changes, but is vouching that this is essentially Mutt, plus changes they comprehend and can vouch for. By switching out the tarball to someone something generated by another project, or adding a ginormous "blob patch", Mutt can not and should not vouch for it. You are relying on the other project's reputation, not ours. It is then completely inappropriate for you to call it mutt. It's not mutt. It's not "mutt + neomutt". It's neomutt. > I don't believe that your work is lost, all your code ends up in > Debian (and derivatives) and yes there will be patches on the top of > it. Perhaps lost was the wrong word. The code may be mixed in, but as Mutt project maintainer, the package has nothing to do with my work anymore. The package you are calling "mutt" is not something I've helped create. Your version "1.8.3+blah" is not even remotely the code I decided should be in version "1.8.3". It's code the NeoMutt project made the decision on. Is it that hard to understand why calling it mutt upsets me? -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Mutt - Neomutt and Debian Stretch
On Fri, Jun 30, 2017 at 07:03:22AM +, Antonio Radici wrote: > I agree that the naming + versioning is confusing but I've sorted that out > since > we switched .tar.gz from usptream a week ago, not +neomutt2017 is in the > version, for example the latest version of mutt is 1.8.3+neomutt20170609-2. > The main reason for the switch was that they have standardized code indenting, > therefore a theoretical neomutt patch would have been bigger than the source > code itself. Here's the thing. Your tarball is not just Mutt 1.8.3 + some NeoMutt stuff. It includes most everything in my development (default) branch for 1.9.0 as of 20170609. Stuff that hasn't had time to bake, or that I feel I have the right to change. NeoMutt pulls all the stuff out of *my* default branch, packs it in, and gives to you as if it were extra NeoMutt "goodness". With the new release numbering, I try very hard to keep the "patch" versions, e.g. 1.8.[1-3], as bug-fix only releases. They are released out of the "stable" branch. By calling your package "mutt 1.8.3", regardless of what extra version labels you attach, you are reflecting on me and making my efforts at stable releases irrelevant. As you know, the same thing happened with 1.6.2, when you first started incorporating NeoMutt. Your NeoMutt patches included half implemented features from 1.7.0 development, and was broken. > [...], I'll be open to reconsider this if/when the neomutt devs stop > rebasing their changes from the latest mutt source tarball. This furthers my point: if NeoMutt drives your decisions as a packager, you should name your package neomutt. > I know it is not simple to add a feature to the main code base because certain > standards have to be respected and some patches might generate undesiderable > side effect; at the same time Debian users have grown used to features that > have > been there even before I started maintaing mutt (compressed folders, sidebar, > etc) so I have to play a balancing act there. You mean the compressed folders that I fixed up and included in 1.8.0? Or the sidebar I spent a huge amount of effort fixing and included in 1.7.0? Wait, I must be mistaken, https://packages.debian.org/sid/mutt says those are NeoMutt additions. > I might have made some mistakes in the past so I'm sorry if I caused > extra work on your side, but it is my intention to do a fair amount of > investigation work before reporting any bug. The problem is not in your triaging, but that not every user picks up on the distinction when you call your package mutt. People show up in the IRC channel or mutt-users, or submit tickets directly. Then I end up trying to debug a problem that isn't even in the version they purport to be using. I understand your point about the extra work involved in multiple packages. But it is disrespectful to me for Debian to label a *fork's* tarball as the package "mutt". It is frustrating and demotivating that all my work towards resuscitating mutt is lost and mislabeled to the huge user base encompassed by Debian and all its derivatives. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Mutt - Neomutt and Debian Stretch
On Thu, Jun 29, 2017 at 04:05:35PM +0200, leo wrote: > I've read that Neomutt is not a fork "We merge all of Mutt's changes > into NeoMutt and get features into a state that Mutt will accept" [2]. No, it's a fork. And no, they don't get features into a state I will accept. > It isn't a big problem ;) but I want Mutt and not Neomutt. Let Debian know then. I used to spend time looking at Debian bugs, but don't bother anymore. I wish they would rename their package to NeoMutt since they've basically switched their upstream. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: New mutt GPGME error
On Thu, Jun 01, 2017 at 11:09:40AM -0700, Ian Zimmerman wrote: > Is there a good reason for this restriction, i.e. a known > incompatibility with gpgme-1.8 and later? I'm compiling against gpgme 1.8.0, and am not aware of any issues. I haven't tested against 1.9.0 yet, but haven't received any reports of problems. If anyone is aware of an issue, please file a ticket or email mutt-dev. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
mutt 1.8.3 released
Hi Mutt Users, I'm pleased to announce that version 1.8.3 has been released. Instructions for downloading are at http://www.mutt.org/download.html. This is a bug-fix release. Of note to Gmail users is a potential crash fix when copy/moving messages to its Trash folder. Thanks to everyone who submitted bug reports, patches, and helped with testing. -Kevin signature.asc Description: PGP signature
Re: New mutt GPGME error
On Tue, May 30, 2017 at 06:57:00AM -0700, Jeffery Small wrote: > > I just upgraded to Ubuntu 17.04 and got a new version of mutt: 1.7.2.1 > > I now frequently get the following error message for delivered mail: > > "GPGME: CMS protocol not available" > > I'm not using gpg and would like to stop the continual generation of these > messages. I'm hoping that there is something that can be placed in the > config file that can control this. If you're not using gpg, the easiest fix is to put 'unset crypt_use_gpgme' in your .muttrc. Alternatively, you can install the gpgsm package, to enable S/MIME (CMS) support in GPGME. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: customize folder order in sidebar
On Mon, May 08, 2017 at 06:17:58AM +0800, Yubin Ruan wrote: > I was wondering whether it would be possible to customize the folder order in > mutt's sidebar. I have subscribed to some mailing lists and have mails from > each of them automatically put into a seperate folders. But there are some > mailing lists that I found more important and will check more frequently. > Therefore, I would like to re-arrange them to the top of the sidebar so that > I can see whether there are new mails in those mailing lists. If you set $sidebar_sort_method=unsorted (the default), it uses the order listed in the 'mailboxes' commands. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Scroll-off option for mutt
On Mon, May 08, 2017 at 05:49:40AM +0800, Yubin Ruan wrote: > Is it possible to do this for the sidebar in mutt? Are there anything like > $sidebar_scroll and $sidebar_context? Not currently. It's a good suggestion though. I'll look into it. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Scroll-off option for mutt
On Sun, May 07, 2017 at 05:43:00PM +0800, Yubin Ruan wrote: > On Sat, May 06, 2017 at 09:50:50AM -0700, Kevin J. McCarthy wrote: > > On Sun, May 07, 2017 at 03:36:41AM +0800, Yubin Ruan wrote: > > > Is there a scroll-off option for mutt? In vim, you can use > > > set scrolloff = 7 > > > to make the editor scroll rather than changing pages when you get to the > > > end of > > > the current page, so that you can see things continuously. But for mutt's > > > pager, > > > it seems not possible to do so. Anyone know any alternative methods? > > > > and can scroll line by line. $pager_context > > can give you some overlap when scrolling page by page. > > Hmm...I mean the index (where all the emails are listed), not pager. I can > make > the pager scroll. But I cannot make the index do so. Sorry for the misuse of > terminology. Sorry about my misunderstanding. As Erik mentioned, there is $menu_scroll, but may want to also try setting $menu_context=7. With both of them set, I hope that may be close to what you are looking for. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Scroll-off option for mutt
On Sun, May 07, 2017 at 03:36:41AM +0800, Yubin Ruan wrote: > Is there a scroll-off option for mutt? In vim, you can use > set scrolloff = 7 > to make the editor scroll rather than changing pages when you get to the end > of > the current page, so that you can see things continuously. But for mutt's > pager, > it seems not possible to do so. Anyone know any alternative methods? and can scroll line by line. $pager_context can give you some overlap when scrolling page by page. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Minor annoyance with mutt, crypt_replyencrypt and PGP
On Wed, Apr 19, 2017 at 06:56:37AM +0200, Francesco Ariis wrote: > Hello Kevin, > > On Tue, Apr 18, 2017 at 11:49:03AM -0700, Kevin J. McCarthy wrote: > > On Tue, Apr 18, 2017 at 07:10:43PM +0200, Francesco Ariis wrote: > > > 5. Now it seems I am stuck in the select key menu, and I have > > >no idea how to exit it without sending the email > > > > You should be able to hit ctrl-g to get out of that prompt and back to > > the compose screen. > > C-g doesn't bring me out of that prompt (mutt 1.5.23), urxvt. Is > it a bound function or just a 'generic' key combination? Sorry, I may have misunderstood. If you're in the select key menu, showing a list of matching keys, you can hit 'q' to exit the menu. It should then display a prompt: "Enter keyID for xxx: ". You should then be able to hit ctrl-g at that prompt and it will bring you back to the compose menu. C-g is a 'generic' abort key for prompts. I don't think 1.5.23 was different with this behavior, but it has been a while since I used that version. :-) -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
mutt 1.8.2 released
Hi Mutt Users, I'm pleased to announce that mutt version 1.8.2 has been released. Instructions for downloading the release are at http://www.mutt.org/download.html. This release fixes a regression in 1.8.1 that resulted in gpg failures with an ncurses pinentry program. Thanks to ilf on IRC for alerting me to the problem and helping test out the fix. -Kevin signature.asc Description: PGP signature
Re: Small question for mutt-1.8.x
On Tue, Apr 18, 2017 at 09:29:41PM +0200, Pavel Troller wrote: > When (q)uitting, mutt 1.5.x asked for example: > Move read messages to /home/patrol/Mail/mail.arch? ([no]/yes): > while the new mutt just quits and to be honest, I don't know, how to > trigger this action manually and then quit. Try setting $move to ask-no. Version 1.5.19 changed the default of $move to "no". The documentation for $move mentions this, but the "Using Multiple Spool Mailboxes" section does not. I'll add a mention about this. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Minor annoyance with mutt, crypt_replyencrypt and PGP
On Tue, Apr 18, 2017 at 07:10:43PM +0200, Francesco Ariis wrote: > 5. Now it seems I am stuck in the select key menu, and I have >no idea how to exit it without sending the email You should be able to hit ctrl-g to get out of that prompt and back to the compose screen. > alternatively a way to colour `Security: Encrypt (PGP/MIME)` red or > something? Not currently, but this was suggested in https://dev.mutt.org/trac/ticket/3915 and I'll be looking into it for a future release. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
mutt 1.8.1 released
Hi Mutt Users, I'm pleased to announce that mutt 1.8.1 has been released. Instructions for downloading are at http://www.mutt.org/download.html. As usual, the release tarball is signed with my gpg key. This is a bug fix release. In particular, it has fixes for setenv, sidebar_whitelist, some refresh issues, and a potential segfault. Details can be seen in the ChangeLog file. Thanks to everyone who contributed towards this release, and for your help keeping Mutt development going. I couldn't do it without your support and encouragement. -Kevin signature.asc Description: PGP signature
Re: Quitting when messages tagged
On Tue, Apr 11, 2017 at 09:52:42PM -0600, Charles Cazabon wrote: > I'm wondering if there's a setting or combination of settings I'm missing to > prevent an annoyance. In short: an accidentally-doubled "q" keypress in the > message view will quit mutt (I have exit set to the default of "yes"), even if > I have a bunch of messages tagged in the folder view. No there is no such setting. I can only think of two workarounds, but you may not like either. First, you could try training yourself to use 'i' to exit the pager menu instead. Some distros include a version of the nntp patch which steals this keybinding, but by default it is bound to in the pager menu but not the index menu. Another possibility is to wrap the tagging and tag-copy/save operations in macros, which set quit=ask-yes/no on tag and unset quit on copy/save. It's impossible to make this perfect though. A macro wouldn't be able to figure out if you are toggling a tag back off. There are also probably some issues with wrapping a tag-copy/save operation effectively. It might be worth playing with though. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: strip of some filename chars in folder_format setting
On Wed, Apr 12, 2017 at 03:26:51PM +0200, Oliver Graute wrote: > how can I strip of the first 23 chars of my filename string in the > folder_format setting? I don't believe the built-in format specifiers give this functionality. You may want to try using a filter: https://dev.mutt.org/doc/manual.html#formatstrings-filters -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
