Somewhat OT as this may not be CentOS/EL-specific. I am seeking help in trying to determine why the combination of my work e-mail server and evolution is usually, but not always, giving the error
Error verifying signature Cannot verify message signature: Incorrect message format
on signed messages (such as those from Ralph Angenendt and Johnny Hughes), and refusing to display them; while the same messages are readable with a webmail interface, in the list archives, or when they go to my home address that is also subscribed to some of the same lists (same version of evolution at home and work). This problem only started last week and the origin is probably related to infrastructure upgrades on the mail server, over which I have no control.
Google has not come through on this one . Many of the results seem to lead to sources or change-logs containing the strings, not to similar problem reports of fixes. Can't find anything relevant in bugzilla.gnome.org, bugzilla.ximian.com, bugzilla.redhat.com, or bugs.centos.org. Have searched without success in the evolution docs and on-line for a way to turn off the checks in evolution so the message will display.
Has anyone else seen this behavior?
Anyone have a fix or work-around?
Thanks, Phil
On Tue, 2007-03-13 at 16:35 -0400, Phil Schaffner wrote:
Somewhat OT as this may not be CentOS/EL-specific. I am seeking help in trying to determine why the combination of my work e-mail server and evolution is usually, but not always, giving the error
Error verifying signature Cannot verify message signature: Incorrect message format
on signed messages (such as those from Ralph Angenendt and Johnny Hughes), and refusing to display them; while the same messages are readable with a webmail interface, in the list archives, or when they go to my home address that is also subscribed to some of the same lists (same version of evolution at home and work). This problem only started last week and the origin is probably related to infrastructure upgrades on the mail server, over which I have no control.
Google has not come through on this one . Many of the results seem to lead to sources or change-logs containing the strings, not to similar problem reports of fixes. Can't find anything relevant in bugzilla.gnome.org, bugzilla.ximian.com, bugzilla.redhat.com, or bugs.centos.org. Have searched without success in the evolution docs and on-line for a way to turn off the checks in evolution so the message will display.
Has anyone else seen this behavior?
Anyone have a fix or work-around?
Thanks, Phil
Not sure of the full fix ... but you need to import the public key to be able to validate the messages.
You may have something set so that signed messages (even those in clear text) must be validated before they can be read.
For me ... you can download my CentOS.org / CentOS list public key here:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6AC163B3
Thanks, Johnny Hughes
On Wed, 2007-03-14 at 08:31 -0500, Johnny Hughes wrote: ...
Not sure of the full fix ... but you need to import the public key to be able to validate the messages.
You may have something set so that signed messages (even those in clear text) must be validated before they can be read.
No setting that I can find to control this behavior, and this has not been a problem until very recently. The usual behavior until last week has been that Evolution would complain about an invalid key, but still display the message. Now the message content is effectively lost. To see your message to which I am replying I had to go to the list archives to read it and "paste quotation" to supply the context. See
http://bugs.centos.org/view.php?id=1789
http://bugzilla.gnome.org/show_bug.cgi?id=418608
for gory details.
Phil
On Thu, 2007-03-15 at 16:00 -0500, Jeff Stacey wrote [off-list]:
You could do what I do when I get this problem and hit reply.
It works on Evolution 2.8.1 (on Ubuntu)
I only see this problem with email from Rodrigo Barbosa Johnny's seem to display fine just warning of an invalid signature.
If you're seeing the problem at all, it is of interest. As you can see from the BZ reports it seems to be rather random, although a consistent problem. Would appreciate any comments added to the BZ entries, particularly the upstream one:
http://bugs.centos.org/view.php?id=1789
http://bugzilla.gnome.org/show_bug.cgi?id=418608
Phil