> |-----BEGIN PGP MESSAGE-----
> |Charset: ISO-8859-1
> |Version: GnuPG v1.2.3 (GNU/Linux)
> |Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> ...encrypted mumbo jumbo...
>
> |-----END PGP MESSAGE-----
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFABZ2RV/+PyAj2L+IRAjIIAJ9RTCJ1RFVKi331sFB3E5+hFtNUHwCgmAGA
> 3aG8jw9h+fd8rhQrhWl29Ik=
> =UQf7
> -----END PGP SIGNATURE-----
>
based upon these tests, that signature looks like it matches... does
the + need to be \+ in __PGP_MIDDLE maybe?
rawbody __PGP_BEGIN /^-----BEGIN PGP SIGNATURE-----$/
rawbody __PGP_MIDDLE /^[0-9A-Za-z+\/]{64}$/
rawbody __PGP_END /^-----END PGP SIGNATURE-----$/
question i have is... what if the message was encrypted but not
signed.... should this change the meta tests?
rawbody __PGP_BEGIN /^-----BEGIN PGP
(SIGNATURE|MESSAGE)-----$/
rawbody __PGP_MIDDLE /^[0-9A-Za-z+\/\=]{64}$/
rawbody __PGP_END /^-----END PGP
(SIGNATURE|MESSAGE)-----$/
??
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
