On 11.06.19 13:45, Kevin J. McCarthy wrote: > On Tue, Jun 11, 2019 at 06:43:25AM -0700, Kevin J. McCarthy wrote: > > Something like $fcc_order or $fcc_before_send is possible, > > I've pushed a branch up to gitlab, kevin/fcc-before-send. It adds > $fcc_before_send, default unset.
Many grateful thanks, Kevin. That leaves Derek unimpacted, while restoration of what we had protects older use cases. Nicolas' case of a recipient having a copy of an email, but the sender not, can be a serious problem. For the last half year I have been exchanging (approval) stamped plans with authorities, consultants, engineers, and now building contractors. As I've made design changes along the way, it is very import to know which version of the plans has been received by which recipient - and that a quote received here applies to a specific plans version. > The caveats to enabling are as mentioned: message manipulation is turned > off, so $fcc_clear and $fcc_attach are ignored. Another change (from before > 1.12.0) is if the Fcc fails, you are prompted to retry or save to another > mailbox, rather than returned to the compose menu. The caveats are just fine in my use case. I had to look up $fcc_clear, as I've never figured out any use for message signing. (The framing carpenters would doubtless look at me oddly if I sent such stuff.) And, oh goody!, $fcc_attach defaults to yes, so the plans and other attachments will be saved. Prompting for an Fcc retry seems ideal to me. To regain that, in place of being dumped elsewhere, is another improvement. Mission accomplished - Mutt much improved. > The branch is off of stable, and is fairly minimal. I planned on releasing > 1.12.1 this weekend with some important fixes. If those opposed to the new > Fcc behavior think this is an acceptable alternative, I'll be glad to > include it in that release. That would be brilliant, Kevin. I'll look for it next week, then. Many thanks, again, for the effort you're putting in to make mutt the ideal MUA - despite a variety of use cases in the wild. Erik