Closed thoffmann-fms closed 2 months ago
@thoffmann-fms This is the correct behavior, your message is of text/html
content-type instead of multipart/alternative
content-type. The presence of boundary=
parameter does not affect the parsing (at least not according to any RFCs I can find on this topic).
Do you know of any e-mail clients that would display your message in a way that you expect it to be displayed in? This seems very incorrect but if at least both Outlook and Gmail display it this way I'm going to add it in.
Ok, please give me a few days to get the mail routed to another mail client. It's being generated in a test environment that I need to replicate elsewhere. It's an older implementation of JMail that's sending it, so possibly a bug on that end, too. Thanks.
@thoffmann-fms Closing this issue due to lack of activity. Please feel free to reopen if the problem persists.
Hi, got an odd one here.![image](https://github.com/mat-sz/letterparser/assets/28546239/ed884dca-dc9e-4a6a-b799-daa00b1508b7)
const result: LetterparserMail = extract(block.Data);
is returningresult.html
wiith the data not being decoded. e.g.Here's the raw data in JSON: