-
# Bug report
### Bug description:
If a (legacy email API) email.message.Message is assigned an address header that is pre-encoded with RFC 2047, calling as_bytes(policy=default) can generate an …
-
Hi! 👋
**What's the problem this feature will solve?**
By following the [`pyproject.toml` specification](https://packaging.python.org/en/latest/specifications/pyproject-toml/#authors-maintainers…
-
**What tool do you want?**
A mime header (RFC 2047) encoder and decoder
**Describe the solution you'd like**
Encoder: an input box where you type your UTF-8 text and another box where the output …
-
# Bug report
### Bug description:
The modern email package incorrectly encodes a non-ASCII email address 'local-part' (username) using an RFC 2047 encoded-word, resulting in undeliverable email:
``…
-
For example, I'm getting
```
Subject: =?UTF-8?Q?Can_you_make_[Special_Event]?= _DevBeat_2013_â_Nov_12-13th?
```
-
For example, hectane converts `日本語 ` to `=?utf-8?q?=E6=97=A5=E6=9C=AC=E8=AA=9E_?=`, but according to RFC 2047, RFC 822 and related others, I think it should be `=?utf-8?q?=E6=97=A5=E6=9C=AC=E8=AA=9E?=…
-
The `Address.String()` method sometimes encodes as RFC 2047 after the 5322 formatting depending on the characters in the address. However some services (Ala sparkpost transmission api header fields) w…
epelc updated
4 years ago
-
It seems like the implementation doesn't respect the character limit on `encoded-words` specified in [RFC-2047](https://tools.ietf.org/html/rfc2047#section-2).
The following example string is 139 cha…
toonn updated
4 years ago
-
Should Endpoints use these for error message? It might be deprecated
Links:
* [RFC 2616 14.46 Warning](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html)
* [RFC 2047](https://tools.ietf.o…
-
BPO | [41553](https://bugs.python.org/issue41553)
--- | :---
Nosy | @warsaw, @bitdancer, @websurfer5
*Note: these values reflect the state of the issue at the time it was migrated and might not refle…