#6989: Inability to define DNS_NAME in django.core.mail results in e-mail 
being rejected or marked as spam
     Reporter:  Franklin             |                    Owner:  heathervm
         Type:  Bug                  |                   Status:  assigned
    Component:  Core (Mail)          |                  Version:  master
     Severity:  Normal               |               Resolution:
     Keywords:  local_hostname,      |             Triage Stage:  Accepted
  DNS_NAME, CachedDnsName, smtplib,  |
  SMTPConnection                     |
    Has patch:  1                    |      Needs documentation:  1
  Needs tests:  0                    |  Patch needs improvement:  1
Easy pickings:  0                    |                    UI/UX:  0

Comment (by Diederik van der Boor):

 To add, this issue also happens on Kubernetes pods.

 A standard Pod on Kubernetes has the following configuration:


 # Kubernetes-managed hosts file.       localhost
 ::1     localhost ip6-localhost ip6-loopback
 fe00::0 ip6-localnet
 fe00::0 ip6-mcastprefix
 fe00::1 ip6-allnodes
 fe00::2 ip6-allrouters    examplepod-77f687b9b9-5hlsg


 search NAMESPACE.svc.cluster.local svc.cluster.local cluster.local
 options ndots:5

 Hence email is submitted using `EHLO examplepod-77f687b9b9-5hlsg` and thus
 triggering spam filtering.

Ticket URL: <https://code.djangoproject.com/ticket/6989#comment:20>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to