Re: [PATCH] Fix sidebar_sort_method usage in documentation

Committed. Thank you! -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: Message-id parsing change

On Thu, May 14, 2020 at 06:36:28PM +0200, Oswald Buddenhagen wrote: On Thu, May 14, 2020 at 07:18:24AM -0700, Kevin J. McCarthy wrote: On Thu, May 14, 2020 at 11:51:08AM +0200, Oswald Buddenhagen wrote: i think a reasoanble heuristic would be to just accept anything as long as it's a single

Re: Message-id parsing change

. We've basically already taken the approach garbage-in garbage-out, if it was surrounded by <>. This is expanding that, but at least adding the <> delimiters back. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: Message-id parsing change

On Thu, May 14, 2020 at 11:51:08AM +0200, Oswald Buddenhagen wrote: On Wed, May 13, 2020 at 08:03:02PM -0700, Kevin J. McCarthy wrote: However, in order to reduce the risk of extracting garbage, insist that message-id's outside of angle brackets at least have an '@'. well, guess what

Message-id parsing change

, but ticket 241 prompted me to work on it a bit sooner. I've just committed a change to master that loosens this up a bit. Note that message-ids are stored in the header cache, so you'll need to flush the header cache in order for Mutt to reparse them. -- Kevin J. McCarthy GPG Fingerprint: 8975

Re: locking mechanism

e will first perform fcntl/flock and then *also* perform a dotlock. I guess you could disable the dotlock by setting $dotlock_program to "/bin/true". -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: [PATCH] Remove commented out mutt_message_hook calls

On Thu, May 07, 2020 at 07:41:43PM -0400, Remco Rijnders wrote: --- recvcmd.c | 4 1 file changed, 4 deletions(-) Given that those were commented out 20 years ago, that seems reasonable. I've commmited this too. Thank you. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C

Re: [PATCH] Clarify CH_WEED debug message

On Thu, May 07, 2020 at 07:17:42PM -0400, Remco Rijnders wrote: --- copy.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Committed. Thank you. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: LF to CRLF translation responsibility

, not an MSA afterall. :) I just peeked in msmtp's code and it does appears to perform LF to CRLF conversion. So perhaps there is a bug in the submitter's version, or the problem is something else. Thanks everyone for your help! -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308

Re: LF to CRLF translation responsibility

in outgoing mail. Whoops. Indeed. I saw the linked Debian ticket was about msmtp, but somehow missed the Mutt ticket was using msmtp too. I must be going blind slowly. :-/ So the problem would seem to be in msmtp. Thank you Kurt! -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910

Re: LF to CRLF translation responsibility

