v0.6.1: Fix for multipart message rendering

[wneessen]

Welcome to go-mail v0.6.1! This release is a bug-fix release that addresses a regression introduced in v0.6.0.

Important

If you are working with multipart messages and are currently using v0.6.0, it is advised to upgrade to v0.6.1 to avoid rendering issues.

Fix missing new-lines in multipart rendering

The v0.6.0 release introduced a regression in the multipart message generation (See #412). The boundary lines were not correctly seperated with a new line. This bug was introduced while working on the S/MIME handling. The issue has been fixed in #413. I am sorry for any inconveniences this might have caused. Thanks to @Thomas2500 for reporting the issue!

Multipart boundary handling refactoring

While working on #412, I noticed a general issue with the boundary handling when fixed boundaries are set for the message. This bug was present already since the introduction of Msg.WithBoundary/Msg.SetBoundary, but was only brought to light with the new S/MIME feature introduced in v0.6.0. Since the S/MIME signing needs to set a fixed boundary, it was using the Msg.SetBoundary feature. If more than one multipart parts were used with a fixed boundary, this would render the mail broken (since it was using the same boundary for multiple parts). This has been fixed in #414 and #416. The GoDoc for Msg.WithBoundary/Msg.SetBoundary has also been updated with a warning that using the feature with more than one parts will break the message rendering.

Removal of XOAUTH2 from Auto-Discovery feature

Since XOAUTH2 works with Bearer tokens instead of passwords but the Auto-Discovery SMTP auth feature makes use of a username/password pair having XOAUTH2 in the prefered mechanisms list could cause authentication failures. Therefore the XOAUTH2 mechanism has been removed from the feature completely. Thanks to @james-d-elliott for pointing this out!

What's Changed

• Fix regression in multipart boundary writing by @wneessen in Fix regression in multipart boundary writing #413
• Refactor multipart boundary handling in message rendering by @wneessen in Refactor multipart boundary handling in message rendering #416
• Remove XOAUTH2 from Auto-Discovery SMTP auth feature by @wneessen in Remove XOAUTH2 from Auto-Discovery SMTP auth feature #417
• chore: prepare 061 release by @wneessen in chore: prepare 061 release #418

Full Changelog: v0.6.0...v0.6.1

---

This discussion was created from the release v0.6.1: Fix for multipart message rendering.