mutt 1.11.1 released

2018-12-01 Thread Kevin J. McCarthy
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 . This release fixes a crash bug involving the new $imap_qresync feature. Special thanks to ilf for reporting this to me

Sending via command line and $record

2018-12-01 Thread Dave Woodfall
Hi I have been using a script for a while now that uses mutt to send emails out. I've just noticed today that it no longer saves in =Sent, and I suspect it's since I started using a dynamic record setting - i.e. ^ for most mail, but =Sent for mailing lists. I can't see any option for fcc'ing mai

Re: Sending via command line and $record

2018-12-01 Thread Kevin J. McCarthy
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. McC

Re: Sending via command line and $record

2018-12-01 Thread Dave Woodfall
On Saturday 1 December 2018 16:19, Kevin J. McCarthy put forth the proposition: > 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 > > st