On Wed, May 06, 2020 at 08:44:29PM +0200, Claus Assmann wrote: On Wed, May 06, 2020, Kevin J. McCarthy wrote: RFC5322 states that headers and the header/body delimiter are supposed to be CRLF, but I (and ticket #235) note that mutt is writing them with just LF. Thank you for your reply

LF to CRLF translation responsibility

. Is that correct, and if so, is there a specification documenting that expectation? Thank you very much! -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: mutt 1.14.0 released

gression I accidentally introduced in the 1.13 series. :-/ I would have released a fix for 1.13, but didn't realize the regression until a ticket submitted last week. (It turns out I had already fixed the problem during 1.14 development as part of fixing a bigger problem.) -- Kevin J. Mc

Re: [PATCH] olen length requirement was too conservative

On Sun, Apr 19, 2020 at 02:20:33PM -0700, Kevin J. McCarthy wrote: On Sun, Apr 19, 2020 at 04:28:02PM -0400, Remco Rijnders wrote: When converting binary values to Base 64 encoding, we go from a 8 bit representation to a 6 bit representation. As a result, we need extra space to store the result

Re: mutt 1.14.0 released

On Sun, May 03, 2020 at 04:05:30AM +0200, Moritz Barsnick wrote: On Sat, May 02, 2020 at 18:02:59 -0700, Kevin J. McCarthy wrote: I'm pleased to announce the release of version 1.14.0. Thank you, great job! Thank you Moritz. I'm always glad to hear from long-time users, especially when

Re: exact address: broken with utf-8 encoding

On Thu, Apr 23, 2020 at 07:11:08AM -0700, Kevin J. McCarthy wrote: Claus, would it be acceptable for Mutt to normalize the email addresses you send or reply to? That way, 2047-encoding and IDNA can be properly applied. As a compromise for this release, I have pushed a change that disables

Re: [PATCH] Change Message-ID generation to be more unique and leak less information

uot; again, didn't I? :-) Sorry Remco. Hopefully it's clear enough now that by "leak" we mean the memory is not being free()'ed properly. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: exact address: broken with utf-8 encoding

On Thu, Apr 23, 2020 at 07:11:08AM -0700, Kevin J. McCarthy wrote: Claus, would it be acceptable for Mutt to normalize the email addresses you send or reply to? That way, 2047-encoding and IDNA can be properly applied. A patch for that behavior would look like this: diff --git a/rfc2047.c b

Re: exact address: broken with utf-8 encoding

On Thu, Apr 23, 2020 at 01:56:32PM +0200, Vincent Lefevre wrote: On 2020-04-23 09:47:08 +0200, Claus Assmann wrote: On Wed, Apr 22, 2020, Kevin J. McCarthy wrote: > I think I would prefer to make "exact address" deprecated in 1.14 and remove > it for 1.15. Then I would not

Re: [PATCH] Change Message-ID generation to be more unique and leak less information

like to understand. Can you clarify this to me and explain how this would be a concern? The memory allocated and returned by mutt_gen_base64_enc_rand() is being leaked. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP

Re: exact address: broken with utf-8 encoding

but: Are there still users who use this old syntax??? Exactly. I don't think it's worth the trouble, and it still wouldn't completely fix the problems. I think I would prefer to make "exact address" deprecated in 1.14 and remove it for 1.15. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3

Re: exact address: broken with utf-8 encoding

, including the email address. I suspect there was a problem in your testing. Please test again, and if you are positive provide more details. The (non exact address) 2047 code doesn't touch the email address unless it's a group address. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910

Re: exact address: broken with utf-8 encoding

On Wed, Apr 22, 2020 at 02:57:22PM -0700, Kevin J. McCarthy wrote: The "exact address" is also a mess with respect to IDNA encoding. Fixing it will require some thought. The whole point was to capture the address "as typed", but we have to parse it to properly apply 2047

Re: exact address: broken with utf-8 encoding

On Wed, Apr 22, 2020 at 02:31:32PM -0700, Kevin J. McCarthy wrote: I'm looking at whether encode_specials should be set for the exact address (ptr->val) value. My suggestion would be to try turning it off as a workaround for now. The "exact address" is also a mess with re

Re: exact address: broken with utf-8 encoding

_rfc2047_encode_string (>val, 1, col); dprint (2, (debugfile, "%s: out:%s\n", __FUNCTION__, ptr->val)); } #endif I'm looking at whether encode_specials should be set for the exact address (ptr->val) value. My suggestion would be to try turning it off as a workaround for now.

Re: exact address: broken with utf-8 encoding

de can fix it. I'll try to take a look, but this likely won't be something I can get to (or commit) for 1.14.0. I haven't delved into the exact address code much, and so need to tread carefully. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA sig

Re: exact address: broken with utf-8 encoding

get fixed and then broken again? I haven't take a look at the problem yet; just wanted to know whether to look out for something I've done or a deeper problem. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: consistency in message strings

sed to put myself above Thomas Roessler, Brendan Cully, Rocco Rutte, and all the others who have put so much into this project too. I think the most respectful thing is to leave the single line version with Michael Elkins' name. :) -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910

Re: consistency in message strings

