-
Before send mail, UTF-8 char will be encode with base64, which is difficult filted by
procmail.
I want to add a field: X-Subject-Pinyin, which can be generate from Subject fields, for example:
``…
-
**Describe the bug**
The Mime Header Decoding (RFC 2047) does not correctly resolve in case the display name contains an encoded comma.
The entire mailbox-list is decoded _before_ separated into dif…
Fabma updated
2 weeks ago
-
Vulnerable Library - jetty-http-9.4.31.v20200723.jar
Library home page: https://webtide.com
Path to dependency file: /jetty-servlets/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/reposi…
-
I receive the below error when importing a key, that has "pref-hash-algos" set to "101".
```
[...]
# off=892 ctb=89 tag=2 hlen=3 plen=323
:signature packet: algo 1, keyid [redacted]
version 4,…
-
Needs a separate, stateful codec, so probably will not implement without a sign of significant usage.
-
There are a various related issues; here are the two main ones. I note issues in bold in the description below.
* The documentation about when non-ASCII characters are allowed in S3 key and when they…
-
Continuation of the discussion in #4272
> [...] in my e-mail listing (index), some subject names shows those `?`.
>
> ```
> Google Payments | ??? ? ? ? ? ? ? ? ??Googl…
-
There is an HTTP response splitting vulnerability in the login redirection. When formatting the service parameter any control characters should be removed.
See https://www.owasp.org/index.php/HTTP_…
-
This library will only generate the extended filename parameter if the filename is not representable in ISO-8859-1 (checking against [NON_LATIN1_REGEXP](https://github.com/jshttp/content-disposition/b…
-
This is really probably a FLIM issue, but that repo has no Issues support at the moment.
`mime-charset-decode-string`, if indeed it is what's used to decode RFC2047-encoded header strings doesn't s…