-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
assp v1.7.5.5
perl v5.8.6
When ASSP adds its header entries to the end of the header, it does so
incorrectly. All of the relevant headers are collected in a string and
then that string is encoded instead of each header's entry value.
For instance:
=?UTF-8?Q?X-Assp-Version: 1.7.5.5(1.0.02) on
assp1654-stable=0D=0AX-Assp-Re-noProcessingDomains:
sourceforge.net=0D=0AX-Assp-Delay: [email protected] not delayed
(noProcessingDomains); 20 Jun 2010 21:09:29
- -0700=0D=0AX-Assp-Envelope-From:
[email protected]=0d=0ax-assp-intended-for:
[email protected]=0d=0ax-assp-passing:
noProcessingDomains=0D=0AX-Assp-ID:
assp1654-stable =0D=0A?=
The encoding appears to be hard coded for utf-8 in "sub headerFormat()".
- --
James Moe
jimoe at sohnen-moe dot com
520.743.3936
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkwfzKoACgkQzTcr8Prq0ZNLZACfYRa+VetT95HkrjJjAm+A7EOE
14MAoIRowLbc/ERa+dGiU9+bvwcdJW14
=ptgx
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user
