Windows Vista Forums

multipart/signed RFC 1847 Compliance

  1. #1


    Josh Guest

    multipart/signed RFC 1847 Compliance

    I have a question about multipart/signed message handling in Vista's
    Windows Mail application pursuant to RFC 1847 section 2.1. When Windows
    Mail receives a message in multipart/signed format with just the 2 body
    parts specified in the RFC, Windows Mail does not display the body text
    in the message and instead puts the entire body into a text file that
    appears to be named ATT#####.txt where the #'s are numbers, such as
    00013. However, when I alter the message so that inside the
    multipart/signed message is multipart/alternative nested MIME
    formatting, Windows Mail does correctly display the HTML version of the
    message.

    I have several questions:

    Why does Windows Mail not correctly display the message body when a
    standard multipart/signed MIME format is used? (The message is instead
    displayed as a .txt attachment with a blank message body.)

    Why does it display correctly when another multipart/alternative MIME
    body appears beneath the multipart/signed body? (In this case the HTML
    alternative message body is displayed as expected.)

    Is there any way to get Windows Mail to display the body correctly when
    only the multipart/signed MIME formatting is used?

      My System SpecsSystem Spec

  2.   


  3. #2


    Steve Cochran Guest

    Re: multipart/signed RFC 1847 Compliance

    I don't think you can fix it. Its probably a bug. You can try saving the
    message and then renaming it to give it a mht file extension and then it
    will open in IE. I don't know what the result will be.

    steve

    "Josh" <pekster-news@usa.net> wrote in message
    news:R-ydnWxx0JW1dTHbnZ2dnUVZ_sqinZ2d@comcast.com...
    >I have a question about multipart/signed message handling in Vista's
    > Windows Mail application pursuant to RFC 1847 section 2.1. When Windows
    > Mail receives a message in multipart/signed format with just the 2 body
    > parts specified in the RFC, Windows Mail does not display the body text
    > in the message and instead puts the entire body into a text file that
    > appears to be named ATT#####.txt where the #'s are numbers, such as
    > 00013. However, when I alter the message so that inside the
    > multipart/signed message is multipart/alternative nested MIME
    > formatting, Windows Mail does correctly display the HTML version of the
    > message.
    >
    > I have several questions:
    >
    > Why does Windows Mail not correctly display the message body when a
    > standard multipart/signed MIME format is used? (The message is instead
    > displayed as a .txt attachment with a blank message body.)
    >
    > Why does it display correctly when another multipart/alternative MIME
    > body appears beneath the multipart/signed body? (In this case the HTML
    > alternative message body is displayed as expected.)
    >
    > Is there any way to get Windows Mail to display the body correctly when
    > only the multipart/signed MIME formatting is used?



      My System SpecsSystem Spec

  4. #3



    Newbie
    Join Date : Jun 2009
    Posts : 2
    none
    Local Time: 10:18 PM


     

    Re: multipart/signed RFC 1847 Compliance

    It is a bug. Has been a bug since the inception of Outlook Express over 10 years ago.

      My System SpecsSystem Spec

  5. #4



    Newbie
    Join Date : Jun 2009
    Posts : 2
    none
    Local Time: 10:18 PM


     

    Re: multipart/signed RFC 1847 Compliance

    Quote Originally Posted by Steve Cochran View Post
    I don't think you can fix it. Its probably a bug. You can try saving the
    message and then renaming it to give it a mht file extension and then it
    will open in IE. I don't know what the result will be.

    steve

    "Josh" <pekster-news@usa.net> wrote in message
    news:R-ydnWxx0JW1dTHbnZ2dnUVZ_sqinZ2d@comcast.com...
    >I have a question about multipart/signed message handling in Vista's
    > Windows Mail application pursuant to RFC 1847 section 2.1. When Windows
    > Mail receives a message in multipart/signed format with just the 2 body
    > parts specified in the RFC, Windows Mail does not display the body text
    > in the message and instead puts the entire body into a text file that
    > appears to be named ATT#####.txt where the #'s are numbers, such as
    > 00013. However, when I alter the message so that inside the
    > multipart/signed message is multipart/alternative nested MIME
    > formatting, Windows Mail does correctly display the HTML version of the
    > message.
    >
    > I have several questions:
    >
    > Why does Windows Mail not correctly display the message body when a
    > standard multipart/signed MIME format is used? (The message is instead
    > displayed as a .txt attachment with a blank message body.)
    >
    > Why does it display correctly when another multipart/alternative MIME
    > body appears beneath the multipart/signed body? (In this case the HTML
    > alternative message body is displayed as expected.)
    >
    > Is there any way to get Windows Mail to display the body correctly when
    > only the multipart/signed MIME formatting is used?
    All versions of any mail product by MS have this problem.

      My System SpecsSystem Spec

  6. #5


    David Gravereaux Guest

    Re: multipart/signed RFC 1847 Compliance

    Just for fun, this is an example of OpenPGP/MIME. It can not be viewed
    inline by any MS mail product.


    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.9 (GNU/Linux)

    iEYEARECAAYFAkpAA5oACgkQlZadkQh/RmFmkQCfe3AUF63X/DkyTlaTBRWu9+8O
    BSUAnRNt7Hu7Q1L9jje9h/CY9w+aPCDp
    =/E+S
    -----END PGP SIGNATURE-----


      My System SpecsSystem Spec

  7. #6


    David Gravereaux Guest

    Re: multipart/signed RFC 1847 Compliance

    Here's an example with S/MIME. Both the OpenPGP/MIME signed message and
    this S/MIME one use 'multipart/signed' [RFC1847] (listed as "MIME-Encyp"
    in RFC5000 "Internet Official Protocol Standards" 5/2008) as the MIME
    type, but only this post is viewable by the MS mail products.


      My System SpecsSystem Spec


multipart/signed RFC 1847 Compliance
Similar Threads
Thread Forum
RFC 1847 (MIME_cryp) support is not working correctly Live Mail
Multipart messages not decoding properly Live Mail
Transmit Multipart data with part being binary VB Script
windows mail and multipart messages Vista General
Re: windows mail and multipart messages Vista mail