On Mon, Apr 20, 2020 at 07:08:34PM +0200, Vincent Lefevre wrote: On 2020-04-20 09:14:22 -0700, Kevin J. McCarthy wrote: On Mon, Apr 20, 2020 at 04:13:08PM +0200, Vincent Lefevre wrote: > BTW, about copyright years, "mutt -v" says: > > [...] > Copyright (C) 1996-2016 Michae

Re: consistency in message strings

since 2016. Is it correct to swap the date to 2020, or should I instead change the line to show my copyright? -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: [PATCH] Change Message-ID generation to be more unique and leak less information

ing versus hashing. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: consistency in message strings

; "GPG key" I may be able to edit the translation strings too. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: consistency in message strings

quot;autocrypt" should be written with a capital letter (Autocrypt) like on the official website <https://autocrypt.org/>. Hi Vincent and welcome back! Corrections are welcome, but let's wait on translation string changes until after the release. I've already received five of the tran

Re: [PATCH] olen length requirement was too conservative

, but FYI that during the freeze I'm not looking at these kind of patches. I'll take a closer look after the release. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: [PATCH] Change Message-ID generation to be more unique and leak less information

On Sun, Apr 19, 2020 at 12:00:45PM +0200, ilf wrote: Should I open a ticket with this suggestion? Thanks ilf, and others. I think I've made my thoughts clear elsewhere in this thread. However, I have opened a placeholder ticket #222 for future consideration. -- Kevin J. McCarthy GPG

Re: [PATCH] Change Message-ID generation to be more unique and leak less information

? Personally, I approved the MR for a different reason - disclosing version numbers opens the potential for targeted attacks. Reducing metadata was secondary for me, and still is a minor factor when it comes to competing interests (e.g. correctness, security, performance, utility). -- Kevin J

Re: Background editing

license as the rest of Mutt (GPL 2+) to the header? -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: [PATCH] Include instructions on how to build with sidebar support

On Sat, Apr 18, 2020 at 11:50:45AM -0400, Remco Rijnders wrote: --- INSTALL | 5 + 1 file changed, 5 insertions(+) diff --git a/INSTALL b/INSTALL Applied. Thanks. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP

Re: [PATCH] Change Message-ID generation to be more unique and leak less information

were a *real* threat model, Derek and I would take this more seriously. But I'm not going to backtrack on the generator determinism just to satisfy vague "security" threats. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: [PATCH] Change Message-ID generation to be more unique and leak less information

that trade-off. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Mutt 1.14 freeze in progress

you, -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: Background editing

u had sent a useful script too. Sorry for dropping the ball on replies! As I said with Aaron, the same goes here. If you'd like to contribute this, or a current iteration of it, please just let me know. I'll bundle them into a background-edit group. Thank you. -- Kevin J. McCarthy GPG Fingerp

Re: Upcoming freeze for 1.14 release

the below script to wait for a passed command, allowing me to `set editor="tmuxwait vim"`. https://github.com/aschrab/dotfiles/blob/master/bin/tmuxwait Nice. If you would like to distribute it in Mutt's contrib, let me know. Be sure to add a license and copyright in that case.

Upcoming freeze for 1.14 release

welcome, but nothing too crazy at this point. :) Thanks, -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: Counting single inline-part "attachments"

content in the MIME root element. (E.g. "attachments +R image/*") Thanks a lot for your response, David! I'll see if I can work in a +R functionality without disturbing the code too much. :) -Kevin -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684

Counting single inline-part "attachments"

ionality in this case without goofing up existing configs? -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: Attachments counter broken?

t;: and see if there is a Muttrc file in one of those directories? If so, see if there are any 'attachments' lines in there. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: Background editing

in $status_format, so (everyone) please feel free to provide opinions if you think another default value would be better, just like with $background_format. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: Background editing

