bad telegrams and qsps when syncing a new server

[zem]

There are many of those, there is a bug in the processor somewhere that causes messages to go stuck here

[zem]

2015-06-10 17:32:08 UTC processing file qsp_oe1src_e4a5747a9ab8545e3f6433ea4bb2003244616a
ca5eabf1fd555786f9b3cb68ea.qtc
2015-06-10 17:32:08 UTC processing file pubkey_la3jra_e6fc20b53a0bdc0b6db8a7cd9789c568615
0ee28c1de32e021d1faae41f4a968.qtc
Message Signature Check is done
check for revokes of this key passed
older keyversions done
key linked to target
2015-06-10 17:32:08 UTC processing file qsp_oe1src_72058448c001f18acda995118d51fc8ad2991b
e2f7df0a1bf0a2d5fc29791c8f.qtc
2015-06-10 17:32:08 UTC processing file telegram_oe1lfb_ab3d5eb6a40f719bd2aefe6f25355df25
e01c0ccfc2a5e54beb2286942c5c8a5.qtc
$VAR1 = bless( {
'call' => 'oe1lfb',
'tree' => {},
'keys' => [],
'keyhash' => {},
'selfsigned_to_delete' => [],
'root' => '/var/spool/qtc/messages'
}, 'qtc::keyring' );
2015-06-10 17:32:08 UTC Uuuuuuups there are no keys there for oe1lfb
2015-06-10 17:32:08 UTC processing file pubkey_oe3kab_02d4d1eaa4c035d7c18c2d8e39d4ef9c52609c9f62eaeea820edad52671afb69.qtc
Message Signature Check is done
check for revokes of this key passed
older keyversions done
key linked to target
2015-06-10 17:32:08 UTC processing file qsp_oe1xgb_82cbab5126e20af3f3f8e2b24c4ed7339f6158bfc03ef2c647960fdab7ab99af.qtc
2015-06-10 17:32:08 UTC processing file qsp_oe1src_83bee48fd3a1fafe77acff296fb4129f2c289cc0f11a74f59ed244d584a078bd.qtc
2015-06-10 17:32:08 UTC I do not have a key to verify with
2015-06-10 17:32:08 UTC processing file pubkey_oe1rpw_47f2edf68ac1bfeb9ee7716f17256a414214d704ebbb0047b99edbf8a1c93736.qtc
Message Signature Check is done
check for revokes of this key passed