How to configure webmail tools in django? - django

I configured mail for my django project. It worked as usual perfectly for gmail. But when I used this configuration for webmail it won't work. Someone pleas help me how to setup webmail configuration for django proejct.
I try for several time but it gives me error. I expect to send mail using my webmail.

Related

Open EDX - LMS : Unable to send verification email

I have a server setup for python 2.7. I have followed the below link for open edx setup and configuration.
Click here
After doing a lot of stuff, I have successfully run CMS and LMS on different domains. Everything is working except emails. When I registered from LMS, I didn't found verification mail. Because of that, I am not able to login to LMS system.
I have added SMTP details in lms.env.json
I have also replaced the console by smtp in aws.py, common.py
I have also restarted all the services after doing this but none worked for
me.
Please help me to get out of this.

Running Django on a Linux Server using Apache with HTTPS

I've been trying to figure this out for a while now and nothing I've found has really been helping.
I've got a remote Linux server running with Apache installed, and right now everything going to the server is redirected to HTTPS through Apache. This all works fine and I can access the files I need to normally, but now I'd like to also add in a Django site to my server under a new "subdomain". (For example I'd like to still be able to access non-Django files as usual 'https://www.thesite.com/path/to/file.php' and also be able to access the Django site like 'https://www.thesite.com/djangosite/some/site/page')
Could someone please give me some direction as to how I'd be able to do this? I can supply more information if it's needed.
Thanks in advance!
Edit 1: The Django server seems to dislike connecting via HTTPS and I'm getting an error that it can only support HTTP, but I need it because I want the site to be secure, and currently Apache is redirecting all HTTP requests to HTTPS, so do I need some other method of making it work?
https://www.digicert.com/ssl-support/apache-multiple-ssl-certificates-using-sni.htm
Check out SNI and also potentially wild card certificates

Why after deploying django docker container, emails getting sending failed?

I was working on django and everthing was working fine on my local machine as well as on heroku.
But than i deodorize my django project and it was working fine locally till now. now i have depolyed this container on my dedicated server and than i came to know that my emails was failing after deployment.
Can anybody have idea why my dedicated server is not sending mails?
I am sending mails using smtp protocol.
Any help or suggestion will be highly appreciated.
Thanks.
I'm assuming you're connecting to your local SMTP server to send out those emails.
The problem is that your Django is trying to use localhost:25 to send out the emails and in your docker there's no SMTP server. Docker has it's own network, and you can see what are the interfaces available by executing
ifconfig
To solve your issue, you should tell django to use your host SMTP server (and not localhost). Moreover you should tell your local SMTP server to accept emails coming from the docker network.

Magento 2.0 hosted on Google Cloud - Email/Smtp Issue

I have no computer knowledge, so here under a message from my developer to you :
"All the email related problems are occurring because the server is not able to fire mail.
The smtp details you provided are ok and are working at our server well. But when we try to fire a mail using the given smtp details on your server it shows an error.This is the testing url for smtp mail http://kzdiffusion.fr/smtpmailertest/testemail.php
Please ask the hosting provider to resolve the issue.
After that we will create an extension to send mail through smtp"
Can you please help with that problem above, please ?
My project is already delayed 2 months. Every tips that can help moving forward is a big plus. Google Support is not answering my emails anymore.
Best Regards,
David.
GCP blocks standard email ports , you can choose a non-standard port to send email through. You can also take advantage of the mail services offered by Compute Engine partners: SendGrid, Mailgun, and Mailjet.
See here: https://cloud.google.com/compute/docs/tutorials/sending-mail

Facebook Debugger unable to test localhost

I am building a Facebook app using Django. So, for development, I connected the app to localhost. My app is loading on canvas and working fine but the Facebook debugger is unable to test it correctly when I give localhost address as input.
These are the requests I tried in debugger
http://localhost
https://localhost/
http://127.0.0.1/
localhost
etc
Almost for all possible combinations.. It showed me
Error Parsing URL: Error parsing input URL, no data was scraped.
When I deployed the same code on heroku and tried.. It was working!
So,
Can't I debug the project on localhost? What's the point in working on it then??
If I can work, how should I fix it?
Can't I debug the project on localhost? What's the point in working on it then??
You can debug your code etc. on localhost – but of course you can’t have Facebook’s debug tool reach a site on your localhost, because Facebook (and everyone else on the web) does have no idea what machine your localhost actually is. (Absolute bascis, dude!)
If I can work, how should I fix it?
You have to make your web server accessible from the “outside”, over the internet.
Set up your test server so that it accepts requests from outside IPs, and get a DynDNS address (basically something that can be resolved by third parties like Facebook over the DNS).
You can access Facebook apps locally but you need to fake the domain of your local computer. You can do this by adding
127.0.0.1 mysite.test.example.com
to /etc/hosts. You should update mysite.test.example.com to your domain. Your Facebook app needs to be configured for that domain. You can then use the Facebook app locally and debug your project.
The alternative is to setup up a web server and use its domain for testing purposes (but this is not ideal because you'll need to commit and build the code before you can see your changes).