Trying to track down why Mime4J now longer parses complex nested messages correctly.
tree36217acbc98cf6500edc1b66df20cf037e43c9d1
-rw-r--r-- 229 BUILDING.txt
drwxr-xr-x - examples
-rw-r--r-- 15072 pom.xml
drwxr-xr-x - src
drwxr-xr-x - stage