On 9/19/06, Jeremie Kilgore <[EMAIL PROTECTED]> wrote: > I was curious if there was a way to only stop a certain jid from > registering with PyMSNt?
If you're using ejabberd, then just add some acl's. Otherwise (like the reset of us) you're out of luck atm, because PyMSNt doesn't support this as far as I know. -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Tue Sep 19 20:55:56 2006 From: [EMAIL PROTECTED] (Norman Rasmussen) Date: Tue Sep 19 20:56:01 2006 Subject: [py-transports] PyYIMt setup problems - cont. In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On 9/19/06, Les Seigneur <[EMAIL PROTECTED]> wrote: > The transport did appear in the Psi roster. Also, after I made some changes > to the config.xml file it now appears in the Exodus Roster too. I am also > able to successfully add a Yahoo user in Exodus and Psi now! I made the > following changes in the config.xml file and they seemed to make the > difference: > I commented out the vanity address: > <!-- <host>jabberserver.uark.edu</host> --> Very strange, this should not have effected Exodus, but not Psi - maybe the transport restart fixed it? > I changed the mainServerJID from > <mainServerJID>jabber.jabberserver.uark.edu</mainServerJID> > to > <mainServerJID>jabberserver.uark.edu</mainServerJID> This setting is only used to ignore service discovery requests for the confjid. > Another issue that I see in Psi is that when I bring up the Service > Discovery window "Yahoo Transport Chatrooms chat.yim" appears under the > "Yahoo! Transport entry. At the current time I am not using Yahoo Chatrooms > and I would rather not advertise something that is not enabled. How can I > get rid of "Yahoo Transport Chatrooms chat.yim" in the discovery window? > BTW I have commented out the <confjid> tag in my config.xml file. so based on the above logic, you need to set the mainServerJID to whatever JID the server uses to 'discover' support on each transport. With jabberd2 this would be 'jabberserver.uark.edu'. > Does this make sense to you that these changes may have made the difference? Changing the host address only affect your ability to make a succesful conntion to the yahoo network. Changing the mainServerJID only affects the disco response from the confjid. So no, changing these shouldn't make a difference between clients. More likely is that the clients are doing something subtly different. > I am still seeing the "Unknown notify event: /presence/subscription" error > in the Exodus debug window when I add a yahoo user with Exodus but this may > be an Exodus problem. Does Psi have a debug window so I can compare the two > clients when adding a Yahoo user? Yes, right click your account entry, and select the XML Console, tick Enabled. > Also, in Psi when I am adding a Yahoo user and I choose > yahoo.jabberserver.uark.edu from the Add User window I see this message: > > "The service may not support this feature. In this case you may need to > enter the Jabber ID manually for the contact you wish to add. Examples: > [EMAIL PROTECTED] of Yahoo Transport]" > > Is this because PyYIMT does not support this feature or is there something > else I need to change? PyYIMt doesn't support this feature yet. On 9/19/06, Arnaud Ab?lard <[EMAIL PROTECTED]> wrote: > Les Seigneur wrote: > >> Here is another problem. When I am register with the Yahoo Transport it > >> looks like the registration is successful but the Yahoo Transport never > >> shows up in my Roster. > > I've also noticed that behavior lately.. actually it works smoothly for > a while then start acting like weirdly like this, then it works again > after a while. very strange. It's happy on my jabberd2 server. Just to double check, can you guys post which version of the transport you're using (revesion should be on the second line of yahoo.py) > When it doesn't work properly, the transport says the registration went > ok, but nothing shows up in the roster. When a registrered user tries to > log on the transport, it says ok, but for each contact the transport > gets a 404 cancel error: > > <iq xmlns='jabber:client' to='[EMAIL PROTECTED]/Gajim' > type='error' id='2935' > from='[EMAIL PROTECTED]'> > <vCard xmlns='vcard-temp'/> > <error code='404' type='cancel'> > <item-not-found xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/> > <text xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'>The addressed JID or > item requested cannot be found.</text> > </error> > </iq> This is the broken vcard support showing up. It seems to be releated to avatar's. The code needs to be changed to return a 'valid' vcard even if there's no avatar for the user - and probably to broadcast the user's current avatar hash as part of the presence too. -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Tue Sep 19 23:57:01 2006 From: [EMAIL PROTECTED] (James Bunton) Date: Tue Sep 19 23:57:12 2006 Subject: [py-transports] PyMSNt Dis-allow users to register. In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On 20/09/2006, at 2:42 AM, Jeremie Kilgore wrote: > I was curious if there was a way to only stop a certain jid from > registering with PyMSNt? > > > Jeremie Kilgore You could find out what file they would be registered as in the spool directory and create it, then remove permission from PyMSNt to modify it. The hash is the first three characters of the hex md5 digest of the full JID. So abc/[EMAIL PROTECTED] should be not writeable by PyMSNt. Also do the same for abc/[EMAIL PROTECTED] (a temp file that is used) to make things work a bit nicer. --- James
