On 2026-10-28 13:49, Nicolas George wrote: >> Is there something I'm missing to get mutt to deliver a message >> straight to a FCC: mailbox without an intermediate recipient? > > Hi. The way I understand it, it is designed so that Fcc is a side > effect of sending, not the other way around, and it is not possible to > send without a recipient because the recipient argument is mandatory > to /usr/lib/sendmail and the RCPT command is mandatory in SMTP.
Okay, that's what I've been picking up from my experiments. I know that mail(1) does some recipient-sniffing (in OpenBSD's mail(1), I need to set the 'expandaddr' option), so I can specify $ mail ... & mail ~/mbox Subject: Notes... to have a message go into my ~/mbox folder, or if I have 'folder' set, I can & mail +somefolder to send a message to an mbox file in my 'folder'-setting directory > You could put a dummy recipient and let the mail bonce. Yeah, that's sorta what I've done, just replying, sending the message to myself (it FCCs the current folder as a side-effect), I just then have to wait for the message to arrive, then clean up the duplicate message with <delete-pattern>~=<enter> > You could put a dummy recipient and use a script that does `cat > > /dev/null` to deliver the mail instead of /usr/lib/sendmail. Yeah, that's another option, but I was hoping to avoid messing with the system-wide delivery for a particular dummy-recipient address. > Different method: you can postpone the mail and then move it from > the postponed mailbox to the fcc mailbox. Or change the name of the > postpone mailbox just before you postpone. that's more steps than I was hoping for :-) Thanks though! -tkc --
