Great Circle Associates Majordomo-Workers
(August 2002)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: fronters/footers idea
From: Daniel Liston <dliston @ sonny . org>
Date: Sat, 31 Aug 2002 19:43:47 -0500
To: majordomo-workers @ greatcircle . com
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0rc2) Gecko/20020618 Netscape/7.0b1


I am not sure if anyone still uses this list :) but I have a
"what if" idea for dealing with MIME content messages when a
list utilizes fronters or footers.  I know we want to convince
users to stick to plain text, but as someone mentioned on the
-users list, MIME will not be going away, and we need to deal
with it.  Does anyone think it is worth the effort during the
body/header parsing to add this kind of logic?

If header_content_type m/multipart/i
boundary = split('=', whatever goes here)
fi

inserting a fronter would become
if boundary
--$boundary
Content-Type: text/plain
<blank line>
fi
$fronter

Inserting/appending a footer would become
if boundary
$_ =~ s/--$boundary--/--$boundary/
Content-Type: text/plain
<blank line>
fi
$footer
if boundary
--$boundary--
fi

In other words, to quote from someone on the mailman list,
if a message has MIME parts and the header/footer is going
to be added, the message should be transformed into a
mulitpart/mixed with the header and footer added as text/plain
parts.

Is my logic above over simplified?

Dan Liston





Follow-Ups:
Indexed By Date Previous: config-test.0 patch
From: Daniel Liston <dliston@sonny.org>
Next: Re: fronters/footers idea
From: Jason L Tibbitts III <tibbs@math.uh.edu>
Indexed By Thread Previous: config-test.0 patch
From: Daniel Liston <dliston@sonny.org>
Next: Re: fronters/footers idea
From: Jason L Tibbitts III <tibbs@math.uh.edu>

Google
 
Search Internet Search www.greatcircle.com