Re: Editing a bounced message
On Wed, Oct 13, 1999 at 12:18:17PM -0500, David DeSimone wrote:
> rex <[EMAIL PROTECTED]> wrote:
> >
> > If the message is edited ("e"), the bounce function is disabled, and
>
> As someone else pointed out, what I mean was to edit the message, save
> the edited message back to the folder, then bounce that message.
Yuck! :) (no offense, it works, but it sure is awkward.)
> Since I don't use edit-message very often, it didn't occur to me that it
> would be difficult to tell the original from the new (edited) message in
> the folder.
I need to edit/bounce about 20 messages a day to my list, so
minimizing keystrokes is important. I've incorporated the changes you
suggested to my script and put
"macro index B bbt\ny#bounce/edit to BT(alias for Birdtech-L)"
in .muttrc. "B" bounces (i.e., inserts the "Resent-*" lines) the message
and brings it up in my editor. Nothing more needs to be done to the
header, and when the editor is exited the message is automatically mailed
to the list. Very, very, handy for LISTSERV listowners. Now if I could just
make the script smart enough to do most of the editing...
Thanks,
-rex
Re: Editing a bounced message
rex <[EMAIL PROTECTED]> wrote:
>
> If the message is edited ("e"), the bounce function is disabled, and
> "b" results in a Bcc: query instead of bouncing the message as it
> normally would.
As someone else pointed out, what I mean was to edit the message, save
the edited message back to the folder, then bounce that message.
Since I don't use edit-message very often, it didn't occur to me that it
would be difficult to tell the original from the new (edited) message in
the folder. I thought edit-message marked the old message for deletion,
or somesuch. Ah well...
> I've looked at $@. Mutt passes "--", then the address(es), and .muttrc
> includes "-oi -oem" in the sendmail call, so they may be needed (I
> have no idea what they do, and couldn't find them in the sendmail docs
> I have).
Just FYI, "-o" is used to turn on options that can also be enabled with
the "O" command in the sendmail.cf file. The two options are "i"
(ignore a single "." if it appears in the input), and "em" (if there are
errors, report them via E-mail). Without those command-line options, a
message which happens to have a single "." on a line by itself, will
prematurely terminate the message. And if there are delivery problems,
sendmail will try to print errors on your terminal, which wreaks havoc
with curses-based programs like Mutt. So we choose to bounce the error
messages in E-mail instead, and users are accustomed to that, anyway.
> I'll remove the "-t" and use "$@", as you suggest, however I want to
> dump the first argument ("--") first, as it makes premail choke. A
> shift command should handle that, eh?
That would do the trick.
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is no man really clever who has not
Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson
UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Editing a bounced message
Michael Thies <[EMAIL PROTECTED]> wrote on Wed, 13 Oct 1999: > And quit that message without postponing it. .-) Well, if you create a special macro, it's possible to set the $postpone variable temporarily to "no", and restore it to "ask-yes" (or whatever you prefer) after you're finished with edit-message. If you do a lot of message editing, it's probably worthwhile to do this. Just a note... Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / "Managing senior programmers is like herding cats." -- Dave Platt
Re: Editing a bounced message
On 1999-10-12 15:37:27 -0500, David DeSimone wrote: > Seems like it would be just as easy to use edit-message, change the > message around, then when you're done, go ahead and the > resulting edited message. Doesn't sound too difficult, and works with > current code. This depends on the user's need. edit-message requires some knowledge of message formats, MIME, etc, to avoid mistakes. resend-message handles all this for you, and is even able to do some nice things to pgp/mime signed and encrypted messages. I'll look into getting this married with the bounce function soon, but probably not today.
Re: Editing a bounced message
Mikko Hänninen hat ueber "Re: Editing a bounced message" geschrieben: > My guess is this: > > 1. Edit the message you want to bounce (with the edit-message function), > change it to your liking, and use w(write) to write it back to the same > or some other folder. And quit that message without postponing it. .-) > 2. Find that *edited* message (in the same folder, or by changing to > that other folder where you saved it in step 1) and bounce that with > the normal bounce function. thx, that works, but as You mentioned, it is an arghful method .-( Maybe it will be in some future release one feature for mutt. CU -- \o/ Michael Thies --- [EMAIL PROTECTED] Was heißt Zeugnis auf arabisch? - Der-wisch!
Re: Editing a bounced message
Michael Thies <[EMAIL PROTECTED]> wrote on Tue, 12 Oct 1999: > Maybe someone could make it clear to me, what David mean with "and > the resulting editing message" > > How could I bounce that message? Changing the To-Header? My guess is this: 1. Edit the message you want to bounce (with the edit-message function), change it to your liking, and use w(write) to write it back to the same or some other folder. 2. Find that *edited* message (in the same folder, or by changing to that other folder where you saved it in step 1) and bounce that with the normal bounce function. I think that's a bit awkward, but probably works. If you write the message back to the same folder, you may have difficulty in determining which is the original and which is the edited copy. If you save it to some other folder, you need to change there before you can bounce. Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / "It's just a shadow of the people we should be" -- Big Country
Re: Editing a bounced message
On Tue, Oct 12, 1999 at 03:37:27PM -0500, David DeSimone wrote:
> Thomas Roessler <[EMAIL PROTECTED]> wrote:
> >
> > 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.
>
> Seems like it would be just as easy to use edit-message, change the
> message around, then when you're done, go ahead and the
> resulting edited message. Doesn't sound too difficult, and works with
> current code.
Yes, this would be an easy solution, but it doesn't work for me (95.3i).
If the message is edited ("e"), the bounce function is disabled, and "b"
results in a Bcc: query instead of bouncing the message as it normally
would.
> rex <[EMAIL PROTECTED]> wrote:
> >
> > #! /bin/sh
> > # uses ideas from a script by Winfried Szukalski <[EMAIL PROTECTED]>
> > from_file=${HOME}/.sendit_pre
> > to_file=${HOME}/.sendit_post
> > POSTTOOL=/usr/lib/sendmail
> > POSTARGS="-oi -oem -t"
> > EDITARGS="-tmp -f mail_mode"
> > cat > ${from_file}
> > if (grep ^"Resent-From: $USER@" ${from_file})
> > then
> > sed '/Delivered-To: '$USER'@/d' ${from_file} > ${to_file}
> > mv ${to_file} ${from_file}
> > $VISUAL ${from_file} ${EDITARGS}
> > fi
> > ${POSTTOOL} ${POSTARGS} < ${from_file}
> > #rm -f ${from_file}
>
> This doesn't look right. "sendmail -t" is going to read the message's
> headers, and if there are Cc: recipients, they will get a second copy of
> the message sent to them, because of your bounce mechanism.
>
> Mutt passes the recipients to your script, and you should go ahead and
> pass them on to sendmail; then the message will go only to the recipient
> specifies in your command.
I knew there was a reason I didn't like "-t". Thanks.
> POSTARGS should have "-t" removed, and your call to ${POSTTOOL} should
> look like this:
>
> ${POSTTOOL} ${POSTARGS} "$@" < ${from_file}
>
> Actually, Mutt's arguments that it passes to your script might already
> include -oi and -oem, so you probably could forget ${POSTARGS} entirely.
I've looked at $@. Mutt passes "--", then the address(es), and .muttrc
includes "-oi -oem" in the sendmail call, so they may be needed (I
have no idea what they do, and couldn't find them in the sendmail docs
I have).
I'll remove the "-t" and use "$@", as you suggest, however I want to
dump the first argument ("--") first, as it makes premail choke. A
shift command should handle that, eh?
> Having said all that, perhaps you should give and
> another try.
I did, just before writing this. It still doesn't work for me. Does
it work for you?
Thanks,
-rex
Re: Editing a bounced message
David DeSimone hat ueber "Re: Editing a bounced message" geschrieben: > Seems like it would be just as easy to use edit-message, change the > message around, then when you're done, go ahead and the > resulting edited message. Doesn't sound too difficult, and works with > current code. Thats not the way (I think) rex wanted it. And I could need this feature too. If I edit a message and send it, I get a second X-Mailer-Header (mine) and don't have those "resent-from|date|to" Headers in it .-( Maybe someone could make it clear to me, what David mean with "and the resulting editing message" How could I bounce that message? Changing the To-Header? TiA -- \o/ Michael Thies --- [EMAIL PROTECTED] Auf, auf und auf! Laßt uns von Tonne zu Tonne eilen! Wir wollen dem Müll eine Abfuhr erteilen! Heinz Erhardt
Re: Editing a bounced message
Thomas Roessler <[EMAIL PROTECTED]> wrote:
>
> 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.
Seems like it would be just as easy to use edit-message, change the
message around, then when you're done, go ahead and the
resulting edited message. Doesn't sound too difficult, and works with
current code.
rex <[EMAIL PROTECTED]> wrote:
>
> #! /bin/sh
> # uses ideas from a script by Winfried Szukalski <[EMAIL PROTECTED]>
> from_file=${HOME}/.sendit_pre
> to_file=${HOME}/.sendit_post
> POSTTOOL=/usr/lib/sendmail
> POSTARGS="-oi -oem -t"
> EDITARGS="-tmp -f mail_mode"
> cat > ${from_file}
> if (grep ^"Resent-From: $USER@" ${from_file})
> then
> sed '/Delivered-To: '$USER'@/d' ${from_file} > ${to_file}
> mv ${to_file} ${from_file}
> $VISUAL ${from_file} ${EDITARGS}
> fi
> ${POSTTOOL} ${POSTARGS} < ${from_file}
> #rm -f ${from_file}
This doesn't look right. "sendmail -t" is going to read the message's
headers, and if there are Cc: recipients, they will get a second copy of
the message sent to them, because of your bounce mechanism.
> I am concerned that by calling sendmail with the "-t" option instead
> of passing parameters as Mutt does I may be causing a problem that
> hasn't shown up yet.
Mutt passes the recipients to your script, and you should go ahead and
pass them on to sendmail; then the message will go only to the recipient
specifies in your command.
POSTARGS should have "-t" removed, and your call to ${POSTTOOL} should
look like this:
${POSTTOOL} ${POSTARGS} "$@" < ${from_file}
Actually, Mutt's arguments that it passes to your script might already
include -oi and -oem, so you probably could forget ${POSTARGS} entirely.
Having said all that, perhaps you should give and
another try.
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is no man really clever who has not
Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson
UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Editing a bounced message
On Tue, Oct 12, 1999 at 09:52:44AM +0200, Thomas Roessler wrote:
> 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?
Thanks for the response.
LISTSERV(tm) has a moderation option that sends messages to be posted
to the editor for approval. Approval requires that the MUA insert
"Resent-From: the_editor", and "Resent-To: the_list" header lines and
to leave the "From: ..." line as is. Mutt does this when a message is
"bounced", but it does not offer the opportunity to edit the bounced
message. However, with the help of members of this list, I've now got
a shell script that allows editing after bounce is selected. Normally,
it simply calls sendmail. However, if a message is bounced, the
presence of "Resent-From: the_editor" in the headers results in a call
to an editor so any excess quoting, etc., can be fixed. Since there
may be a large number of messages to be approved that need no editing,
minimizing the number of keystrokes is important, and this solution
does that. All that's required is "b", the alias for the list address,
"Enter" to confirm, and the editor exit key(s). Here's the current
version of the script "bounce":
(.muttrc has set sendmail="/home/rex/bin/bounce")
#! /bin/sh
# uses ideas from a script by Winfried Szukalski <[EMAIL PROTECTED]>
from_file=${HOME}/.sendit_pre
to_file=${HOME}/.sendit_post
POSTTOOL=/usr/lib/sendmail
POSTARGS="-oi -oem -t"
EDITARGS="-tmp -f mail_mode"
cat > ${from_file}
if (grep ^"Resent-From: $USER@" ${from_file})
then
sed '/Delivered-To: '$USER'@/d' ${from_file} > ${to_file}
mv ${to_file} ${from_file}
$VISUAL ${from_file} ${EDITARGS}
fi
${POSTTOOL} ${POSTARGS} < ${from_file}
#rm -f ${from_file}
This seems like a reasonable solution that doesn't require adding code
to Mutt. I am concerned that by calling sendmail with the "-t" option
instead of passing parameters as Mutt does I may be causing a problem
that hasn't shown up yet. OTOH, perhaps the only reason for Mutt's
passing parameters is to pass "--" (which I do not need or want).
Regards,
-rex
Re: Editing a bounced message
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)
>
Re: Editing a bounced message
On Mon, Oct 11, 1999 at 07:07:32AM +, winfried szukalski wrote:
> I use the script you are looking for together with
[...]
Thanks much, Winfried. I have adapted your script to call the editor
only when the message is bounced. The script resides in /home/rex/bin
and is named "bounce." .muttrc has
set sendmail="/home/rex/bin/bounce"
#=> bounce <
#! /bin/sh
# adapted from a script by Winfried Szukalski <[EMAIL PROTECTED]>
# allows editing a bounced ("b") message before sending it.
from_file=${HOME}/.sendit_pre
POSTTOOL=/usr/lib/sendmail
POSTARGS="-oi -oem -t"
cat > ${from_file}
if (grep "Resent-From: $USER@" ${from_file})
then
$VISUAL ${from_file}
fi
${POSTTOOL} ${POSTARGS} < ${from_file}
rm -f ${from_file}
#> end bounce <=
In normal use, bounce is transparent. If a message is bounced, the
presence of "Resent-From: [EMAIL PROTECTED]" in the header triggers the
"if (grep ..." and my editor (XJed) opens the message.
The ability to edit a bounced message is very useful for listowners
using LISTSERV(tm) for moderated lists.
-rex
Re: Editing a bounced message
Op zo. 10 okt 1999 14:54:21 zei rex: > 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. man sendmail(1): With no flags, sendmail reads its standard input up to an end-of-file or a line consisting only of a single dot and sends a copy of the message found there to all of the addresses listed. It determines the network(s) to use based on the syntax and contents of the addresses. > The line in .muttrc is > set sendmail="usr/lib/sendmail -oi -oem" > I can't find any docs on what "-oi" and "-oem" do. man sendmail(1): There are also a number of processing options that may be set. Normally these will only be used by a system administrator. Options may be set either on the command line using the -o flag (for short names), the -O flag (for long names), or in the configuration file. I don't know what these two options do, you'can try taking a peek in /etc/mail/sendmail.conf (comment-documented configuration file). So what I suggest your script does is: - redirect stdin of your script into a temp file. - vi the tempfile - redirect sendmail's stdin from the tempfile - remove the tempfile best of luck, stasinos
Re: Editing a bounced message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello, rex <[EMAIL PROTECTED]>,
I use the script you are looking for together with
the naive and clueless PINE. PINE allows in '.pinerc'
to configure a:
sendmail-path=/usr/local/sbin/sendit.sh
In '.muttrc' I use:
set sendmail="/usr/local/sbin/sendit.sh"
I use this script to delete the 'root' from the header
of my mail to satisfy the sysadmin of 'uni-mainz.de'.
The script is still under construction:
- ---
#! /bin/sh
#
# $Id:$
#
#T H EP I N EM A I L S Y S T E M
#
# Mike Seibel
# Networks and Distributed Computing
# Computing and Communications
# University of Washington
# Administration Building, AG-44
# Seattle, Washington, 98195, USA
# Internet: [EMAIL PROTECTED]
#
# Please address all bugs and comments to "[EMAIL PROTECTED]"
#
#
# Pine and Pico are registered trademarks of the University of
Washington.
# No commercial use of these trademarks may be made without prior
written
# permission of the University of Washington.
#
# Pine, Pico, and Pilot software and its included text are Copyright
# 1989-1996 by the University of Washington.
#
# The full text of our legal notices is contained in the file called
# CPYRIGHT, included with this distribution.
#
#
# Simple script to expedite mail posting at the expense of timely
# error reporting and 8BITMIME support.
#
# NOTE: If for any reason POSTFILE below is created on an nfs mounted
# file system, the trap statement below must get removed or
# altered, and the last line must get replaced with:
#
# ( ${POSTTOOL} ${POSTARGS} < ${POSTFILE} ; rm -f ${POSTFILE} ) &
#
###POSTFILE=/tmp/send$$
###POSTTOOL=/usr/lib/sendmail
###POSTARGS="-oi -oem -t"
###
###umask 077
###trap "rm -f ${POSTFILE}; exit 0" 0 1 2 13 15
###
###cat > ${POSTFILE}
###${POSTTOOL} ${POSTARGS} < ${POSTFILE} &
the above originates from PINE ##
to_file=${HOME}/.sendit_post
from_file=${HOME}/.sendit_pre
args_file=${HOME}/.sendit_args
POSTTOOL=/usr/sbin/sendmail
POSTARGS="-oi -oem -t -B8BITMIME -f [EMAIL PROTECTED]"
any_args=$*
echo $any_args > ${args_file}
cat > ${from_file}
cat ${from_file} \
| /usr/bin/sed -e "s/From: winfried szukalski <[EMAIL PROTECTED]/From:
|winfried szukalski
<[EMAIL PROTECTED]/g" \
| /usr/bin/sed -e "s/Sender: szukw000@localhost/Sender: szukw000@localhost/g"
\
| /usr/bin/sed -e "s/Sender: szukw000@localhost/Sender: szukw000@localhost/g"
\
| /usr/bin/sed -e "s/@localhost/@localhost/g" \
| /usr/bin/sed -e "s/From: winfried szukalski <[EMAIL PROTECTED]>/From:
|winfried szukalski
<[EMAIL PROTECTED]>/g" > ${to_file}
${POSTTOOL} ${POSTARGS} < ${to_file} &
#rm -f ${from_file} ${to_file} ${args_file}
- - ~/.sendit_pre --
Date: Mon, 11 Oct 1999 06:22:58 +
From: winfried szukalski <[EMAIL PROTECTED]>
To: szukw000@localhost
Subject: sendit.sh instead of sendmail
Message-ID: <19991011062258.A12860@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
test
- - ~/.sendit_post --
Date: Mon, 11 Oct 1999 06:22:58 +
From: winfried szukalski <[EMAIL PROTECTED]>
To: szukw000@localhost
Subject: sendit.sh instead of sendmail
Message-ID: <19991011062258.A12860@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
test
- --
As you can see: it works with 'mutt-1.0pre3i'.
The 'sendmail' I use is the one of POSTFIX:
-t Extract recipients from message headers. This
requires that no recipients be specified on the
command line.
-f sender
Set the envelope sender address. This is the
address where delivery problems are sent to, unless
the message contains an Errors-To: message header.
Options '-oi -oem' seem to be silently ignored.
winfried
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: Made with pgp4pine 1.62
iEYEARECAAYFAjgBjMIACgkQdoAGL0q6k7pDrgCfYYPHRlC+wfTIoCg+tiGYi/Ro
5DsAn111AwLbDgiqW+6naYNP3igzo6qJ
=ubji
-END PGP SIGNATURE-
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)
Re: Editing a bounced message
rex [[EMAIL PROTECTED]] wrote: > I host a moderated list using LISTSERV(tm), and have a frequent need > to trim off excess quoting and other detritus from messages submitted > for approval before bouncing them to the list. Unfortunately, Mutt's > bounce does not offer any opportunity to do this. > > Forwarding to the list works, but is quite awkward because it requires > changing the "From: ..." line, adding "Resent-From: rex@ptw", and > removing all the lines forwarding adds. > > The (I think) ideal solution would be for Mutt to offer the option to > edit the message after "bounce" is selected. Eudora offers this feature. > Surely Mutt should also. ;) 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. -- Jeremy Blosser | [EMAIL PROTECTED] | http://jblosser.firinn.org/ -+-+-- "If Microsoft can change and compete on quality, I've won." -- L. Torvalds PGP signature
Editing a bounced message
I host a moderated list using LISTSERV(tm), and have a frequent need to trim off excess quoting and other detritus from messages submitted for approval before bouncing them to the list. Unfortunately, Mutt's bounce does not offer any opportunity to do this. Forwarding to the list works, but is quite awkward because it requires changing the "From: ..." line, adding "Resent-From: rex@ptw", and removing all the lines forwarding adds. The (I think) ideal solution would be for Mutt to offer the option to edit the message after "bounce" is selected. Eudora offers this feature. Surely Mutt should also. ;) TIA for any pointers. -rex
