Re: Suggested Requirements for Multi-part Multi-Structured 822 Encoding

["Ned Freed, Postmaster" <NED@xxxxxxxxxxxxxxxxxxxx>]

This is addressed in our draft RFC. Unique token separators are used by
smart software. They are easy to parse, highly resistant to damage, and
fairly easy to generate. RFC934 mode is retained both for backwards
compatibility and to provide a simpler form to generate. As the discussion
has progressed I'm less in favor of retaining the RFC934 mode and more
in favor of just using unique tokens. I've grown convinced that they are
easier to generate, even by hand (make one up and then search your files
for any occurences; any text editor should be able to do that), than I
originally thought, and are truly the only viable option when it comes
to surmounting the known types of damage messages suffer.

				Ned