added functionality of sending mail when new user is created and when…

[PRANJALJAVIA]

… any new broadcast is added then also mail sent to the registered users only backend part is completed

Issue that this pull request solves

Closes: #870

Proposed changes

when new user is registered in the website using email and password then welcome mail is sent to the user and every time when new podcast is generated then mail is send to the registered user

Backend part is added

Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• [ x ] New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update (Documentation content changed)
• Other (please describe):

Checklist

Put an x in the boxes that apply

• [ x ] My code follows the style guidelines of this project
• [ x ] I have performed a self-review of my own code
• [ x ] I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• [ x ] My changes generate no new warnings
• [ x ] My changes does not break the current system and it passes all the current test cases.

Screenshots

Please attach the screenshots of the changes made in case of change in user interface

Other information

enter mail id which is used to sent the mail to registered user in the .env file of backend
enter passkey of that mail id in the EMAIL_ID_FOR_SENDING_MAIL in the .env file of backend

[welcome]

Thank you and congrats🎉 for opening this pull request!💖

Please make sure you have followed our Contributing Guidelines.🙌 We will test out your code and reply in a bit with some pointers and requests.💿 There may be some errors, but don't worry! We'll work through them with you! 👍🎉😄 If you haven't filled the template out, Please do so!🚀
Feel free to join our Slack Community.💖 We have different channels for active discussions.✨ Hope you have a great time there!😄

[Kajol-Kumari]

• Please resolve the conflict
• Can you attach any screenshot/recording showing the functionality?
• Please address the below comments

[PRANJALJAVIA]

Frontend part is not done so I am not able to show any screen shot but I have tested in backend API in Thunder client

…

On Wed, 3 Jul 2024 at 23:16, kajol ***@***.***> wrote: ***@***.**** requested changes on this pull request. - Please resolve the conflict - Can you attach any screenshot/recording showing the functionality? - Please address the below comments ------------------------------ In backend/.env <#1072 (comment)> : > @@ -8,3 +9,7 @@ EMAIL_HOST=smtp.gmail.com CLUSTER=no JWT_RESET_PASSWORD_EXPIRES_IN=1h LOCAL_DEV_ENV=http://localhost:3500/ + + +EMAIL_PASS_FOR_NODEMAILER=<enter your gmail pass key> can't we reuse EMAIL_USER and EMAIL_PASS as those 2 are the community email and the email's password respectively ------------------------------ In backend/utility/emailTemplates.js <#1072 (comment)> : > + </ul> + <p>Welcome once again to the HITK Tech Community. We're glad to have you with us!</p> + <p>Best regards,<br>The HITK Tech Team</p> + </div> + <div class="footer"> + <p>&copy; 2024 HITK Tech Community. All rights reserved.</p> + <p><a href="[Unsubscribe Link]">Unsubscribe</a> | <a href="[Privacy Policy Link]">Privacy Policy</a></p> + </div> + </div> + </body> +</html> + `; + return emailContent; +} + +module.exports.NewBroadCastMailTemplate = (subscriber) => { let's keep this template in a separate file for better maintainance? — Reply to this email directly, view it on GitHub <#1072 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXAOZS5HIDPMC4RFMQ3RUKTZKQ2HPAVCNFSM6AAAAABKJ6OVBSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCNJXGAZTMMBXHE> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>