natan via Postfix-users:
> 1.
> FROM is encoded as "FRIENDLY_NAME " == encoding ==> "base64"
That form is NOT VALID. For proper encoding, please see
https://datatracker.ietf.org/doc/html/rfc2047#section-5
> 2.
> FROM is encoded as "FRIENDLY_NAME " == encoding ==>
> "base64 "
That form is valid,
On Tue, Mar 19, 2024 at 11:39:29AM +0100, natan via Postfix-users wrote:
> Hi
> I have one question regarding the RFC of the FROM field: in the message
> header.
>
> Is there any restriction that will force the FROM field to be correct
> according to the RFC?
Nothing builtin to Postfix.
> I'm as
Hi
The problem is that 1 works and 2 doesn't:
1.
FROM is encoded as "FRIENDLY_NAME " == encoding ==> "base64"
2.
FROM is encoded as "FRIENDLY_NAME " == encoding ==>
"base64 "
This means that if the entire FROM content is encoded, "author's ticket
app" cannot read it. He probably doesn't even
Le 19/03/2024 à 11:39, natan via Postfix-users a écrit :
Hi
I have one question regarding the RFC of the FROM field: in the
message header.
Is there any restriction that will force the FROM field to be correct
according to the RFC?
I'm asking because one client "parses e-mails strangely" and
