Re: [Django] #31784: Emails name over 75 characters are incompatible with the latest versions of python.

[Django]

#31784: Emails name over 75 characters are incompatible with the latest 
versions of
python.
-----------------------------+------------------------------------
     Reporter:  Nick Orr     |                    Owner:  nobody
         Type:  Bug          |                   Status:  new
    Component:  Core (Mail)  |                  Version:  2.2
     Severity:  Normal       |               Resolution:
     Keywords:               |             Triage Stage:  Accepted
    Has patch:  0            |      Needs documentation:  0
  Needs tests:  0            |  Patch needs improvement:  0
Easy pickings:  0            |                    UI/UX:  0
-----------------------------+------------------------------------

Comment (by Florian Apolloner):

 @Nick: How are you generating those emails in the first place currently? I
 nowhere see a possibility to specify an actual name in
 https://docs.djangoproject.com/en/3.0/topics/email/

 I also cannot reproduce it with:
 {{{
 In [12]: e = EmailMessage('subject', 'content', 'f...@example.com',
 ['t...@example.com' * 99])

 In [13]: e.message()
 Out[13]: <django.core.mail.message.SafeMIMEText at 0x7fc900437050>

 In [14]: e.message().as_bytes()
 Out[14]: b'Content-Type: text/plain; charset="utf-8"\nMIME-Version: 1.0
 \nContent-Transfer-Encoding: 7bit\nSubject: subject\nFrom:
 f...@example.com\nTo: \n
 
to@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.comto@example.co...@example.com\nDate:
 Tue, 14 Jul 2020 20:41:37 -0000\nMessage-ID:
 <159475929766.21330.4162456845040318158@apollo13>\n\ncontent'
 }}}

 I assume you are manually injecting `to` headers?

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31784#comment:10>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.739ae03f79e3e910293938ea01256dfd%40djangoproject.com.