Uploaded image for project: 'Confluence Server'
  1. Confluence Server
  2. CONFSERVER-22636

Mail Archive doesn't handle inline mime content cleanly



      When receiving a multipart mime message in the mail archive with an inline bodypart, the inline bodypart content is displayed in the email body, but an attachment is also added to the email in Confluence named "unnamed-0" which has the text of the inline mime section. This seems redundant and unnecessary. Also, I've found no way to remove these attachments while leaving the email intact without deleting them directly from the SQL backend, as we're using the DB for storage of attachments.

      In our environment, all emails are coming from MailMan which is adding the footer as an inline bodypart as described in detail at http://wiki.list.org/pages/viewpage.action?pageId=4030707

      A sanitized example of an email that has caused this behavior is:

      Content-Type: multipart/mixed; boundary="===============2040488032934442827=="

      Content-Type: multipart/alternative; boundary=20cf307d02cebad5fe04a46e428f

      Content-Type: text/plain; charset=ISO-8859-1

      This is the email

      Name, Sig, etc.

      Content-Type: text/html; charset=ISO-8859-1
      Content-Transfer-Encoding: quoted-printable

      This is the email.
      <br clear=3D"all">Name, Sig, etc.<br><br>


      Content-Type: text/plain; charset="us-ascii"
      MIME-Version: 1.0
      Content-Transfer-Encoding: 7bit
      Content-Disposition: inline

      LIST mailing list


      This displays quite nicely on our mail archive in confluence as:

      This is the email

      Name, Sig, etc.

      LIST mailing list

      And has one attachment:
      Text File unnamed-0 (0.1 kB - Anonymous - May 29, 2011)

      The content of the attachment is:

      LIST mailing list

      So, it would seem that the main email message is displaying the inline mime attachment correctly and in compliance with RFC 2183, section 2.1 (http://www.ietf.org/rfc/rfc2183.txt), but Confluence is incorrectly creating an attachment with the inline bodypart.


          Issue Links



              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Created:
                  Last commented:
                  6 years, 14 weeks, 3 days ago