Accept failure to verify signature during speculative check
Previously, the tool would stop before examining the directive file if the
signature did not match a keyring somewhere. Plans to replace this check
with a single check against the collected master keyring ran afoul of plans
to eliminate the collected master keyring. Current future plans are to use
an index mapping long key IDs to email addresses to replace this, since GPG
will report the long key ID used to produce a signature even if the key is
not in the available keyrings.
This changed the email sent in two cases in the testsuite, which has been
adjusted accordingly in this commit. Concerns about unauthorized parties
abusing the mechanism to spam ftp-upload-report are not relevant here,
since a reuse of a valid directive with a bogus file would be sufficient
to cause mail to be sent to that box. In short, that is a separate issue.