>>>>> "LB" == Lars Bungum <firstname.lastname@example.org> writes:
LB> When the mail bounces to the approval address afterwards, the mail
LB> client does not present a mail with attachements, but one long message
LB> with a lot of UUCODE in the bottom.
That depends on the message; if there was a base64 encoded part then it
will look like that, yes.
LB> Didn`t someone speak about aprroving throug the subject field?
The development version allows something like this. When the owner is
consulted about a message (the messages now say 'CONSULT' instead of
'BOUNCE' because the latter has too many other connotations) the subject
includes a string of digits and the original message is included as a
message/rfc822 attachment. This means that MIME-aware clients can see the
message no matter how it was encoded and non-MIME-aware clients are no
To approve the message, just reply to it and put 'accept' in the body. Or
click on one of the URLs you see in the approval message. Or you can
approve it in the usual way, except that we allow the Approve: line to be
in any number of additional places (in the header, first line of message,
first line of the prologue, first line of the first body part, or in a
separate MIME part with the message to be approved as an attachment).
Some information about the development version is at
http://www.hpc.uh.edu/majordomo/. Discussion is ongoing on
email@example.com. The software is working but is
considered to be alpha quality.