>No, it always was in band - the 4-SOH sequence was searched for in all >lines of the message, and SOH has always been a possible character in >e-mail. Just even more unlikely years ago than it is now.
You know, I _was_ going to disagree here but Robert is, as he almost always is, 100% correct. 4-SOH is not valid in an email HEADER (mostly), but it is certainly valid in a message BODY, and this goes all the way back to RFC 822. There were some minor changes along the way (RFC 822 said NULs were valid, but RFC 2822 said they were not), but SOH has always been a valid character in email bodies; MIME didn't change this one bit. --Ken _______________________________________________ Nmh-workers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/nmh-workers
