Changes between Initial Version and Version 3 of Ticket #35713
- Timestamp:
- Sep 3, 2024, 4:11:40 PM (3 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #35713
- Property Triage Stage Unreviewed → Accepted
- Property Version 5.0 → dev
- Property Owner set to
- Property Status new → assigned
-
Ticket #35713 – Description
initial v3 21 21 Expected results: no `=?utf-8?...` encoded-word in the generated ''To'' addr-spec. And an error on the call to `send()` (or `message()`) saying that a non-ASCII local-part is not supported. 22 22 23 There is ''no'' supported way to send to non-ASCII usernames using 7-bit email headers. That requires using 8-bit headers with the SMTPUTF8 extension under RFC 6530/6531/6532. ( I'll open a separate feature request ticket about that; this ticket is solely about removing the current buggy behavior.)23 There is ''no'' supported way to send to non-ASCII usernames using 7-bit email headers. That requires using 8-bit headers with the SMTPUTF8 extension under RFC 6530/6531/6532. (That new feature request is ticket #35714; this ticket is solely about removing the current buggy behavior.) 24 24 25 25 For more details see [https://code.djangoproject.com/ticket/25986#comment:12 #25986 comments 12-13].