aboutsummaryrefslogtreecommitdiffstats
path: root/contrib/ircbot/Sourcehut/README.md
diff options
context:
space:
mode:
authorRobin Jarry <robin@jarry.cc>2024-07-02 15:58:41 +0200
committerRobin Jarry <robin@jarry.cc>2024-07-02 22:12:45 +0200
commit44b14ebdff0e3da8df2348eeda27bfc2ec421fbb (patch)
tree8711abffa76e415dde14a67a671603fa27da586f /contrib/ircbot/Sourcehut/README.md
parentbee2fc62ac7808cf081e58947023cd4c61c0109e (diff)
downloadaerc-44b14ebdff0e3da8df2348eeda27bfc2ec421fbb.tar.gz
rfc822: be liberal with invalid address headers
Some email clients format email addresses with quotes around B encoded names. E.g.: "=?utf-8?B?U21pZXRhbnNraSwgV29qY2llY2ggVGFkZXVzeiBpbiBUZWFtcw==?=" This seems non standard. I tried reading the multiple RFCs that describe the MIME headers encoding but could not find any precise answer to determine if adding quotes around encoded words is valid or not. In any case, ParseAddressList completely ignores any encoding when it encounters a double quote. When that happens, try to detect it and force decoding a second time after the quotes have been removed. Link: https://datatracker.ietf.org/doc/html/rfc2045#section-3 Link: https://datatracker.ietf.org/doc/html/rfc2047#section-2 Link: https://datatracker.ietf.org/doc/html/rfc822#section-3.3 Reported-by: Bence Ferdinandy <bence@ferdinandy.com> Signed-off-by: Robin Jarry <robin@jarry.cc> Tested-by: Bence Ferdinandy <bence@ferdinandy.com>
Diffstat (limited to 'contrib/ircbot/Sourcehut/README.md')
0 files changed, 0 insertions, 0 deletions