feat: add "null" STMP transport mode #48977
Open
+22
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
If mails ought to be send by other means than rendering messages from
templates and sending them via SMTP-like protocols.
Use-case example
Listening to specific Nextcloud events and pass parameters to a centralized (i.e. REST-based) API that sends e-mails.
Background why not ...
mail_template_class
: same as beforeBeforeMessageSent
and act upon that: would be an option, but it would still render messages that will never be sent and the template data might also have to be enriched with custom information (i.e. in our case the sender's user ID, not their e-mail address)(Short list of internal reasoning we had before making this pull request.)
Checklist
Screenshots before/after for front-end changesBackports requested where applicable (ex: critical bugfixes)