Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-26542

Mail should handle extension for embedded attachments.

XMLWordPrintable

      The Content-Type name parameter should be in quotation marks and include a file extension. The Content-Disposition filename parameter should also be in quotation marks and include a file extension.

      • Effects everyone who uses Amazon SES for Confluence.

      Error message in the logs:

      ERROR [http-80-6] [atlassian.core.task.AbstractErrorQueuedTaskQueue] handleException com.atlassian.mail.MailException: com.sun.mail.smtp.SMTPSendFailedException: 554 Transaction failed: Illegal filename xxxx

      Examples of illegal filenames:

      • page-icon
      • attachment-icon
      • avatar_1a7f5ad0a95a4db2f2845b51c14661ea
      • icon-like

        1. relay_error.jpg
          130 kB
          William Zanchet

            [CONFSERVER-26542] Mail should handle extension for embedded attachments.

            Jonathan Allen added a comment -

            Awesome thanks!

            Jonathan Allen added a comment - Awesome thanks!

            Issac Gerges (Inactive) added a comment - - edited

            Hey jansr,
            I can definitely tell this is causing our users some pain. I've just signed up for a AWS personal account and I plan to test on my local instance to try and flush out any additional issues (once Amazon grants me SES access). Since the issue this ticket specifically relates to has been resolved (regarding the headers missing file extensions) I think it's best to leave this ticket marked as Fixed. If I do run into any issues with SES I'll link them to this one to keep everyone aware.

            Issac Gerges (Inactive) added a comment - - edited Hey jansr , I can definitely tell this is causing our users some pain. I've just signed up for a AWS personal account and I plan to test on my local instance to try and flush out any additional issues (once Amazon grants me SES access). Since the issue this ticket specifically relates to has been resolved (regarding the headers missing file extensions) I think it's best to leave this ticket marked as Fixed. If I do run into any issues with SES I'll link them to this one to keep everyone aware.

            Jonathan Allen added a comment -

            For the money we spend on Atlassian products, seems like Atlassian should be able to sign up for a free AWS EC2 account to test this before releasing it. Your customers would really appreciate it.

            Jonathan Allen added a comment - For the money we spend on Atlassian products, seems like Atlassian should be able to sign up for a free AWS EC2 account to test this before releasing it. Your customers would really appreciate it.

            Issac Gerges (Inactive) added a comment -

            Hi All,

            Thanks for reporting this issue. I've added a fix to ensure all mail attachments "Content-Type" and "Content-Disposition" headers include a file extension matching the MIME type of the file. I've also verified the "Content-Disposition" header will use a quoted filename if it contains spaces. This is on track to be included in the upcoming 5.3 release.

            Since we're unable to interactively test with Amazon SES, there may be additional issues you run into with that service. If they appear to be related to Confluence, please create a ticket and we'll take a look.

            Thanks,
            Issac

            Issac Gerges (Inactive) added a comment - Hi All, Thanks for reporting this issue. I've added a fix to ensure all mail attachments "Content-Type" and "Content-Disposition" headers include a file extension matching the MIME type of the file. I've also verified the "Content-Disposition" header will use a quoted filename if it contains spaces. This is on track to be included in the upcoming 5.3 release. Since we're unable to interactively test with Amazon SES, there may be additional issues you run into with that service. If they appear to be related to Confluence, please create a ticket and we'll take a look. Thanks, Issac

            Steve Haffenden (Inactive) added a comment -

            Hi William

            This is currently on our backlog waiting to be resolved. We'll keep you informed of any updates.

            Regards

            Steve Haffenden (Inactive) added a comment - Hi William This is currently on our backlog waiting to be resolved. We'll keep you informed of any updates. Regards

            Bradley Betts added a comment -

            Also experiencing this, with 5.1.2 and SES. Hope the issue can get resolved, thanks in advance for any attention you can give it.

            Bradley Betts added a comment - Also experiencing this, with 5.1.2 and SES. Hope the issue can get resolved, thanks in advance for any attention you can give it.

            Matthew Stevens added a comment -

            I've had to temporarily use Gmail until this issue can be resolved. Fortunately we don't have enough alerts to hit the Gmail sending limit as we did with Jira. At the very least Atlassian should allow for not including attachments to let basic (even text based) alerts pass through.

            https://confluence.atlassian.com/pages/viewpage.action?pageId=42795030

            Matthew Stevens added a comment - I've had to temporarily use Gmail until this issue can be resolved. Fortunately we don't have enough alerts to hit the Gmail sending limit as we did with Jira. At the very least Atlassian should allow for not including attachments to let basic (even text based) alerts pass through. https://confluence.atlassian.com/pages/viewpage.action?pageId=42795030

            Deleted Account (Inactive) added a comment - - edited

            I'm also experiencing this using Amazon SES with Confluence 5.1.5

            Deleted Account (Inactive) added a comment - - edited I'm also experiencing this using Amazon SES with Confluence 5.1.5

            Daisuke Miyamoto added a comment -

            Is there a workaround to use Amazon SES as Confluence mail server?

            Daisuke Miyamoto added a comment - Is there a workaround to use Amazon SES as Confluence mail server?

            Sorin Stoiana added a comment -

            Affects us on Confluence 5.0.1

            Sorin Stoiana added a comment - Affects us on Confluence 5.0.1

              igerges Issac Gerges (Inactive)
              wzanchet William Zanchet (Inactive)
              Affected customers:
              22 This affects my team
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: