Hi, On Friday, 2022-01-14 14:36:13 +0300, Jean Louis wrote:
> > > It MAY, and it MAY NOT. There is no strict rule to it. > > > > Indeed, it doesn't say "MAY NOT", so that "Re: " is not forbidden. > > But this does not mean that other prefixes are allowed. > > Quite contrary, my understanding is that it implies that anything is > allowed in the Subject: line. That is foundation of basic freedom for > people to choose how their subject line should or would be. > > Better file bug report on that RFC because what kind of standard it > is when it just provides vague instructions with "MAY". It was > capitalized with intention for people to understand that "MAY" implies > "OR MAY NOT". Suggested reading: https://datatracker.ietf.org/doc/html/rfc2119 specifically https://datatracker.ietf.org/doc/html/rfc2119#section-5 > The point and conclusion is all written in the RFC, this mutt settings > is just fine. It may be there and may be not. RFC says it. https://datatracker.ietf.org/doc/html/rfc5322#section-3.6.5 | When used in a reply, the field body MAY start with the | string "Re: " (an abbreviation of the Latin "in re", meaning "in the | matter of") followed by the contents of the "Subject:" field body of | the original message. A "Re: " in a reply is optional. It does not say that anything else may prefix the original Subject. Eike -- OpenPGP/GnuPG encrypted mail preferred in all private communication. GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A Use LibreOffice! https://www.libreoffice.org/
signature.asc
Description: PGP signature
