fix(deps): update module github.com/wneessen/go-mail to v0.2.8 #1258
No reviewers
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1258
Loading…
Reference in 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.2.6
->v0.2.8
Release Notes
wneessen/go-mail
v0.2.8
Compare Source
This release adds a middleware concept to the
Msg
context to allow 3rd parties to extend mail messages with their own code. Thanks to Dhia Gharsallaoui for the PR!It was also pointed out on Discord that it would be useful to have a
DialAndSendWithContext()
method, which is also part of this release.Noteworthy changes
3a5f639
implements the middleware concept664aca5
implements theDialAndSendWithContext()
methodv0.2.7
Compare Source
This release adds support for requesting MDNs (RFC 8098) and DSNs (RFC 1891) to be delivered for outgoing mail messages. We've also added more test coverage.
MDNs
MDNs (Message Disposition Notification) allows you to request a - what is often referred to as - "read receipt". This is implemented via a message header and it's up the the recipients MUA to send out this notification to the sender.
Code example:
For MDNs we implement the same methods as for the
To
methods:RequestMDNTo
RequestMDNToFormat
RequestMDNAddTo
RequestMDNAddToFormat
DSNs
DSNs (Delivery Status Notification) are an extension to the SMTP protocol and need to be supported by the sending server. The RFC for DSNs defines different parameters of which we've implemented the once which we think make most sense for go-mail:
RET
extension for theMAIL FROM
command, to let the user specify if a DSN should contain the full mail (FULL
) or only headers (HDRS
) of the sent mail.NOTIFY
extension that allows the user to request a DSN for the different types of allowed situations:NEVER
,SUCCESS
,FAILURE
andDELAY
ENVID
andORCPT
are currently not supported but might follow in a later relaese (please open an issue if you see usefulness in this).Since DSNs are part of the SMTP protocol, these need to be enabled on the
Client
. We've added 3 ways to do so:WithDSN
: Which enables DSNs, sets theFULL
Mail From Return Option and theSUCCESS
andFAILURE
Recipient Notify OptionsWithDSNMailReturnType
: which enables DSNs and allows the user to specify which type of Mail From Return Option is wantedWithDSNRcptNotifyType
: which enables DSNs and allows the user to specify which types of Recipient Notify Options are wantedCode example:
Noteworthy changes
5bd3cec
implements the MDN supportf4cdc61
implements the DSN supportda266bc
adds better test coverageConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 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 Renovate Bot.
1f7bf733d0
toceb52135bd