Re: MIME boundary strings

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Thu, 22 August 2002 11:20 UTC

Message-ID: <AhNFVsj9hZKsigvgZmJFog.md5@melkebalanse.gulbrandsen.priv.no>
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Jacob Palme <jpalme@dsv.su.se>
Subject: Re: MIME boundary strings
Cc: ietf-822@imc.org
References: <p0510033db98a5c7c98f8@[192.168.100.100]> </BLSH2pUcq+8GtjI1MFhyQ.md5@melkebalanse.gulbrandsen.priv. no> <p0510034cb98a750b5df8@[192.168.100.100]>
In-Reply-To: <p0510034cb98a750b5df8@[192.168.100.100]>
Content-Type: text/plain; format="flowed"
MIME-Version: 1.0
Date: Thu, 22 Aug 2002 16:50:05 +0530
Sender: owner-ietf-822@mail.imc.org
Precedence: bulk

That's one possible strategy. There are three that I know of:

a) if using quoted-printable, quote something.
b) if using format=flowed, rewrap differently
c) if nothing else helps, use base64 for that body-part

Basically, the boundary strings should be treated like "From " or ".". A 
good MUA avoids those strings at the beginnings of lines. IMO, avoiding 
n strings isn't harder than avoiding 2.

A good MUA also quotes properly, which I can't right now ;) Sorry about 
that.

--Arnt

Re: MIME boundary strings Russ Allbery
Re: MIME boundary strings Adrian 'Dagurashibanipal' von Bidder
Re: MIME boundary strings Russ Allbery
Re: MIME boundary strings Marc Mutz
Re: MIME boundary strings Arnt Gulbrandsen
Re: MIME boundary strings Jacob Palme
Re: MIME boundary strings Arnt Gulbrandsen
MIME boundary strings Jacob Palme