TroubleShooting GPG Errors

Do you have a key?

For an update to be successfully applied via GPG-signed email you should have first stored a GPG key in your account.

To export your key please execute the following command upon your system:

gpg --armor --export your.email.address

This will output a block of text which you should paste into your account page.

A sample key would look like this:

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.9 (GNU/Linux)

mQGiBDz05k4RBADTpjnB8kNOvv6nsPDi1y3E0orgyZAep0OvQ9DAhB++4ThzeOoD
33YRenpk+Dxa3+8tftAjd+/XvrieZTQBwG+CRKmi7MWKyeeN2PmU9+E569f89tjD
RvJWMU/9108LgTbgf/uodO0uvaZcNcVylKQv+nbJH9M+HtjBeW/DWMBPCwCg5JSU
...
...
...
nRp0AJ9jSvNZCauHObqvUGUx+AiCNz8OBACfZlaXlfXEkaKDf+NHRStvOKn/1pw=
=tGbT
-----END PGP PUBLIC KEY BLOCK-----

The GPG-key in your account is the only key that will be used to determine whether a message has been signed correctly.

Did you "clearsign" your mail?

Our system currently only supports the use of messages which have been signed with the --clearsign option.

Given an input like this:

add-user: foo
list-users:

You should be able to mail it to our system via:

cat input.txt | gpg --clearsign | mail example.com@updates.mail-scanning.com

The message that is send should look something like this:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

add-user: foo
list-users:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkiXECAACgkQwM/Gs81MDZ02zACeMF8VP0qXzkjCNkBypWp0pls3
LvEAni41R8qQQkkvhdCx/NTs84mQeY++
=3yZA
-----END PGP SIGNATURE-----

Still having problems?

If you're still having problems please get in touch and let us know about them.