[Snyk] Security upgrade MimeKit from 2.11.0 to 4.15.1

[ashmuck]

Snyk has created this PR to fix 1 vulnerabilities in the nuget dependencies of this project.

Snyk changed the following file(s):

• IndicoV2/IndicoV2.csproj

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	CRLF Injection SNYK-DOTNET-MIMEKIT-15468175	738

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 CRLF Injection

---

Note

Low Risk
Single dependency version bump in project packaging metadata; risk is limited to potential breaking changes in MimeKit APIs if consumed elsewhere.

Overview
Updates IndicoV2.csproj to upgrade MimeKit from 2.11.0 to 4.15.1 (Snyk-driven) so the package is pulled in as a NuGet dependency with the patched version.

^{Written by Cursor Bugbot for commit 70d2795. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Security upgrade incomplete: test project still references vulnerable version

Medium Severity

The MimeKit upgrade to 4.15.1 was only applied in IndicoV2/IndicoV2.csproj, but IndicoV2.IntegrationTests/IndicoV2.IntegrationTests.csproj still explicitly references the vulnerable MimeKit version 2.11.0. Before this change, both projects referenced the same version; now they're inconsistent. While NuGet resolution may pick the higher transitive version at build time, the explicit vulnerable reference remains and Snyk will likely continue flagging it.