Announcement

Collapse
No announcement yet.

Attachment displays in body using TLS connection

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Attachment displays in body using TLS connection

    We have a secure TLS connection between our company and companyX.

    Company X sends us an email with an .zip attachment (except the change the extension to .zi_ and after we receive it theywould like us to change it back to .zip)

    The email displays the attachment in body with a whole bunch on gibberish. The actual attachment size is 5MB but the size of the email is 11MB.

    I created a .ZIP file that is 5MB in size and change the extension to .ZI_
    I was able to receive the attachment and then change its extension and open the file.

    Are there any file extension restrictions when using TLS? Any help is appreciated.

    Thanks

  • #2
    Re: Attachment displays in body using TLS connection

    That is something interfering with the traffic. TLS does not modify the actual transport of the message in any way, all that it does is wrap it in SSL.

    Simon.
    --
    Simon Butler
    Exchange MVP

    Blog: http://blog.sembee.co.uk/
    More Exchange Content: http://exchange.sembee.info/
    Exchange Resources List: http://exbpa.com/
    In the UK? Hire me: http://www.sembee.co.uk/

    Sembee is a registered trademark, used here with permission.

    Comment


    • #3
      Re: Attachment displays in body using TLS connection

      The weird thing is this only started to happen as soon as we routed our incoming/outgoing email through the hub transport.

      Previously, all email came directly into the E2003 Mailbox server.

      Is there something on the hub transport that would interfere with the traffic??

      Originally posted by Sembee View Post
      That is something interfering with the traffic. TLS does not modify the actual transport of the message in any way, all that it does is wrap it in SSL.

      Simon.

      Comment


      • #4
        Re: Attachment displays in body using TLS connection

        When I say interference I mean third party interference. There is nothing in Exchange that would cause this type of problem. I have never had a issue with the native SMTP transport in Exchange, all problems have been caused by AV or antispam software.

        Simon.
        --
        Simon Butler
        Exchange MVP

        Blog: http://blog.sembee.co.uk/
        More Exchange Content: http://exchange.sembee.info/
        Exchange Resources List: http://exbpa.com/
        In the UK? Hire me: http://www.sembee.co.uk/

        Sembee is a registered trademark, used here with permission.

        Comment

        Working...
        X