[kde] Re: RFC question
- From: "Boyd Stephen Smith Jr." <bss@xxxxxxxxxxxxxxxxx>
- Date: Wed, 10 Nov 2010 12:15:27 -0600
In <201011101225.05209.gheskett@xxxxxxxx>, gene heskett wrote:
Greetings;
Is it 'legal' for a single MIME'd message containing many parts, to re-
specify the
boundary=string
more than once in the same message?
It is possible to "nest" multipart/* types--same or different. Each of these
must specify the boundary= option AND each boundary must be different.
So the structure of a message is allowed to look like this (IIRC):
+ multipart/alternative (a)
+ multipart/yowsa (b)
+ vendor/wonka
+ image/omgwtfbbq
+ multipart/alternative (c)
+ image/mng
+ image/gif
+ image/png
+ multipart/mixed (d)
+ text/html
+ image/jpeg
+ text/plain
So, each of the multipart/* objects (a-d) would have a different boundary
setting.
This question generated by a windows email agent that is doing that as it
sends me stuff, and in order to see the full message I find I must enable
the message structure viewpane, and then click on the html subtree before I
can see the whole message's jpegs etc. Otherwise nothing below the 2nd
boundary= statement is visible.
I've seen that stuff. I doubt those messages are using a standardized format,
but KMail should try and be better about that, providing the normal "click
here to view HTML" option.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss@xxxxxxxxxxxxxxxxx ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/ \_/
Attachment:
signature.asc
Description: This is a digitally signed message part.
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
- Follow-Ups:
- [kde] Re: RFC question
- From: gene heskett
- [kde] Re: RFC question
- References:
- [kde] RFC question
- From: gene heskett
- [kde] RFC question
- Prev by Date: [kde] RFC question
- Next by Date: [kde] Re: RFC question
- Previous by thread: [kde] RFC question
- Next by thread: [kde] Re: RFC question
- Index(es):