We have macs running quickmail (a lovely product, ugh) which are
supposedly going to be using majordomo. The problem is that quickmail
is dumb and doesn't seem to clean up things like the quickmail subject
and timestamps, so they end up in the body of a message and majordomo
tries to process them.
Here's enough of what a quick mail message looks like:
-------------
Return-Path: <Person_name@host.sps.mot.com>
Date: 27 Sep 1993 13:34:48 U
Subject: email list server . . .
To: "majordomo" <majordomo@risc>
Subject: Time:1:30 PM
OFFICE MEMO email list server . . .
Date:9/27/93
Actual commands end up here ... "which", etc.
--------------
As you can guess "majordomo" tries to process the lines like:
Subject: Time:1:30
and the user gets a help message for each line.
This is very ugly. Has anyone handled this situation already
and have some suggestions on what to do?
Short of blowing up quickmail or the macs (either one I'd gladly do,
but they are here to stay), I've thought about slurping up lines until
I get to a valid majordomo command and ignoring everything before that.
This includes not sending a help message on those ignored lines. One
help message could be sent if no valid commands were processed in the
whole message.
John Rouillard suggested:
How about an explict "BEGIN" line like we have an explicit END line.
At least it keeps thing symmetric. The only problem is that the output
to the REPLY pipeline has to be deferred until a begin line is seen.
Once the begin line is seen the output is cleared, and everything else
is sent to the user.
comments and ideas are appreciated,
jennifer
--
Jennifer Joy sys/net admin Motorola/RISC HW Austin,TX
jjoy@risc.sps.mot.com 512.891.8561 pgr:928.7447 #9561
Follow-Ups:
|
|