On Mon, Mar 02, 2020 at 10:44:02PM +0300, Consus wrote: On Mon, Mar 02, 2020 at 09:31:23AM -0800, Kevin J. McCarthy wrote: I can easily add an expando for the total number of background sessions: both still editing, and done editing but waiting to be resumed. Would that be helpful

Re: Background editing

pid inside the background menu). -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: Background editing

On Sun, Mar 01, 2020 at 03:49:10PM -0800, Kevin J. McCarthy wrote: Thank you for giving it a try so quickly! That sounds like a good suggestion. I'll add that in later tonight. I added %i to the list of expandos for $background_format. Although I didn't add it to the default value, I'm

Re: Background editing

the Message-Id of the replied-to messsage could be added to background_format so that could be looked up if in doubt. Hi Eike, Thank you for giving it a try so quickly! That sounds like a good suggestion. I'll add that in later tonight. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C

Re: Background editing

On Sun, Feb 23, 2020 at 01:32:05PM -0800, Kevin J. McCarthy wrote: Just a brief weekly update. Last update for this thread. I've merged the branch into master. Testing and suggestions are most welcome. Please check out the section in the manual: <https://muttmua.gitlab.io/mutt/man

Re: Background editing

Hi Everyone, Just a brief weekly update. On Mon, Feb 17, 2020 at 10:03:19AM -0800, Kevin J. McCarthy wrote: After I get the above working, I'll start working on multiple-background processes along with a "resume" menu. This is now pushed up to the kevin/background-edit branch. I

Re: Background editing

On Sun, Feb 09, 2020 at 06:07:18PM -0800, Kevin J. McCarthy wrote: Recently, I've been playing around with background editing. This is still in the early stages, and is very much "work in progress" - meaning the code is a mess, light on testing, and subject to rebasing. But if

Re: Do you have any plans to make mutt compatible with Microsoft's Exchange Online after they discontinue support for IMAP?

me in, or your local administrators may be able to help. You could point them to <http://www.mutt.org/doc/manual/#oauth> to show how Mutt is using a script for Gmail OAUTHBEARER and see if there is anything equivalent that could be used for Exchange Online. Hope that helps, -- Kevin J. McCa

Re: Do you have any plans to make mutt compatible with Microsoft's Exchange Online after they discontinue support for IMAP?

at it yet. Is usage becoming widespread outside of Fastmail yet? -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Background editing

n around to blocking exiting with a backgrounded session yet, so for now "don't do that". Yeah, that's a lot of caveats, but I'd still appreciate ideas or feedback from those brave enough to give it a try. Thanks, -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910

Re: Mutt 1.13.0 problem with German umlauts

did not help. Make sure you have libncursesw5-dev installed. You'll need to re-run configure after that is installed. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Freeze for translations in place

composition is discussed at <https://muttmua.gitlab.io/mutt/manual-dev.html#alternative-order>. Martin F. Krafft's sample filter is under contrib/markdown2html. Help testing the new features is always appreciated too. Thank you, -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 38

Re: botched display - mutt or ncurses bug?

main.c:591. However I'm starting to suspect something funky with your terminal or terminfo... -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: botched display - mutt or ncurses bug?

where the flag is reset *after* the resize/reflow. That does seem racy, and is easy enough to fix. I've pushed a commit up to the branch 'kevin/sigwinch-fixes'. Would you mind giving that a try and seeing if it resolves the issue? -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C

Starting towards a 1.13 release

of 11/29-12/1. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: MTA behavior with respect to Bcc headers

On Sat, Nov 02, 2019 at 07:00:55AM +0800, Kevin J. McCarthy wrote: Personally I'm leaning toward #1 to at least give users the choice (assuming there might be that one MTA, somewhere, that reads recips from the mail by default instead of looking at the arguments). I've implemented #1

Re: www.mutt.org https certificate problem?

a ticket opened with them about it, so I know it's on their todo list for eventually. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: $send_multipart_alternative

