Hi, Axel
I'm _vt from spectrum room 
A lot of openfire users complain about spectrum2 setup with openfire and can't getting it work.
I have try to setup openfire and spectrum and found the problem: openfire does not push transport jid to user roster. It must be there and subscription must be approved in "both" ways, then spectrum will able to detect user connect/disconnect and sends proper presences from contacts. The only way to make spectrum work - is add spectrum jid manually.
At first, the problem is in openfire core: when user have registered on transport - transport check remote roster support by sending jabber:iq:roster request to server jid from transport jid. If server reply with error - then spectrum considers remote roster is not supported and sends subscription request to user and when user approve it - it pushed to user roster and transport will work normal. But Openfire replies with empty result, which is a bug - it should send an error response, because we cannot access to user roster.(See http://xmpp.org/rfcs/rfc6121.html#roster for details). Transport receive empty result, consider server is supporting remote roster and trying to push contacts directly, which doesn't work, because server reject pushes from unapproved jid. So the whole registration flow is broken: user must add transport jid to roster manually to work properly, receive tons of subscription requests from his contacts and only after that it will work more or less normal.
The second problem is gojara - it does not resolve the first problem properly
It approve somehow transport jid for roster pushes, but it should push transport jid first when user just registered. If it will do it, then "gajim workaround" will not need Anyway, this workaround works only first time, if I check "persistent roster" option, which should be default, as I think
If you have any questions - please, contact me in spectrum room.