1 2 Previous Next 10 Replies Latest reply: Feb 23, 2015 7:29 AM by Brad McGarr RSS

    Mcafee SAAS Secure email coming through as mime base64 encodded junk

    miedaner

      Hi,

       

      We are receiving emails from a Mcafee SAAS Email service user that is not readable.

       

      Users see mime encoded message.

       

      Any idea what the fix for this is?

       

      Thanks.

       

       

       

       

        • 1. Re: Mcafee SAAS Secure email coming through as mime base64 encodded junk
          Ex_Brit

          Moved provisionally from Community Help to SaaS Email Security for better support.

          • 2. Re: Mcafee SAAS Secure email coming through as mime base64 encodded junk
            kwidhalm

            miedaner,

             

            I appologize for the delay in response to your inquiry.  Are you still experiencing this issue?  If yes, please contact support so we can take a look at this issue and try to come to resolution for you.

             

            At minimum, we will need the To/From/Date/Subject information for one of the messages in question.

             

            Best Regards,

             

            Karen W.

            System Support Specialist

            McAfee SaaS Email and Web Security Technical Support

            • 3. Re: Mcafee SAAS Secure email coming through as mime base64 encodded junk
              big_mike

              I actually had the same error this week and received a responce from McAfee, this should help out:

               

              The issue is actually on the recipient side. Something on the recipient server is truncating, removing or not interpreting the boundary and multipart sections, so it looks all garbled ( I suspect something with the TNEF- Transport Neutral Encapsulation Format). Without the 'boundary' definition & the multipart specification, there is no way that the mail client can decipher the message.

               

              This can be seen 2 ways.

               

              1 - The same message can be sent to other client and is not garbled.

               

               

              2. If you look at the encoding, it is listed as base64. If I take a portion of the encrypted message and run it through a base 64 decoder (IE- http://www.base64decode.org/) it is shown just fine.

               

              The issue is that the recipient server is truncating, removing or not interpreting the boundary and multipart sections, so it looks all garbled ( I suspect something with the TNEF- Transport Neutral Encapsulation Format).  Without the 'boundary' definition & the multipart specification, there is no way that the mail client can decipher the message.

               

               

              Hope this helps!

              • 4. Re: Mcafee SAAS Secure email coming through as mime base64 encodded junk
                bob_a_hay

                I an having what I think is the same issue. A customer is getting the multipart/alternative raw message as an alert to log into the portal. The actual base64 content can manually be decoded correcty as described here.

                 

                We have found that the issue is with boundary tag within the automated email alert is 71 chars long and the RFC standard states it can not be longer then 70 chars. The customer started seeing the issue when they put in place a new Oracle Messaging Server that is enforcing the 70 char standard and trashing boundary so it is not decoded.  

                 

                As you can see from the snippet below that the boundary within the quotes is 71 chars.

                 

                 

                Not sure how to get this information to someone at McAfee that can look into this. Hopefully someone will read this and pass it along. Otherwise I maybe forced to change vendors for our secure emails. 

                 

                 

                 

                MIME-Version: 1.0

                Content-Type: multipart/alternative;

                  boundary="--=_NextPart_21a1_0fee_6fa4e6e3_a635_11e3_ae0d_0017a477901c_alternative"

                 

                This is a multi-part alternative message in MIME format.

                 

                ----=_NextPart_21a1_0fee_6fa4e6e3_a635_11e3_ae0d_0017a477901c_alternative

                Content-Type: text/plain;

                  charset="utf-8"

                Content-Transfer-Encoding: base64

                 

                WW91IGhhdmUgYSBTZWN1cmUgV2ViIE1haWwgbWVzc2FnZSBmcm9tIGJoYXlAbW5nbGFiLmNvbSB3

                YWl0aW5nIHRvIGJlIHJlYWQuIFRoZSBtZXNzYWdlIHdpbGwgZXhwaXJlIGluIDMwIGRheXMuCgpB

                Y2Nlc3MgeW91ciBTZWN1cmUgV2ViIE1haWwgYWNjb3VudCBodHRwczovL0NlbnRlcnBvaW50LnBv

                cnRhbC5tY2FmZWVzYWFzLmNvbS9lZHMvZW5jcnlwdGlvbi9lbmNyeXB0aW9uX2xvZ2luLnBocD9k

                PW0zd1kxRTVfSWozNFFuTnlkWG5HZ0FlaHZyVXJhMElyMVV2SWtUYWtoMHZxWWlyT2hQNmc4VkRf

                Z29WX2wwelUwWFBfci1kdy1SVlpPdndCZC1SSzRvOTllMHNVT2s5a3ctQTQyMGxCbEc5TmludllS

                RHNsb1Z3MEsyTzZiV2NUcW9FV0Z3YjA5YUVYSWhnVktGN3J0ZkVRNkMxZTJCNmgzUXlqR2lCMFo1

                ZyUzRCZlbWFpbD1ib2JhaGF5JTQwZ21haWwuY29tJnRpbWU9MTM5NDIyMzQxOCZzZW5kZXJfZW1h

                aWw9YmhheSU0MG1uZ2xhYi5jb20maD1iNzc1NDM3MTk0NGUyM2Q4NTFiNzA2MzBkZmM1MWE3Nzgz

                OGVlMDI2YTRmYWE4Mjc0OTAxMjdjOWIyMGRjZGM4CgpOb3RlOiBZb3Ugd2lsbCBiZSByZXF1aXJl

                ZCB0byBzdWNjZXNzZnVsbHkgc2lnbiBpbiB0byB5b3VyIFNlY3VyZSBXZWIgTWFpbCBhY2NvdW50

                IHRvIHJlYWQgdGhpcyBtZXNzYWdlLgpZb3Ugc2hvdWxkIG5vdCByZXNwb25kIHRvIHRoaXMgYXV0

                b21hdGljYWxseSBnZW5lcmF0ZWQgbWVzc2FnZS4KCg==

                ----=_NextPart_21a1_0fee_6fa4e6e3_a635_11e3_ae0d_0017a477901c_alternative

                Content-Type: multipart/related;

                  boundary="--=_NextPart_21a1_0fee_6fa4e6e3_a635_11e3_ae0d_0017a477901c_related"

                 

                This is a multi-part related message in MIME format.

                 

                ----=_NextPart_21a1_0fee_6fa4e6e3_a635_11e3_ae0d_0017a477901c_related

                Content-Type: text/html;

                • 5. Re: Mcafee SAAS Secure email coming through as mime base64 encodded junk
                  ddonal2

                  We use exchange 2007 and are having this EXACT same issue.  What is the fix for this? 


                  We are up to date on all rollups for exchange and we have researched this issue for the past 2 weeks.

                   

                  Need help!

                  • 6. Re: Mcafee SAAS Secure email coming through as mime base64 encodded junk
                    ddonal2

                    We are having this EXACT SAME issue.  We have exchange 2007.  Have you figured out a solution or a fix??

                     

                    Help!!

                    • 7. Re: Mcafee SAAS Secure email coming through as mime base64 encodded junk
                      chad5840

                      I am having this exact same issue with 2 vendors that are trying to send us secure e-mails from McAfee Secure email service.  The "answer" provided doesn't tell me why vendors using McAfee's services are not coming through like they are supposed to.

                      • 8. Re: Mcafee SAAS Secure email coming through as mime base64 encodded junk
                        chad5840

                        Did you happen to figure out the issue, it's happening with as well.

                        • 9. Re: Mcafee SAAS Secure email coming through as mime base64 encodded junk
                          david_vi

                          This post has been marked as answered but from what I read from above, this is still outstanding. Does McAfee have a resolution to this???

                          1 2 Previous Next