On Sat, Nov 02, 2019 at 09:18:14AM +0800, Kevin J. McCarthy wrote: I don't want to over-complicate the code, but if there is a quick fix, I'll see what I can do about this. I won't have a chance to work on it until later this week though. I put together a quick hack and pushed it up

Re: $send_multipart_alternative

On Sat, Nov 02, 2019 at 08:56:08AM +0800, Kevin J. McCarthy wrote: I'll have to look at the code when I have more time. But I still wonder if you sent the message, and whether the actual sent message was corrupt or just the preview. Okay, taking a quick peek, I see sending wouldn't work

Re: $send_multipart_alternative

On Sat, Nov 02, 2019 at 08:49:14AM +0800, Kevin J. McCarthy wrote: Did you try previewing the message, or just sending it straight through? It *might* work, if you don't use preview before sending. Trying to preview will cause mutt to parse out the parts in a receive-mode manner, which won't

Re: $send_multipart_alternative

ny promises about the behavior in that case. Did you try previewing the message, or just sending it straight through? It *might* work, if you don't use preview before sending. Trying to preview will cause mutt to parse out the parts in a receive-mode manner, which won't work when you then try to

Re: MTA behavior with respect to Bcc headers

I've been using the default i.e. write_bcc=yes for years. I need to fix that. Me too, and as Gero made me aware of, it affects exim4. Fortunately, I believe my provider is stripping the header for me, but it's certainly embarrassing. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910

Re: MTA behavior with respect to Bcc headers

! -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: [PATCH] Exit pager before calling browse-mailboxes

