On Sat, 13 Apr 1996, Marc G. Fournier wrote:
>
> First off, is there a newer version of Majordomo available currently?
> I've checked the FAQ and 1.94 is in Alpha, according to it...any ETA?
None that I know of, although I do have 1.94a3 finally running
more or less smoothly on post.io.org. The 1.94 resend doesn't work
for moderated lists, and I beat me head against the wall for a few
hours before I figured out that using the 1.93 resend just for the
moderated lists is a workable kludge.
> ----[ begin of moderated message ]----
>
> Received: (from majordom@localhost) by ki.net (8.7.4/8.7.4) id OAA00650 for
> netnotify-outgoing; Sat, 13 Apr 1996 14:19:43 -0400 (EDT)
> Date: Sat, 13 Apr 1996 14:19:43 -0400 (EDT)
> From: owner-netnotify
> Message-Id: <199604131819.OAA00650@ki.net>
> X-Authentication-Warning: ki.net: majordom set sender to owner-netnotify using
> -f
>
> this is a moderated list
> Sender: owner-netnotify
>
> ----[ end of moderated message ]----
This appears to be a problem if you put the "Approved:" header as
the first line of the body rather than inside the header block.
You'll notice that resend incorrectly rewrites some headers after the
text of the message (the Sender header, in this case).
The problem is more obvious if you send an approved message
consisting of more than one paragraph. From what I remember of the
problem, all text up to the first blank line *after* the blank line
that separates the Approved: line from the rest of the message is
included in the header block.
I didn't notice this problem until recently since I always use a
proper Approved header, rather than an Approved line in the message
body.
--
Brian Tao (BT300, taob@io.org)
Systems and Network Administrator, Internex Online Inc.
"Though this be madness, yet there is method in't"
Follow-Ups:
References:
|
|
