Interesting interface! You don't appear to be on anymore though. ;D Anyway, you are welcome to contact me directly at [EMAIL PROTECTED] . . . or possibly even better, [EMAIL PROTECTED] Anyway, I don't see anything specific going wrong with this conversation. I also don't see any options settable from within adium x for aim. We may need to try it realtime. What version of PyAIM are you using?
Daniel On Jun 8, 2006, at 9:42 PM, Adam Thorsen wrote: > Daniel, > > The other client is Adium, but it doesn't appear to be auto > authorizing because the client doesn't appear in my contact list. > However, I am able to receive messages from/to my Adium account no > problem. > > (BTW- I offered the reward to entice you to use the webchat > interface at guruza.com instead of the mailing list. :) ) > > Here is what the sequence of jabber messages looks like: > > <iq type="set" id="aaefa" > > <query xmlns="jabber:iq:roster"> > <item name="n4rrowfe11ow" jid="[EMAIL PROTECTED]" /> > </query> > </iq> > > <presence type="subscribe" to="[EMAIL PROTECTED]" /> > > <iq from="[EMAIL PROTECTED]/Psi" type="set" id="push" > to="[EMAIL PROTECTED]/Psi" > > <query xmlns="jabber:iq:roster"> > <item ask="subscribe" subscription="none" > jid="[EMAIL PROTECTED]" /> > </query> > </iq> > > <iq from="[EMAIL PROTECTED]/Psi" type="set" id="push" > to="[EMAIL PROTECTED]/Psi" > > <query xmlns="jabber:iq:roster"> > <item ask="subscribe" subscription="none" name="n4rrowfe11ow" > jid="[EMAIL PROTECTED]" /> > </query> > </iq> > > <iq from="[EMAIL PROTECTED]/Psi" type="result" id="aaefa" > to="[EMAIL PROTECTED]/Psi" /> > > <iq from="[EMAIL PROTECTED]/Psi" type="set" id="push" > to="[EMAIL PROTECTED]/Psi" > > <query xmlns="jabber:iq:roster"> > <item subscription="to" name="n4rrowfe11ow" > jid="[EMAIL PROTECTED]" /> > </query> > </iq> > > <presence from="[EMAIL PROTECTED]" type="subscribed" > to="[EMAIL PROTECTED]/Psi" > > <x xmlns="vcard-temp:x:update"/> > </presence> > > <presence from="[EMAIL PROTECTED]" > to="[EMAIL PROTECTED]/Psi" > > <x xmlns="vcard-temp:x:update"> > <photo>482b02d125e39008d700ab4382042e1e0e3032b7</photo> > </x> > <x xmlns="jabber:x:avatar"> > <hash>482b02d125e39008d700ab4382042e1e0e3032b7</hash> > </x> > <c xmlns="http://jabber.org/protocol/caps"; node="http://pyaim- > t.blathersource.org/protocol/caps" ver="0.7c" /> > </presence> > > > On Jun 8, 2006, at 6:00 PM, Daniel Henninger wrote: > >> *chuckle* Why the $15 reward? >> >> Anyway, what client is the person on the other end (not using >> pyaim) using? It is possible to set up your client to auto- >> authorize all requests, which would prefer the authorization >> dialog. There's nothing specific about the way pyaim requests >> auth that should cause this. >> >> Daniel >> >> On Jun 8, 2006, at 8:43 PM, Adam Thorsen wrote: >> >>> I'm using pyaim-t with ejabberd. When I add a contact from one >>> IM client connected via the transport, the contact appears to be >>> added successfully. However, the client corresponding to the >>> contact added displays no authorization dialog. Is this the >>> expected behavior from AIM? >>> >>> $15.00 reward for help with this problem: >>> http://guruza.com/question/87/reward-15.00 >>> >>> Thanks, >>> -Adam Thorsen >>> _______________________________________________ >>> py-transports mailing list >>> [email protected] >>> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports >> >> _______________________________________________ >> py-transports mailing list >> [email protected] >> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports > > _______________________________________________ > py-transports mailing list > [email protected] > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
