|
Sender: |
|
Date: |
Tue, 9 Nov 2004 14:56:10 -0500 |
Reply-To: |
|
Content-Transfer-Encoding: |
7bit |
Subject: |
|
From: |
|
Content-Type: |
text/plain; charset=ISO-8859-1; format=flowed |
In-Reply-To: |
|
Organization: |
University of Notre Dame |
MIME-Version: |
1.0 |
On 11/9/2004 2:08 PM, Valdis Kletnieks wrote:
>
> Incidentally, any software that complains about trailing trash breaking
> a digital signature needs to read RFC2046, section 5.1:
...
> Similarly, top banners should end up being "silently swallowed", as they
> fall into the "preamble" area. RFC2046, section 5.1, says:
...
> I have to say that making a change to Listserv to work around non-RFC-compliant brain-damage
> in other software is a Bad Idea...
LISTSERV is simply shoving the banner text into the message body, rather than
adding it to the message package as a separate MIME part. This would not
resolve the S/MIME problem, but it would resolve some other banner-related
problems.
If S/MIME support is a critical requirement for your MLM, you may want to
look at Sympa <http://sympa.org/>.
--
Paul Russell
Senior Systems Administrator
OIT Messaging Services Team
University of Notre Dame
|
|
|