Uploaded image for project: 'James Server'
  1. James Server
  2. JAMES-1937

Recognizing the multipart/alternative and nested multipart attachments with RFC naming support

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.0-beta4
    • Fix Version/s: 3.0.0
    • Component/s: James Core
    • Labels:
      None
    • Flags:
      Patch, Important

      Description

      I cannot conclude this as an issue / improvement. The JAMES server does not recognize many kind of attachments when creating a MimeMessage object. This includes
      1. Nested multipart contents,
      2. multipart/alternative types.
      3. RFC encoded headers for file names. Like continuation, base64 encoded etc
      4. Inline attachments, and proprietary types like the applcation/tnef etc.

      Currently , we cannot depend blindly on the Mail.getMessage(), instead we have to build the DOM Tree using MessageBuilder and parse through it.
      Can this be solved?

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              krishnanunnik Krishnanunni K
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: