Michał Nako

Hi @mgarbin , and thank you for the message. That is a very good suggestion. I still need to fix some known bugs (like the parser crashing if there is...

Hi @ltybenet, Thank you for opening the issue. You are correct that `mime.WordDecoder` can decode `"=?utf-8?Q?=40?="` properly. However, `mail.ParseAddressList()` raises the "expected comma" error, which I believe to be the...

@BoyGPT, thank you for opening the issue. I have reviewed the examples that you provided, and it appears that those emails do not have a plain text part. I could...

Thank you for opening the issue, @iceking2nd. I believe that the best way to handle this and other similar edge cases will be offered in https://github.com/mnako/letters/pull/134. Once the discussion and...

@iceking2nd , I have looked into your issue now and found out that the [`ParseMediaType(v string)`](https://github.com/golang/go/blob/master/src/mime/mediatype.go#L134) that we are using [treats duplicate parameter names as incorrect, but allow them if...

Thank you for this contribution, @Peter2121 . If you could add test cases following our existing patterns to show an example of base64-encoded content that needs spaces removed we will...

I agree with you, I think it has been an oversight to return a zero value instead of returning an error. Let me tackle the date formats in https://github.com/mnako/letters/issues/160 and...

Thank you for opening this issue, @telemachus. I have read the relevant RFCs and I think that you are right. There is a work-in-progress documenting the exact changes needed in...

Thank you for the review, @ValleyCrisps 🙇 @rorycl raised good points in the discussion here https://github.com/mnako/letters/discussions/64, where they mentioned that > [skipping body parsing] dropped my processing time to 1/10th...

Thank you for the review, @ValleyCrisps . Let me merge this first and make a release and we can explore parsing different types of bodies and parsing attachments in a...