Skip to content

[RFC] Email signing (and encryption) workflow #53941

Closed
@jontjs

Description

Description

Currently the recommended workflow for signing emails (DKIM or S/MIME) is to sign the message in a controller/service/wherever and then use the Mailer to send that signed message rather than the original unsigned message.

This causes a broken signature when sending a TemplatedEmail (see issue [Mailer] Signing email is not working with templated email) - seemingly because the signing is done in the controller/service/whatever but the rendering of the template is done in a listener when the mail is sent.

Perhaps the solution to this would be for signing (and S/MIME encryption) to also be performed by a listener at the time of sending, to run after the TemplatedEmail has been rendered. Given that DKIM feels more and more like a must-have feature of sending emails perhaps it is time to integrate it into the Mailer component, i.e. the DKIM options would become options of the Mailer component.

Example

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Good first issueIdeal for your first contribution! (some Symfony experience may be required)Help wantedIssues and PRs which are looking for volunteers to complete them.RFCRFC = Request For Comments (proposals about features that you want to be discussed)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions