When using unstable, "resend-message" essentially behaves like the
recalling of a postponed message. Actually, it shares lots of code
with that function. Thus, you can just re-send the message.
The problem with this is that the message will be sent depending on
the headers, that is, every recipient gets the message again.
You can work around this by changing the To and CC headers of the
submission to ORig-To and Orig-CC or something like that, and by
adding a To header of your own. As an alternative, it should be not
too difficult to implement a send-to function on the compose menu,
which sends a message with the given headers to recipients which are
entered on a prompt.
Would this fit your needs?
On 1999-10-10 14:54:21 -0700, rex wrote:
> Date: Sun, 10 Oct 1999 14:54:21 -0700
> From: rex <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: Editing a bounced message
>
> On Fri, Oct 08, 1999 at 12:44:09PM -0500, Jeremy Blosser wrote:
> > rex [[EMAIL PROTECTED]] wrote:
> > > The (I think) ideal solution would be for Mutt to offer the option to
> > > edit the message after "bounce" is selected.
> >
> > In the stable branch there is an 'edit-message' function that may do what
> > you want. This is being reworked currently in the unstable (dev) branch to
> > include separate 'edit-message' and 'resend-message' functions -- that
> > 'resend-message' is going to be what you want, but the existing
> > 'edit-message' may do it for you.
>
> Thanks, but it doesn't work. If the message is edited ("e") before the
> attempted bounce, "b" brings up a "Bcc:" query rather than bouncing
> the message as it would had the message not been edited. In other words,
> there is apparently no way to bounce after editing.
>
> I'd change the sendmail call in .muttrc to call a shell script to allow
> me to edit the message before calling sendmail, but I don't know how
> to pass the message to the shell script. IOW, I don't know how/where
> sendmail is getting the message. The line in .muttrc is
> set sendmail="usr/lib/sendmail -oi -oem"
> I can't find any docs on what "-oi" and "-oem" do.
>
> -rex (frustrated, again)
>
