Steps to repro:
1. Send yourself a very large email (16 megs works for me)
2. check the SpoolManager log and see this over and over:
ERROR spoolmanager: Exception in JamesSpoolManager.run null
What makes this problem particularly bad is that the spoolmanager doesn't move on to other
messages but keeps pegging the CPU trying to process this email. To fix it, I have to shut down
james, delete the email files out of spool and restart.
EXPECTED: email should spool to the user as expected.