Add spec to check if invalid chars get dropped as expected during initial mail parsing
We've changed the way how we handle initial mail encoding parsing via !325 (merged). If all fails, we might drop invalid chars to at least be able to handle the rest of problematic mails. However, as of now, we didn't found a way to trigger such a case.