Hi
The problem is that 1 works and 2 doesn't:
1.
FROM is encoded as "FRIENDLY_NAME <EMAIL_ADDRESS>" == encoding ==> "base64"
2.
FROM is encoded as "FRIENDLY_NAME <EMAIL_ADDRESS>" == encoding ==>
"base64 <EMAIL_ADDRESS>"
This means that if the entire FROM content is encoded, "author's ticket
app" cannot read it. He probably doesn't even try to decode from, he
just looks for an e-mail address and if he doesn't find it, it "hangs"
and programmer say "thats problem is in postfix ...."
And I would like to prove to him that it is better to improve the
application than to play around with postfix because you can cause a big
problem
I don't want to kick with the horse...
W dniu 19.03.2024 o 11:43, Erwan David via Postfix-users pisze:
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 his
application hangs and instead of correcting it, he sends me to block
such e-mails using Postfix.
Allowed (by the RFCs) syntaxes for addresses being very diverse, there
is much chance that his application refuses a perfectly valid address,
Much more than postfix allowing an illegal syntax.
--
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
