chore(deps): update module github.com/wneessen/go-mail to v0.8.1 #20
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/github.com-wneessen-go-mail-0.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v0.7.3→v0.8.1Release Notes
wneessen/go-mail (github.com/wneessen/go-mail)
v0.8.1Compare Source
Welcome to go-mail v0.8.1! 🎉
This release is only a small release, but fixes a regression on the 386 platform. We hope you enjoy!
Notable features / improvements / fixes
Fix regression on 386 platforms
The NTLM support introduced in v0.8.0 contained a bug affecting 386 platforms: a 32-bit integer could overflow because it wasn't cast to
int64. This caused problems when cross-compiling to the 386 architecture. The bug is fixed in #589. In addition, the CI pipeline has been extended to run cross-compile tests for every platform supported by GitHub runners. Thanks to @firefart for reporting the issue.Opportunistic SMTP authentication
PR #585 introduces an opportunistic authentication mechanism that lets users provide a list of preferred auth types. During SMTP authentication, the client checks the mechanisms the server supports and selects the first match from the preferred list. If the server supports none of the preferred mechanisms, the client falls back to Autodiscover mode and selects the strongest mechanism the server offers.
Convenience helpers for List-Unsubscribe and one-click List-Unsubscribe-Post
We already expose the
HeaderListUnsubscribeandHeaderListUnsubscribePostheader constants, but until now there was no dedicated function to construct these headers. Users had to assemble the angle-bracket URI list and the exactList-Unsubscribe=One-Clicktoken by hand viaSetGenHeader—something that's easy to get subtly wrong (missing<>, an incorrect POST token, or GET-triggerable URLs). Since February 2024, Gmail and Yahoo require a working RFC 8058 one-click unsubscribe for senders exceeding 5k messages per day, making this a common compliance requirement rather than a niche feature. PR #587 adds three convenience helpers to set these headers correctly:SetListUnsubscribe(uris ...string): sets an RFC 2369List-Unsubscribeheader only (mailto/httpslinks).SetListUnsubscribePost(): setsList-Unsubscribe-Post: List-Unsubscribe=One-Click.SetListUnsubscribeOneClick(httpsURL string, additionalURIs ...string): the common case: sets both headers correctly, validating that at least one HTTPS URL is present as required by RFC 8058.What's Changed
CI/CD maintenance changes
Full Changelog: https://github.com/wneessen/go-mail/compare/v0.8.0...v0.8.1
v0.8.0: : Native NTLM and DKIM supportCompare Source
Welcome to go-mail v0.8.0! 🎉
This release brings two big new features and a couple of improvements and fixes to go-mail. We hope you enjoy this release!
Notable features/improvements/fixes
Native NTLM authentication support
With PR #576 native NTLMv2 SMTP auth support has been added to go-mail. This feature has been requested several times and so far we've always resorted to a custom SMTP authentication provider using some 3rd party libraries. With go-mail v0.8.0 you can now natively authenticate with NTLM servers like any of the other supported authentication methods. Big thanks to @mkalus for providing some ground work in #549 and for helping to test the code. The development was mainly based on the excellent documentation of the cURL project.
Native DKIM support
PR #582 adds native DKIM signing support to go-mail. So far we only supported DKIM via go-mail middleware, which proved to very limited and had the caveat that it needs to be the last middleware to be executed, otherwise the signature would be invalid. With go-mail v0.8.0 you can now natively DKIM sign your mails. DKIM support has been added in the
Msgas well as in theClienttypes. In theMsgtype you can sign individual mail messages, while the DKIM support in theClientinstructs the mail sender to sign every outgoing message that runs through it.Named templates support
With PR #556 go-mail now has support for named templates. So far we've been executing a template as a whole, but with this new functions one is allowed to execute only a portion of the template. Thanks to @Maldiran for contributing this PR!
Option to skip RSET after mail delivery
PR #569 adds a new
Clientoption:WithoutRset(). This instructs the client to skip theRSETwe usually send after a successful mail delivery. This option can be useful for MTAs that do not support theRSETcommand and would fail because of that, even though the mail was successfully delivered.What's Changed
CI/CD maintenance changes
New Contributors
Full Changelog: https://github.com/wneessen/go-mail/compare/v0.7.3...v0.8.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.
ℹ️ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the
go getcommand, which resulted in the following additional change(s):Details:
golang.org/x/cryptov0.33.0->v0.54.0golang.org/x/sysv0.30.0->v0.47.0golang.org/x/textv0.37.0->v0.40.039f92ee6769812eb2c48chore(deps): update module github.com/wneessen/go-mail to v0.8.0to chore(deps): update module github.com/wneessen/go-mail to v0.8.1View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.