Sorry if this has been discussed, I haven't followed any threads on MIME.
Anyhow, as you can see, it's trying to interpret my signature instead of
using the dashes as an end. Could this be because Pine inserts MIME
headers into every message it sends? I remember this problem in 1.94
something, and we decided it was bad behavior and issued a patch to change
it.
Thanks,
----------------------------------
| Brock Rozen | brozen@torah.org |
----------------------------------
---------- Forwarded message ----------
Return-Path: <owner-majordomo@test.torah.org>
Received: from neviim.neviim.torah.org (bin@localhost [127.0.0.1])
by neviim.torah.org (8.8.8/8.8.8) with SMTP id OAA29695
for <brozen@torah.org>; Sun, 3 May 1998 14:39:51 -0400
Date: Sun, 3 May 1998 14:39:51 -0400
Message-Id: <199805031839.OAA29695@neviim.torah.org>
Content-Type: text/plain
Content-Disposition: inline
Content-Description: Results from toplevel
Mime-Version: 1.0
To: Brock Rozen <brozen@torah.org>
Subject: Majordomo results: Re: Majordomo results: Re: Majordomo res
From: majordomo@test.torah.org
>>>> lists
There are no lists.
>>>> ----------------------------------
**** Illegal command!
1 valid command processed; it was successful.
Follow-Ups:
|
|
