Navigation

    Kopano
    • Register
    • Login
    • Search
    • Categories
    • Get Official Kopano Support
    • Recent
    Statement regarding the closure of the Kopano community forum and the end of the community edition

    Attachments names broken -> 8.7.3 rfc2231

    Kopano Groupware Core
    1
    1
    254
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • iPC99
      iPC99 last edited by

      Hello,

      i’ve upgraded to 8.7.3 a few days ago and since that, we cannot send attachments filenames over 60 characters as before. We’re using outlook and webapp and depending on the size of the attachment filename, the receiver gets a filename called xxx.dat, “unnamed” or something.

      This happend, because not all email clients agree with the rfc2231, similar to this report: https://jira.kopano.io/browse/KC-1226
      But unlike the report, we have the problem in the webapp and the outlook client, with local and external reciepients.

      If figured out that the 8.7.3 and the 8.6.9 server have installed the libvmime-kopano1 in version 0.9.2.50+12.1. But the 8.7.3 has an additional package called libvmime-kopano2 in version 0.9.2.85+6.1. The file is slightly bigger… and in 64bit?

      And Btw: We’re also affected by the BCC error :(

      Thank you for any suggestions to solve this.

      Alex

      The headers looks like this:

      Content-Type: text/plain; name*0*=utf-8''xxxxxxx%20xxxx%20xxxxxxxxx%20xxxxxx-27th%20april%20xxxxxxxxx;
       name*1*=x%20xxxxxx%206.29%20xxxxxxxxx%20xxxxxx.txt
      Content-Transfer-Encoding: base64
      Content-Disposition: attachment; filename*0*=utf-8''xxxxxxx%20xxxx%20xxxxxxxxx%20xxxxxx-27th%20april%20xxxxx;
       filename*1*=xxxxx%20xxxxxx%206.29%20xxxxxxxxx%20xxxxxx.txt
      
      
      Content-Type: text/plain; name*0*=utf-8''This%20is%20a%20Test%20with%20a%20very%20long%20filename%20o;
       name*1*=ver%2060%20characters%201234567890.txt
      Content-Transfer-Encoding: base64
      Content-Disposition: attachment; filename*0*=utf-8''This%20is%20a%20Test%20with%20a%20very%20long%20filename;
       filename*1*=%20over%2060%20characters%201234567890.txt
      
      

      But it should look like this (for example from version 8.6.9)

      Content-Type: text/plain;
       name="This is a Test with a very long filename over 60 characters 1234567890.txt";
       name*0*=utf-8''This%20is%20a%20Test%20with%20a%20very%20long%20filename%20o;
       name*1*=ver%2060%20characters%201234567890.txt
      Content-Transfer-Encoding: base64
      Content-Disposition: attachment;
       filename="This is a Test with a very long filename over 60 characters 1234567890.txt";
       filename*0*=utf-8''This%20is%20a%20Test%20with%20a%20very%20long%20filename;
       filename*1*=%20over%2060%20characters%201234567890.txt
      
      1 Reply Last reply Reply Quote 0
      • First post
        Last post