as of 0.0.9, mox patches up line endings in the rfc822 opaque email byte-sequence
— mox CANNOT do this. if a corrupt rfc822 comes in, a corrupt rfc822 should go out
— it is value if mox can detect and scrub for stored rfc822 that has been corrupted, using sha256 hashes
— mox could return error and output filename and expected hash to the log
— mox should also return error if say the ENVELOPE cannot be parsed but should best effort return the rfc 822 bytes
as of 0.0.9, mox patches up line endings in the rfc822 opaque email byte-sequence — mox CANNOT do this. if a corrupt rfc822 comes in, a corrupt rfc822 should go out — it is value if mox can detect and scrub for stored rfc822 that has been corrupted, using sha256 hashes — mox could return error and output filename and expected hash to the log — mox should also return error if say the ENVELOPE cannot be parsed but should best effort return the rfc 822 bytes