My understanding was that Y! changed their authentication protocol in such a way that yahoo-t (and other unauthorized software) would fail, but that was some time ago and the yahoo-t maintainers seem to have gotten around the problem. Perhaps Y! has changed things again because we know that they do *not* want unauthorized software connecting to their system (we were told on this list that there was an explicit internal company decision to become less open rather than more open).
Peter -- Peter Saint-Andre Jabber Software Foundation http://www.jabber.org/people/stpeter.php On Thu, 23 Jan 2003, Dov Katz (LIST) wrote: > Has anyone noticed that some of the other yahoo IPs that used to work no longer do? >Try the IPs resulting from nslookup of some addressed that used to work.... > > > Is a protocol change in the works? My Y! transport connects sends yahooized >username, then gets disconnected before receiving the challenge. > > Any insights are appreciated. > > Thanks > -Dov > > C:\>nslookup scsa.yahoo.com > Non-authoritative answer: > Name: scs-fooc.yahoo.com > Addresses: 216.136.173.172, 216.136.173.179, 216.136.175.226, 216.136.226.209 > 216.136.226.210, 216.136.233.132, 66.163.173.203 > Aliases: scsa.yahoo.com, scs.yahoo.com > > > C:\>nslookup scsb.yahoo.com > Non-authoritative answer: > Name: scs-fooc.yahoo.com > Addresses: 216.136.233.132, 66.163.173.203, 216.136.173.172, 216.136.173.179 > 216.136.175.226, 216.136.226.209, 216.136.226.210 > Aliases: scsb.yahoo.com, scs.yahoo.com > > > C:\>nslookup scsc.yahoo.com > Non-authoritative answer: > Name: scs-fooc.yahoo.com > Addresses: 216.136.175.226, 216.136.226.209, 216.136.226.210, 216.136.233.132 > 66.163.173.203, 216.136.173.172, 216.136.173.179 > Aliases: scsc.yahoo.com, scs.yahoo.com > > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
