IMAP MIME boundary life -

IMAP MIME boundary life -

between rfc imap, rfc mime format of net message bodies , rfc mime media types can not see explicitly said life of mime boundaries. mime boundary part of message have remain unchanged long message exists?

i have looked @ how clever net suite implemented imap server, , seems boundary generated (and re-generated) on fly, i.e. separate commands executed against same mailbox different boundaries same parts of same message. meaning if request boundary part of bodystructure , retrieve body parts later may receive body parts different boundaries indicated in bodystructure request.

does mime boundary part of message have remain unchanged long message exists?

yes.

and seems boundary generated (and re-generated) on fly, i.e. separate commands executed against same mailbox different boundaries same parts of same message.

that horribly broken.

part of bodystructure response content-type parameter values of boundary 1 of them. cannot go changing between sessions, never mind between commands.

one of reasons boundary cannot regenerated on fly multipart/signed parts, in order verify digital signature, need serialize kid tree byte-for-byte way when got signed or, obviously, fail verify.

imap mime