Re: Email::Address::XS

--huq684BweRXVnRxX
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* [email protected] [2016-09-12T03:26:52]
> And as I wrote if Email::MIME is not good place, then what about other
> modules like Email::MIME::Header::Address (or invent other name) which
> will use Address parse/format functions and will also do that MIME
> encode/decode procedure? We can maybe add classes also for other headers
> (like you suggested for DKIM signatures, etc...).

I had started to write a lot of reply on the previous parts of your email, =
but
I think that this is the only part that really matters in the end.  Yes, I
think some thing like that is sufficient.  In the end, I think what's best =
is:

* a thing that can take a raw (encoded) header string and give you an object
* ...which is an object with access to the header's structured data
* ...which you can turn back into a raw header to store as needed

With that facility, people can plug in (header =3D> class) configuration and
things just go.  We can start off suggesting, for example, an address one.

--=20
rjbs

--huq684BweRXVnRxX
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJX3HQ0AAoJEOYby6cMccU5T14IALCre0FnX8TKVhtZ03f2MSxx
1qklSLLbJr2MkYEMdFGf0EnQHj7l4Dhhgp0Z0WieEX16LmJT2TnKBX4bWi516kre
UE3FNx8Q3VWFy5SC/ffU+P0CetALN0/sQZFXr1zX4s61ccMv6i/6qA/D7GdAxiuV
UvoLt6ideYgVJiLwGBFKTRAc3ebAeJsQx6nuOxzzhdfsdD9zmvZ1xpSkExEo3Zu9
k6vNJJmKuPPrd11VToTXYSaqoFDxLbEBJOfQNa0lgelkR3WEhYmFE22ryhxyFglx
Q/GUPwQDoOMXdW9u2X1300jUtYm7dCJ7SPCbuDHp8EGC0IwEiWBPBSLE5zq6FwI=
=1pTI
-----END PGP SIGNATURE-----

--huq684BweRXVnRxX--