feat: add option to use single header for destination headers#7
Conversation
Single destination headers are used in compliance with RFC 5322 (https://www.rfc-editor.org/rfc/rfc5322), which Gmail SMTP complained about. This affects the following headers: - To - Cc
|
@gagasdiv Excuse me, why is this pr closed? |
Ah, sorry, I meant to make this PR to the main branch in my own fork because I needed the changes real quick (I made it to your main branch by mistake). I can restore the branch and reopen this PR if you want to implement this upstream. Oh, and I like your library! Using it is quite easy, I was looking for a simple Go email library and this fits my project's needs quite well. |
|
It's so kind of you. I hope to restore this PR. According to this closed PR:
|
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
|
@gagasdiv Thank you very much again! |
Single destination headers are used in compliance with RFC 5322 (https://www.rfc-editor.org/rfc/rfc5322#section-3.6.3), which Gmail SMTP complained about. This affects the following headers: