Apparently my first mail decided to bomb..heres a quick recap if anyone cares...
Does anyone have an idea where Sylpheed-claws gets the check that eventually passes the "No public key to verify the signature"? I've been trying to figure out a way to fairly filter on this, but I'm at a loss now.I had thought to filter on the X-GPG header, but I have seen atleast one instance where this has been faked, and is unreliable as some mailers don't seem to include this either. I know this may be petty to some, but theres quite a few people who sign their messages but don't bother to upload their key, or include a pointer to their key in their .signature or other legitimate way to come by their key. I get to a message where someone has signed it, gpg cant find their key, I wait for the 30 second timeout, then I get to read their message, which in most cases takes longer to determine they have no key on their one or two line message than it did to read it. 30 seconds per nonfindable key and if this person makes a couple replies per day and theres a few users doing this, you can see that the compound lag starts to get irritating. So is there a way to tell Sylpheed to trash these mails or will it be easier to filter on the individual users? -- Chuck Brewer Registered Linux User #284015 Get my gpg public key at pgp.mit.edu!! Encrypted e-mail preferred.
pgp00000.pgp
Description: PGP signature