On Thu, Oct 17, 2019 at 07:42:19AM +0800, Kevin J. McCarthy wrote: I believe I know what the problem is. I was staring so hard at the wrong places I missed it. :-( I don't have time to work on it until later today, but I'll try to post a patch by tomorrow. I've pushed a quick-fix commit

Re: [PATCH] Exit pager before calling browse-mailboxes

what the problem is. I was staring so hard at the wrong places I missed it. :-( I don't have time to work on it until later today, but I'll try to post a patch by tomorrow. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description

Re: [PATCH] Exit pager before calling browse-mailboxes

t folder hook, or something else. If you could send a minimal muttrc that triggers it, that would be helpful. Thank you, -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: Difference between and with $pipe_decode

On Sat, Oct 12, 2019 at 09:24:36AM +0800, Kevin J. McCarthy wrote: I'm wondering if anyone on the list can supply context for the difference between pipe decode and copy decode, before I experiment with adding those two flags for piping too. The only gotcha I can see (so far) is that the pipe

Re: [PATCH] Exit pager before calling browse-mailboxes

ntly? What exactly are you doing that generates the error when invoking 'y' from the pager. Is there any reason why you shouldn't create the macro yourself in that case? -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Difference between and with $pipe_decode

erence between pipe decode and copy decode, before I experiment with adding those two flags for piping too. Thank you! -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Planning stable 1.12.2 release this weekend

Just a heads up that I plan on releasing 1.12.2 this coming weekend. Derek, I feel confident in Gero's fix, but if you have the chance to compile and test before the weekend that would be great. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA

Re: make fails

git branch instead. Thank you! -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: make fails

it by simulating this scenario in the build, leading to a binary using the alternate function. Thanks Gero. I already fixed the compile error in commit 4c2f7c70, but it will be good to have the functionality available on older systems too. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910

Re: make fails

our muttrc. Starting in 1.12, I defaulted that on because of the increasing prevalence of gpg 2.1 (which uses an agent by default). Also, make sure to use the latest contrib/gpg.rc settings. Some of them are now necessary for proper decryption and signing verification. -- Kevin J. Mc

Re: make fails

'--disable-filemontor'. The fix will just end up disabling it on your system. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: make fails

On Mon, Aug 26, 2019, at 3:13 PM, Derek Martin wrote: > Folks, > > I downloaded mutt-1.12.1 today, and tried to compile it. I ran > configure thusly: Derek I will be back from my trip tomorrow and take a look at this. Probably the calls are not ifdef'ed out. -Kevin

Re: Autocrypt and encrypted/signed mail from a key in pubring

On Sun, Aug 18, 2019 at 03:29:50PM -0700, Kevin J. McCarthy wrote: Another choice would be to point $autocrypt_dir at ~/.gnupg (you can copy the autocrypt.db file over to save yourself having to recreate accounts). However, this will then cause Autocrypt header keys to be imported

Re: Autocrypt and encrypted/signed mail from a key in pubring

On Sun, Aug 18, 2019 at 03:29:50PM -0700, Kevin J. McCarthy wrote: Another choice would be to point $autocrypt_dir at ~/.gnupg (you can copy the autocrypt.db file over to save yourself having to recreate accounts). Actually, peer keys would be in the database but not keyring if you just

Re: Autocrypt and encrypted/signed mail from a key in pubring

only if we would subsequently be trying autocrypt. Right now, the changes are in gpgme only, and are very clean... -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: pkg-config usage for sqlite3

. This seems possible. I wonder how the performance would compare. I'll put it on my todo list, but not for this cycle. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: pkg-config usage for sqlite3

th sqlite3. :-/ -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: Autocrypt

On Mon, Aug 12, 2019 at 04:13:16PM -0700, Kevin J. McCarthy wrote: The base64 keydata is stored in the sqlite3 database once the account is created. Updating the key in gpg subsequent to that won't have an effect on the keydata. Make sure to remove the account (via ) and recreate it if you

Re: Autocrypt

keydata is stored in the sqlite3 database once the account is created. Updating the key in gpg subsequent to that won't have an effect on the keydata. Make sure to remove the account (via ) and recreate it if you modify or re-import the key. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3

Re: pkg-config usage for sqlite3

On Mon, Aug 12, 2019 at 07:11:20PM +0200, Oswald Buddenhagen wrote: On Mon, Aug 12, 2019 at 09:15:57AM -0700, Kevin J. McCarthy wrote: One common, and increasingly prevalent, solution is to use pkg-config and the related autoconf macros (e.g. PKG_CHECK_MODULES). However, this isn't without

pkg-config usage for sqlite3

issues, for example dealing with libraries installed in non-standard places. What do you all think about using pkg-config for the sqlite3 dependency? Experiences and tips on doing this properly are welcome. Thank you. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684

Re: Autocrypt

header, again? I've seen other rsa4096 keys where the header is around 45 lines. GPGME_EXPORT_MODE_MINIMAL should be removing all extraneous signatures, so there is no reason for it to be much bigger than that. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031

Re: Autocrypt

ould have acceptable performance for this usage though. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: Autocrypt

because of the autocrypt header scanning, or just in general due to having to rebuild the header cache? While there will be *some* slowdown due to Autocrypt, it shouldn't be that noticeable. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: Autocrypt

eader cache. I didn't mention it in the docs because that would make the issue more confusing. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: Autocrypt

the header, not the UID, to look up the correct key. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: Specific Handling for text/calendar MIME Type

index_format="... %1@hascal@ ..." index-format-hook hascal "~M text/calendar" "C" -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: Specific Handling for text/calendar MIME Type

-used for some more specific limits to be added? You may want to try the ~M pattern. As you mention, ~X doesn't recurse multipart/alternative but I'm not convinced it should. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP

Re: potentially incorrect conversion of pointer to unsigned long

On Sat, Jun 22, 2019 at 07:19:41AM -0700, Kevin J. McCarthy wrote: On Sat, Jun 22, 2019 at 09:42:36AM +0200, Vincent Lefevre wrote: IMHO, the best solution for safety would be to use a union (I think that this would require the use of C99 designators for the MuttVars initialization). Okay, I

<    1   2   3   4   5   6   7   8   9   10   >