tree e9d5fb8b6c7faae12c2ac09f7793c752f1b195bc
parent 4ecbe86e4248062fe0cf3dc49f03290fe8904945
author Thomas Fricker <tommi.fricker@googlemail.com> 1652947868 +0200
committer GitHub <noreply@github.com> 1652947868 +0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJihfucCRBK7hj4Ov3rIwAAPHQIAG+FGCB6Jtye/4T6i14aeNpA
 XpYWXoKbFi52dZdC+znZTzAYY1MRFFHAsKeskcKm5uY/3G+t/qgH+e5khnKrl7mX
 uS4nD6nkEjNXuUXgGHExeeH8r5VcaqRtPbn7oCuvdbstBoN8bOOoU3sUURyDprFY
 PTvRe9UmZX9jJcA4nX6Ue9GQ9HcbMmniYKsoBIDi24kO9qovwdynpNGgoI8Jv8wl
 d4jL5e5bG43uIDCDEC+k9uEzzRM2fYMaWORp0OD7VY0TMShr0vjM+apwUW3K7cm6
 6Ed9JM90CnegnqcxrClB1eet8jvd9q328p45NooYUXPyMo/1OvBtp5BCqR6KaT8=
 =+t86
 -----END PGP SIGNATURE-----
 

MIME4J-316 Parts missing in case of a specific combination of boundaries

The problem can be reproduced by parsing a very specific email structure, where
an inner boundary matches the name of another outer boundary followed by a "-" character.
In the following example, the attached pdf file will be ignored by the parser. 

Merge pull request #2 from bluemind-net/bugfix/BM-18542 (#71)

BM-18542 Fix: check for -- boundary ending

Thanks @tommix000 for the fix.