gpg2 import fails with " this may be caused by a missing self-signature"

I tried to import a public PGP-key into my GPG keyring, but this failed: 

gpg2 -v --import /tmp/publicKey.asc                    
Version: OpenPGP totemomail
gpg: armor header:
Comment: totemomail OpenPGP - http://www.totemo.com
gpg: armor header:
gpg: can't handle public key algorithm 3
gpg: can't handle public key algorithm 2
gpg: pub     0s/XXXXXXXXX 2013-07-15  User Name <user.name@exmaple.com>
gpg: key XXXXXXX: unsupported public key algorithm on user ID "User Name <user.name@example.com>"
gpg: key XXXXXXX: unsupported public key algorithm
gpg: key XXXXXXX: skipped user ID "User Name <user.name@example.com>"
gpg: key XXXXXXX:X skipped subkey
gpg: key XXXXXXXX: no valid user IDs
gpg: this may be caused by a missing self-signature
gpg: Total number processed: 1
gpg:           w/o user IDs: 1

There is an option for gpg to be inserted into gpg.conf to allow the import:

allow-non-selfsigned-uid 

After this, the import works and the key is available in the keyring.