Thanks for reporting this! The issue was caused by the email HTML content not being properly normalized before rendering - some emails from services like emailprivacytester.com return complex nested structures that triggered a React rendering error. I've pushed a fix that safely handles all edge cases (non-string HTML arrays, nested objects in header fields, etc.). Should be live shortly. Really appreciate you testing with edge cases like this!