-
**Version:**
- listmonk: 2.4.0
- OS: Debian bullseye
**Description of the bug and steps to reproduce:**
The `MIME-Version` header is written as `Mime-Version` and that triggers a check on Rspa…
-
### Describe the bug
When using [MultipartReader](https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.webutilities.multipartreader) to read a request, the [ReadNextSectionAsync](https://…
-
### Steps to reproduce
```ruby
# frozen_string_literal: true
require "bundler/inline"
gemfile(true) do
source "https://rubygems.org"
git_source(:github) { |repo| "https://github.com/…
-
- In http/s sources, binary contents are specified by setting headers defined within MIME-type spec (RFC-2045). While data is serialized to text format during transmission, at client's app level is re…
-
The references in 5.2.3, 5.2.5.2, and the informative bibliography to ISO 3166 are incorrect; they should instead be to RFC 3066.
Enhancement: the normative reference should be to BCP 47 instead.
-
In "Table 285 — Additional entries in a media clip data dictionary", the **CT** entry states:
> The string should conform to the content type specification described in Internet RFC 2045.
All ot…
-
### Issue Description
The host is registered to Satellite which has SCA (Simple Content Access) enabled.
SCA/Subscriptions work fine (are finally usable) on the host after:
https://community.th…
-
Update the spec to require that implementations require that a dialect is declared. Implementations MUST refuse to evaluate schemas without a known dialect.
In order of precedence, a dialect can be…
-
The casing for `Mime-Version`, `Content-Id`, and `Message-Id` in [RFC 2045](https://www.rfc-editor.org/rfc/rfc2045) appear to be `MIME-Version`, `Content-ID`, and `Message-ID`. The header keys are…
-
# 概要
rstのロール名がブラウザの表示に見えてしまっています。
ブラウザ(chrome)での表示をコピーすると、
============
[email](https://docs.python.org/ja/3/library/email.html#module-email) パッケージは、電子メールメッセージを管理するライブラリです。 特に、SMTP([:rfc:`28…