-
According to [RFC 2047](https://www.rfc-editor.org/rfc/rfc2047#section-8) an encoded word cannot be longer than 76 characters (including everything). So a longer subject line should be split and encod…
-
### Checklist
- [X] I have used the search function to see if someone else has already submitted the same bug report.
- [X] I will describe the problem with as much detail as possible.
### App versi…
-
Add support for
-
`DecodeHeader('=?utf-8?B?0JDQn9CV0JrQodCe0KTQojog0JfQsNC60LDQtyDQv9GA0LXQ?= =?utf-8?B?t9C10L3RgtCw0YbQuNC4?=')`
Expected: `АПЕКСОФТ: Заказ презентации`
Actual: `АПЕКСОФТ: Заказ пре??ентации`
He…
-
The CoAP spec in RFC 7252 defines number ranges for options:
```
+-------------+---------------------------------------+
| Range | Registration Procedures …
h0ru5 updated
7 years ago
-
Need to carefully examine where it is appropriate to use `ByteString` and where it is appropriate to use `Text`. For instance, headers currently return `Text` values... but are all HTTP headers encode…
-
Headers should (as required) use RFC2047 encoding when being coerced into a string for inclusion in a MimeMessage.
It should:
- [ ] Support determination of charset encoding as determined by the user…
-
# Description
When a URL appears in text, the internal editor renders it as a hyperlink, even if the Markdown source has no link sequence.
An example is as follows:
```
http://some.domain.na…
-
**Describe the bug**
We are using the mail-api to parse incoming emails (MimeMessages), we received a particular email with a PDF attachment.
The filename of this attachment is encoded in the Conten…
-
I have this pair of lines in an email that fails DKIM signature verification:
`List-Unsubscribe: ,
`
If I merge them and remove the whitespace, the dkim signature verification succeeds as expect…