-
Notifications
You must be signed in to change notification settings - Fork 171
feat: add always_bcc feature #91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
@juanluisbaptiste can you please check this PR, it is very important to us |
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-ALPINE315-OPENSSL-5788364 - https://snyk.io/vuln/SNYK-ALPINE315-OPENSSL-5788364
@juanluisbaptiste I just have seen you spend some time on this project today, can you please also merge this request? Thank you. |
7551f12
to
3adc149
Compare
Hi @mstenz could you update the PR with the latest master? |
done. |
@mstenz your branch still cannot be merged due to conflicts. Maybe you could delete it and start over with a fresh fork of master? |
@juanluisbaptiste Please try again |
Hi @mstenz sorry for the late reply, I was on vacations. GitHub still says there's a conflict and does not allow me to rebase and merge. I think the best option is to start with a clean branch based on current master, instead of merging new changes into your current branch. |
Creating a Pull Request
Description of the change
Allows the always_bcc feature to be configured, this allows some type of MIRRORING all emails that are sent through the server
Motivation and Context
we need this feature in our environment to debug applications that send out emails
How Has This Been Tested?
this is a very easy change. that used a copy of different settings as a skeleton. tested this on a live running container by setting the variable
Types of Changes
Checklist:
.env.example
file accordingly.