Implements feature #1578 - CC and BCC on custom headers #1865
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A trivial solution to implement exactly what is suggested on #1578, second option. In a lot of cases companies are required to keep a track record of all emails sent to clients. This is often achieved simply by bcc all emails to an archived mailbox. Of course, a perfect solution would be to implement archival at SMTP server side, but not all senders have this functionality. As an example discussed before in #1578, Amazon SES does not.
This feature addresses this. You can add a Bcc header at SMTP server configuration so that all emails sent by listmonk are copied.