Content-Type: multipart/alternative; charset="ISO-8859-1"; boundary="This_is_the_boundary_hip_ho"
Yep, seen stuff like this before in Apple mailings. Why oh why do people insist on generating such horribly long and ugly boundary strings? It serves no purpose.
Things haven't changed dramatically, but we're on
2046 now (it's spread across 2045 thru 2049).
specifies only that the boundary string should be no more than length 70, not end with a space, consist of these characters: space A-Z a-z 0-9 ' ( ) + _ , - . / : ? and be a string that another e-mail encoder is unlikely to choose (to avoid random collisions with nested/forwarded messages).
...and that's the concept that results in big ugly useless boundaries. It's sufficient to make sure the boundary doesn't appear in the body parts. If each mailer performs this check, there's no need to worry about what other mailers might do, and the planet can be rescued from the plague of big ugly boundary strings!
Looks like Apple was having a little fun here!
I want a written apology from Apple, and five million trillion dollars in compensation for the trauma. Then I'm going to buy IBM and make someone answer for SGML.