I am an Engineering Physics graduate from IIT Guwahati, but merely not restricted to Physics itself. In the past few years, I involved in many Cybersecurity blogging and now on Open-source.
I found the possible issue location, which might give incentives to the dev team. I will also update the post accordingly.
Both the Sendgrid and Sendinblue SMTP details are working, I confirmed this by using the send_email feature within the admin panel(people section). Also, the during the forget password the user was able to receive a password reset instructions.
I am an Engineering Physics graduate from IIT Guwahati, but merely not restricted to Physics itself. In the past few years, I involved in many Cybersecurity blogging and now on Open-source.
So, the issue was resolved with one exception of unable to reset the values to "No Value". Like, unfortunately, I was not able to remove the domain restriction in signup.
How SMTP issues can be resolved.
Unset and Re-SET the default_email from the server (cannot be done using Admin panel).
If domain was not authenticated in send-grid, we should create a sender email within send-grid with the same email as of default_email and not as noreply@example.com
But there are some issues with previous users, but new users have no issues; so configuring SMTP as early as possible in Forem Admin setup should be encouraged.
Persisting Issue
As mentioned above and many times, the admin was not able to undo the changes to no value.
Admin should have the ability to reset the changes he has done. Even though the problem with SMTP was resolved, I cannot remove domain restriction and added gmail as an acceptable domain(which is a bit weird)
if domain was not authenticated in send-grid, we should create a sender email within send-grid with the same email as of default_email and not as noreply@example.com
Ultimately, we can't account for every possible combination of user error, and our documentation attempts to address the issue of domain authentication for Sendgrid as well as other transactional mail providers. If we create conditional settings for specific email providers, we then take on responsibility for maintenance and upkeep of those settings as email providers change their own protocols. Our roadmap plans to broaden the possible reach of Forem, rather than tailor the product to specific third-party services, so instead we do our best to maintain documentation and continue to urge people to address the docs with their questions.
configuring SMTP as early as possible in Forem Admin setup should be encouraged.
Following the documentation as advised in the repo would lead users to understand the importance of SMTP creation earlier in the process. Maybe we need to push the docs harder so users understand that they should probably read ahead rather than choose their own adventure?
I am an Engineering Physics graduate from IIT Guwahati, but merely not restricted to Physics itself. In the past few years, I involved in many Cybersecurity blogging and now on Open-source.
Ok, at least that is working as expected! Thanks for confirming :)
I found the possible issue location, which might give incentives to the dev team. I will also update the post accordingly.
Both the Sendgrid and Sendinblue SMTP details are working, I confirmed this by using the send_email feature within the admin panel(people section). Also, the during the forget password the user was able to receive a password reset instructions.
Great to hear that! Looking forward to getting more info on this one from you, and appreciate your perseverance as always!
So, the issue was resolved with one exception of unable to reset the values to "No Value". Like, unfortunately, I was not able to remove the domain restriction in signup.
How SMTP issues can be resolved.
default_email
from the server (cannot be done using Admin panel).default_email
and not asnoreply@example.com
Persisting Issue
no value
.Thanks for updating this post, @akhil
there is a current PR for being able to clear the fields for SMTP settings that should help fix some of the issues you're experiencing.
Ultimately, we can't account for every possible combination of user error, and our documentation attempts to address the issue of domain authentication for Sendgrid as well as other transactional mail providers. If we create conditional settings for specific email providers, we then take on responsibility for maintenance and upkeep of those settings as email providers change their own protocols. Our roadmap plans to broaden the possible reach of Forem, rather than tailor the product to specific third-party services, so instead we do our best to maintain documentation and continue to urge people to address the docs with their questions.
Following the documentation as advised in the repo would lead users to understand the importance of SMTP creation earlier in the process. Maybe we need to push the docs harder so users understand that they should probably read ahead rather than choose their own adventure?
Now the PR was merged and the issue was resolved. I also updated the post accordingly.
Great news! Glad to hear it's working for you now!