Uploaded image for project: 'James Mime4j'
  1. James Mime4j
  2. MIME4J-152

Zero parts multipart messages are parsed as 1 empty part multipart messages

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 0.6
    • 0.7
    • None
    • None

    Description

      Mime4j currenlty parse a message having only the start boundary as an empty message (zero parts) but at the same time parse a message with no boundary (no start and no end) as a message with 1 empty part.

      This is clearly wrong.

      We also already have a missing-inner-boundary.msg in our testsuite but the expectation files are wrong.

      Attachments

        1. testmsgs-missingboundaries.zip
          4 kB
          Stefano Bagnara

        Activity

          People

            bago Stefano Bagnara
            bago Stefano Bagnara
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: