Email Verifications & Notifications - Deployment with Django - Part 5 

Thank you. Good luck 😉

Hmm, by default allauth targets the primary email for the user, so it shouldn't be necessary to declare it explicitly. Do you declare the primary_email manually like this: primary_email = user.emailaddress_set.filter(primary=True).first()

@@ajudmeister more or less, yes: ```python primary_email = request.user.emailaddress_set.get(primary=True).email send_email_confirmation(request, request.user, email=primary_email) ``` Anyways it's working now. Thanks for being so responsive!

Yea, probably because it involves many services outside django, which get updated all the time, and the implementation can change at any time too.

It's not possible to hide javascript code from the users as js executes in the browser. You can make it hard to read by minifying it, but users will always be able to get it and reverse engineer it. If you have sensitive logic you don't want to be public you need to write it on the server side eg. with python and send only the necessary data to the browser.

Error number 10109 typically indicates a network-related issue, so not Django or Email specific. Could it be a network connection issue or Firewall block? Check if all the configurations are set up correctly (SMTP, SSL/TLS)

@@ajudmeister Thanks for your quick response sir. i tried using env variables with f-string and it worked for me . thanks a lot .You are doing a nice Work keep it up. Hare Krishna 🙏.