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
To help me debug your issue, please explain: What were you trying to do?
Add a linked resource using BodyBuilder
What happened?
Were added with Content-Disposition: attachment instead of Content-Disposition: inline.
What did you expect to happen?
Get Content-Disposition: inline.
That's what we got in MailKit ver. 2.7.0. The problem occurred after upgrading to ver. 2.10.0.
Step-by-step reproduction instructions and/or a simple test case.
oMimeEntity = oBodyBuilder.LinkedResources.Add("Filename.png", binary)
The text was updated successfully, but these errors were encountered:
Always set Content-Disposition: inline for LinkedResources
333b7a0
Accidentally broke this in 2.10.0 due to swapping part.FileName and part.IsAttachment assignments. Fixes issue #627
Sorry about that! I've added some new unit tests to make sure I don't break this again.
Sorry, something went wrong.
I'll probably try to make a 2.10.1 release with this fix this week/weekend.
Great 👍
Released v2.10.1 to nuget.org with this fix.
No branches or pull requests
Add a linked resource using BodyBuilder
Were added with Content-Disposition: attachment instead of Content-Disposition: inline.
Get Content-Disposition: inline.
That's what we got in MailKit ver. 2.7.0. The problem occurred after upgrading to ver. 2.10.0.
oMimeEntity = oBodyBuilder.LinkedResources.Add("Filename.png", binary)
The text was updated successfully, but these errors were encountered: