We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I’m confused by the multipart tree structure generated for a mail with alternate text and html, embed and attachment. Here is what go-mail generates:
multipart/mixed |-- multipart/related | |-- multipart/alternate | | |-- text/plain | | `-- text/html | `-- image/jpg `-- attachment
What I expected to see:
multipart/mixed |-- multipart/alternate | |-- text/plain | `-- multipart/related | |-- text/html | `-- image/jpg `-- attachment
This is the structure that I have seen in mails. Which one is correct ?
What is the point to associate (relate) the embedded image to the text/plain part ?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I’m confused by the multipart tree structure generated for a mail with alternate text and html, embed and attachment. Here is what go-mail generates:
What I expected to see:
This is the structure that I have seen in mails. Which one is correct ?
What is the point to associate (relate) the embedded image to the text/plain part ?
The text was updated successfully, but these errors were encountered: