Skip to content
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

feat: support for smtp server #452

Closed
wants to merge 5 commits into from
Closed

feat: support for smtp server #452

wants to merge 5 commits into from

Conversation

adrian549092
Copy link
Contributor

Description

No issue associated with this feature but could be a solution for #370
The proposed change allows the user to specify an smtp server ip address or fqdn and port in the .env file to use for sending email and sms notifications. In my particular situation, the application resides behind a proxy server which does not allow connections to external smtp servers but I do have a local mail relay agent available for sending emails.

Testing

When SMTP_ADDRESS and SMTP_PORT are left unspecified the application will use the default gmail service and works as normal. When the mentioned variables are set then the application will use the specified settings to connect to an SMTP Relay Agent and send emails. Both of the previously mentioned cases were tested using the available test:notification npm script and I also set the PHONE_NUMBER and PHONE_CARRIER variables in order to confirm that SMS notifications worked as well. All tests succeeded.

SMTP_ADDRESS="<IP ADDRESS OF SMTP SERVER>"
SMTP_PORT=<TCP PORT FOR SMTP SERVER>

@adrian549092 adrian549092 requested a review from jef as a code owner October 5, 2020 06:07
src/notification/email.ts Show resolved Hide resolved
src/notification/email.ts Outdated Show resolved Hide resolved
src/config.ts Outdated Show resolved Hide resolved
Co-authored-by: Jef LeCompte <jeffreylec@gmail.com>
@jef
Copy link
Owner

jef commented Oct 5, 2020

Once conflicts are resolved, would love to have this in!

Thanks for working on this and the previous proxy work.

Co-authored-by: Jef LeCompte <jeffreylec@gmail.com>
@adrian549092
Copy link
Contributor Author

no problem @jef my pleasure. let me know if there is any other action items on my end

@adrian549092
Copy link
Contributor Author

@jef and @andrewmackrodt I am going to close this PR and submit a new one as I am noticing that there are alot of conflicts not related to my feature. I will sync my fork then re-add the feature code and generate a new PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants