-
Notifications
You must be signed in to change notification settings - Fork 51
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
[FEATURE] Implement Backend Functionality for Email Sending #87
Comments
@ajaynegi45 @Guhapriya01 I was studying the email-sending functionality, but I got delayed in raising the issue due to my exams. Now, I’d like to work on this issue. Please assign it to me. |
Hi @shreya5653, Use gmail to send emails. If I didn't reply within 24hr then ping me on LinkedIn. Before making any contributions, please read the Readme.md file carefully to better understand the project's goals and purpose. This will give you clarity on our mission. Also, make sure to review the Contributing.md file, which contains important guidelines to make the contribution process smoother, especially for newcomers. Feel free to start working, and if you have any questions or need assistance during the process, please don't hesitate to reach out. |
Sure! Thank you so much |
@ajaynegi45 @Guhapriya01 I've been trying to run my project since yesterday, but I'm facing issues even after confirming that all dependency configurations are correct. After syncing the fork, I'm encountering errors in various files, such as missing beans in borrowing. Please advise if others are experiencing similar issues and what steps I can take to resolve this. I want to test my changes effectively. |
I think you haven't add required field in resources folder. |
@ajaynegi45 |
@ajaynegi45 While testing the recent changes, I temporarily disabled authentication for the relevant endpoints to ensure everything else was functioning correctly. This allowed me to validate that the logic was correct and that all expected flows were working as intended. I’ve attached the relevant screenshots in my PR for your reference. |
https://www.linkedin.com/in/rishabh-singh-rawat-408762289/ He added the this feature. Ask your issue with him @rishabhrawat05 can you resolve this issue |
@ajaynegi45 Thank you so much for your help so far. I will ask my issue to @rishabhrawat05. I temporarily bypassed the issue to test my changes, and everything is working correctly. It would be great if you could review my PR #89 so I can wrap this up and move on to a new issue. |
Hey! Can you please share some screenshots of the error you are receiving while starting the application and also share screenshot of your application.properties file and application.production file. |
Hi @shreya5653, I saw your message about the redirect issue after logging in. Just to clarify, are you experiencing the redirect problem with the OAuth login or the basic login? Knowing this will help us assist you better. Also, if you could share any relevant screenshots that @rishabhrawat05 requested, that would be really helpful. |
@Guhapriya01 @rishabhrawat05 I am experiencing the redirecting issue when I try to log in using 0Auth and bad credentials using basic login. Here are the screenshots |
Is there any error showing up in terminal and also can you use this jwt.secretKey=eyJhbGciOiJIUzI1NiJ9.eyJSb2xlIjoiQWRtaW4iLCJJc3N1ZXIiOiJJc3N1ZXIiLCJVc2VybmFtZSI6IkphdmFJblVzZSIsImV4cCI6MTczMDEwNTk4MSwiaWF0IjoxNzMwMTA1OTg |
No not error as such only logs |
Ok try this jwt.secretKey=eyJhbGciOiJIUzI1NiJ9.eyJSb2xlIjoiQWRtaW4iLCJJc3N1ZXIiOiJJc3N1ZXIiLCJVc2VybmFtZSI6IkphdmFJblVzZSIsImV4cCI6MTczMDEwNTk4MSwiaWF0IjoxNzMwMTA1OTg |
@rishabhrawat05 Still the same issue . Request received for GET '/login': org.apache.catalina.connector.RequestFacade@6f3b1af5 servletPath:/login Security filter chain: [ This is what I get |
Did you test this on postman, |
For testing any endpoints 401 unauthorized error . I tested my endpoints by temporarily disabling the authentication for those specific endpoints |
Register also showing 401 unauthorised?? |
Yes |
Okay, I will review the code and error and then get back to you as fast as possible |
Okay Thank you so much @rishabhrawat05 . But I request @Guhapriya01 @ajaynegi45 to review my PR or at least let me know is my PR #89 under review coz this won't cause any conflicts with existing code. |
@shreya5653, sure! We’ll review it and let you know soon if any changes are needed. Regarding the error, since you’re receiving a 401 Unauthorized for all endpoints, it’s likely that the Bearer token isn’t being included correctly in the Authorization header, or it might be invalid. Please double-check to ensure that the token is included properly. |
Okay I will check it. Thank you so much! |
Hey! @shreya5653
Hope these changes will help project improvement, |
@rishabhrawat05 |
Happy to hear that |
Is this feature already requested?
Problem or Missing Functionality
The current system cannot send emails to subscribers, which blocks newsletters and notifications from reaching users. It also lacks unsubscribe options and proper email authentication. This feature will add email sending capabilities with reliable delivery and unsubscribe support.
Feature Description
This feature will enable the backend to send emails using an SMTP server (like Gmail or SendGrid) for newsletters and notifications. It will include authentication (SPF, DKIM, DMARC) to avoid spam issues and add unsubscribe options for users.
Screenshots
No response
Would you like to work on this feature?
Yes
Implementation Plan
The feature will be implemented by integrating an SMTP service to enable email sending. We will develop a service for composing and sending emails, add an unsubscribe option for users, and set up a retry mechanism for failed attempts. After testing the functionality, the feature will be deployed to the production environment, with ongoing monitoring for delivery reliability.
The text was updated successfully, but these errors were encountered: