Page MenuHomePhabricator

Let PhutilEmailAddress encode addresses with complex display names somewhat properly
ClosedPublic

Authored by epriestley on Feb 8 2018, 4:52 PM.
Tags
None
Referenced Files
F13974177: D19026.id45622.diff
Fri, Oct 18, 4:24 AM
F13956065: D19026.diff
Mon, Oct 14, 4:06 AM
Unknown Object (File)
Wed, Oct 9, 8:45 AM
Unknown Object (File)
Tue, Oct 8, 3:19 PM
Unknown Object (File)
Oct 2 2024, 3:15 PM
Unknown Object (File)
Oct 2 2024, 4:33 AM
Unknown Object (File)
Sep 12 2024, 9:32 AM
Unknown Object (File)
Sep 12 2024, 9:31 AM
Subscribers
None

Details

Summary

Ref T13053. This is intended to replace the incomplete fix in D17831, which stopped some bleeding but is not correct for all inputs.

This mostly appears to implement the rules in RFC2822, which don't seem exceptionally complex from the escaping side, even though it is well established that no computer can ever successfully parse an RFC2822 address.

Test Plan

Added unit tests; ran unit tests.

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable