Description of Problem:
Mails signed (and/or encrypted) using pinegpg cannot be verified (and/or opened) using evolution itself.

Steps to reproduce the problem:
1. Email a signed mail using pine+pinegpg
2. The mail can be verified normally using pinegpg itself or by saving the mail in evolution and performing a "gpg --verify /path/to/file" or "cat /path/to/file | gpg --verify -"
3. The mail can't be verified using evolution itself (always results in bad sig., which it isn't)

Actual Results:
..

Expected Results:
..

How often does this happen? 
Always

Additional Information:
pinegpg doesn't use a signature.asc attachment. it signs the complete body and replaces that.

(OS : Redhat 7.2)