On Thu, Aug 14, 2008 at 01:51:58PM -0400, Aron Griffis wrote: > Louis-David Mitterrand wrote: [Thu Aug 14 2008, 01:05:06PM EDT] > > Why not simply use > > > > set record=imaps://your.courier.host/INBOX.Outbox > > set sendmail='cat > /dev/null' ## or equivalent > > > > No need for a patch, or did I miss something? > > I agree that seems like the obvious solution, but it has a number > of problems. I detailed some of the history of this patch at > http://blog.n01se.net/?p=10 but here's the relevant excerpt: > > I tried setting $sendmail=/bin/true and used $record to fcc > the message to the IMAP Outbox. This hack generally worked. > The fcc-status patch is needed to prevent "Status: RO" > (screws up the recipients that use mboxes; the mail shows up > as already-read). Additionally mutt doesn't provide a method > to fcc to more than one folder, so to get an fcc other than > the Outbox, I used the write-fcc function in the compose > menu. That was broken because it lacks the Message-ID, > encryption/signing, date, etc! > > Moreover it all falls apart when bouncing (remailing) > messages, because that code path calls mutt_invoke_sendmail > directly, and of course no fcc is done.
Indeed, this patch is really useful. I hope it gets mainlined. One question: will the patch still work when using imap in tunneling mode? account-hook ^imaps?://my.imap.host/ 'set tunnel="/usr/bin/ssh my.imap.host /usr/bin/imapd 2>/dev/null"'
