Hello, i am using smack api to interact with an openfire server with IM Gateway plugin installed. In order to emulate “blocking” behaviour i use a privacy list where all that boring peolple goes, then i dend this guys an unavailable presence in order to dissapear from thier roster. This works fine between openfire users, howeber it is not the case with users from transports.
The problems seems to be the outgoing presence out, wich does get blocked with openfire users. If i change my presence, the openfire user does not recieve it but the (MSN) transport does. The incoming messages are blocked, this is what gets me really confused. It seems a problem just with the presence.
I am using openfire 3.5.1 along with IM Gateway 1.2.3.
Thanks to anyone who spend some time with my problem.
Are you trying to block logging into the transport at all? You can’t block to individual users at legacy networks through the im gateway plugin because they don’t care about your xmpp status. The only thing that does is, for example, msn.yourserver.org. (the MSN transport) It hears you come online and once you come online in MSN land, privacy lists in XMPP land no longer matter. (thought they may block incoming messages before they get to you, but the MSN user will never know they didn’t get through to you, which is probably fine) Anyway. Adding privacy list support to the plugin is on the roadmap. Basically the plugin itself will have to handle privacy lists and translate that to something that works in the legacy service. So like if you blocked someone via XMPP privacy lists, the MSN transport would see that and go ok, and put them on your MSN “blocked” list as well.
However, if you are trying to block the MSN transport itself from seeing you online, that’s a different story. Was I correct in what you were after or were you wanting to block the transport itself?
Thanks for your quick reply! I did not expect it so soon!
Was I correct in what you were after or were you wanting to block the transport itself?
Yes, i am sorry to hear that. I was really hoping to block outgoing presence to an individual from a transport. I was not trying to block the whole transport unfortunately. That seemed to work fine, but it is not the task here.
Anyway. Adding privacy list support to the plugin is on the roadmap.
I am really looking forward to it
Howeber is not there a way to send a presence status just to a single transport individual? That would do. But really seems like the same problem, does’t it? ja!