Jason L Tibbitts III wrote:
> This is confusing; unless your code has been modified, it includes every
> byte of the original message as received by resend. At this level, MIME is
> irrelevant; you're being asked to approve the stream of bytes that was
> passed from the MTA.
MIME's relevant in that my mailer needs to be able to parse the message in
order for me to read (and approve) it. And since I work exclusively from a
mailer (generally Pine or Netscape) and not from a UNIX shell, I don't have
the approve script. This means that if I hit "forward", the message won't
arrive with attachments intact.
> Not that I know of, although you can try adding the following two headers
> to the end of the send_bounce routine in resend:
> MIME-Version: 1.0
> Content-Type: message/rfc822
> You may also add an encoding or charset. Experiment a bit. This does
> essentially what Majordomo2 in its current alpha state does: send the body
> as a message/rfc822. The result to a non-MIME-aware MUA just the same as
> before, and a MIME-aware MUA can at least show you the contents. The
> approve script doesn't care either way; all it cares about is the Subject:
> and everything after the first blank.
Thanks, this helps out a bit.
I guess what I really want is an easy way to just forward a message back to
Majordomo with my approval and have it strip out my headers and send out the
message as it originally came in. Is Majordomo supposed to act this way, and
I'm just forwarding wrong?