*Title: Issue with socket.getfqdn Override Affecting Email Sending in 
Django*

*Body:*

Hello,

I’m encountering an issue with Django when trying to override the 
socket.getfqdn function to use a local hostname for email configuration. 
The override is causing errors when starting the Django development server, 
and I’m also unable to send emails from within the Django shell. 
Additionally, we are experiencing issues with email delivery related to 
user authentication with Djoser and JWT.
Problem Description

I’ve overridden socket.getfqdn to return a specific local hostname in my 
Django settings, but this results in the following error when running 
python manage.py runserver:
javascript
Copy code
TypeError: getfqdn() takes 0 positional arguments but 1 was given 

When I comment out the override, the server starts without issues, but I’m 
unable to test email sending. Here’s the relevant part of my code:
python
Copy code
import socket # Override the local hostname used by Django for sending 
emails EMAIL_HOST_LOCALNAME = 'localhost' socket.getfqdn = lambda: 
EMAIL_HOST_LOCALNAME 
Project Context
   
   - *Authentication:* We are building user authentication using Djoser and 
   JWT. User creation is successful, but activation emails are not being sent.
   - *Email Provider:* We are using Namecheap Private Email for sending 
   emails.

Expected Behavior
   
   1. *Server Start:* The server should start without errors.
   2. *Email Sending:* Emails, including activation emails, should be sent 
   successfully from within the Django shell and during user authentication 
   processes.

Actual Behavior
   
   1. *Server Start:* An error is raised due to the socket.getfqdn override.
   2. *Email Sending:* When the override is commented out, email sending 
   cannot be tested, and activation emails are not sent as expected.

What I Have Tried
   
   1. *Corrected Override:* I ensured that the override matches the 
   expected signature but still faced issues.
   2. *Console Backend:* Used the console backend for testing, which works 
   but doesn’t resolve the issue with the SMTP configuration.
   3. *Configuration Check:* Verified that all environment variables and 
   SMTP configurations are correct.
   4. *Djoser Settings:* Checked Djoser settings to ensure email sending is 
   configured properly.

Question

How can I correctly override socket.getfqdn without causing issues with the 
Django server, or alternatively, how can I resolve the email sending issues 
while using the correct configuration? Additionally, how can I ensure that 
activation emails are sent as part of the user authentication process?

Any guidance or suggestions would be greatly appreciated!

Thank you!

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/371861fc-02e3-4bdd-82c3-d389281b8d49n%40googlegroups.com.

Reply via email to