Opened 10 years ago

Closed 3 years ago

#10023 closed defect (out of date)

Adium fails to login properly on MSN because of FQY error 241.

Reported by: Dimmuxx Owned by: khc
Milestone: Component: MSN
Version: 2.6.1 Keywords: msn fqy 241 login
Cc: Hawk__

Description

When an adium user have a strange contact on their contact list they are unable to login.

21:44:32: (Libpurple: msn) FQY error 241
21:44:32: (Libpurple: msn) FQY response says longsillyandnotvalidpassportaddress@somewhere.net is from network 0
21:44:32: (Libpurple: msn) Ignoring user longsillyandnotvalidpassportaddress@somewhere.net about which server knows nothing.

There are plenty of tickets about this issue on Adium's trac and in the support forum, #a12391 includes some logs. I talked to QuLogic about this issue before and we concluded that it would probably be fixed by the fix for #9505 but it seems it isn't since it still happens in adium 1.4b9 which uses 2.6.2mtn.

Change History (12)

comment:1 Changed 10 years ago by qulogic@…

(In 5d9456311f879116a0aa9a4e39d9262030f2f79e):
This seems to not work every once in a while, so put in some code under the verbose flag.

Refs #10023.

comment:2 Changed 10 years ago by QuLogic

  • Status changed from new to pending

Can you get a log on 5d9456311f879116a0aa9a4e39d9262030f2f79e with the PURPLE_VERBOSE_DEBUG environment variable set?

comment:3 Changed 10 years ago by trac-robot

  • Status changed from pending to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

comment:4 Changed 10 years ago by QuLogic

Ticket #10241 has been marked as a duplicate of this ticket.

comment:5 Changed 10 years ago by QuLogic

  • Status changed from closed to new

comment:6 Changed 9 years ago by Hawk__

The problem also exists in Pidgin 2.6.2 (I think it is in libpurple or the MSN plugin), after an invalid buddy was added to the list.

Removing the buddy using another software (Windows Live Messenger, aMSN) doesn't resolve the problem. In fact, it seems that the buddy is added to the blacklist on the server and when libpurple connects, it sees it and an error (FQY error 241) is sent back from MSN server when libpurple tries to get informations about the invalid buddy.

Using Pidgin 2.5.2, I managed to connect successfully (an error is raised at every connection, but everything seems to work ok), and could get to the filters window. Trying to remove any buddy from the blacklist gives this result in the debug window :

(15:08:47) msn: Passport: d~~~~@hotmail.com, type: 1
(15:08:47) msn: Didn't find existing domain node, adding one.
(15:08:47) msn: list_op: 4
(15:08:47) msn: Send RML with payload:
<ml><d n='hotmail.com'><c n='d~~~~' l='4' t='1'/></d></ml>
(15:08:47) msn: C: NS 000: RML 18 58
(15:08:47) msn: Deleting contact d~~~~@hotmail.com from Block list
(15:08:47) soap: POST //abservice/SharingService.asmx HTTP/1.1

SOAPAction: http://www.msn.com/webservices/AddressBook/DeleteMember

Content-Type:text/xml; charset=utf-8

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Accept: */*

Host: contacts.msn.com

Content-Length: 1780

Connection: Keep-Alive

Cache-Control: no-cache



<soap:Envelope xmlns:soap='http://schemas.xmlsoap.org/soap/envelope/' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:soapenc='http://schemas.xmlsoap.org/soap/encoding/'><soap:Header><ABApplicationHeader xmlns='http://www.msn.com/webservices/AddressBook'><ApplicationId>CFE80F9D-180F-4399-82AB-413F33A1FA11</ApplicationId><IsMigration>false</IsMigration><PartnerScenario>BlockUnblock</PartnerScenario></ABApplicationHeader><ABAuthHeader xmlns='http://www.msn.com/webservices/AddressBook'><ManagedGroupRequest>false</ManagedGroupRequest><TicketToken>t=EwDgAcBdAAAURnMnP0xNtZi9ugdf902M4Br/7wKAALtpfepxfnbiJfwc1Q+mD8yfSi5AUPgpawAsIVEY5SYRMGRBTxshSJasmjM/va4OUBCvNqHrNkh0Tu+A4SEGqEynQ5eTsfT5xJx42svKpcUHFb6BPLAdNa6cCCOQBfFlaeDAcawygewC9jAnpdAKA+qPd3C2R6liA1h+d3RVqXpDA2YAAAjpiZ3LoG4vWTABWHJPAJeSeTNek6Gkypa3OG0N6aa2ouJxGm/3orwpD1aO5ihyOukGAwOO74UfLug1x5CT7aAvXR/KJ6DAKbdfGweBdSQGB0tvFIBEMZjN7MnOb1pemQ/t471kCgyK1gdEWYxfkdjMW9UvKtyUCkCcsazvZUGiYSim3G4SNj5kb33gnIodGmTpYAMr41rwE/hvw3HItXkuO9Rj+S4pXKnu5096PtPEgUFTBrjcfood7UpdVx0T3lhae+8WeYgt3TZqkY/zUU22sj0E4Su+JgBV9EBMwo0tuMtV3p/aSZ4K/Pr2unkOLWcBdT/A19I9PCEjyn8d/R+tpfcFg5L2PQyFXoh3wnDIJ6rAgJ4ViUqpCcks+nJWEsCVnZ0h0BF09dm4Wqd7lPXMG3MZ/nR2nC+m10kB&amp;p=</TicketToken></ABAuthHeader></soap:Header><soap:Body><DeleteMember xmlns='http://www.msn.com/webservices/AddressBook'><serviceHandle><Id>0</Id><Type>Messenger</Type><ForeignId/></serviceHandle><memberships><Membership><MemberRole>Block</MemberRole><Members><Member xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:type='PassportMember'><Type>Passport</Type><State>Accepted</State><PassportName>d~~~~@hotmail.com</PassportName></Member></Members></Membership></memberships></DeleteMember></soap:Body></soap:Envelope>
(15:08:48) msn: S: NS 000: 241 18 47
(15:08:48) msn: error 241: Erreur MSN : Code d'erreur inconnu 241

(15:08:48) soap: read 1315 bytes
(15:08:48) soap: current HTTP/1.1 500 Internal Server Error

Date: Sun, 27 Sep 2009 13:05:50 GMT

Server: Microsoft-IIS/6.0

P3P:CP="BUS CUR CONo FIN IVDo ONL OUR PHY SAMo TELo"

X-Powered-By: ASP.NET

X-MSNSERVER: BY2ABCHWB217

X-AspNet-Version: 2.0.50727

Cache-Control: private

Content-Type: text/xml; charset=utf-8

Content-Length: 996



<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><soap:Fault><faultcode>soap:Client</faultcode><faultstring>The Passport user specified is invalid SignInName: d~~~~@hotmail.com</faultstring><faultactor>http://www.msn.com/webservices/AddressBook/DeleteMember</faultactor><detail><errorcode xmlns="http://www.msn.com/webservices/AddressBook">InvalidPassportUser</errorcode><errorstring xmlns="http://www.msn.com/webservices/AddressBook">The Passport user specified is invalid SignInName: d~~~~@hotmail.com</errorstring><machineName xmlns="http://www.msn.com/webservices/AddressBook">BY2ABCHWB217</machineName><additionalDetails><originalExceptionErrorMessage>The Passport user specified is invalid SignInName: d~~~~@hotmail.com</originalExceptionErrorMessage></additionalDetails></detail></soap:Fault></soap:Body></soap:Envelope>
(15:08:48) soap: ignoring malformed line: P3P:CP="BUS CUR CONo FIN IVDo ONL OUR PHY SAMo TELo"
(15:08:48) msn: Operation {} Failed, SOAP Fault was: <soap:Fault><faultcode>soap:Client</faultcode><faultstring>The Passport user specified is invalid SignInName: d~~~~@hotmail.com</faultstring><faultactor>http://www.msn.com/webservices/AddressBook/DeleteMember</faultactor><detail><errorcode xmlns='http://www.msn.com/webservices/AddressBook'>InvalidPassportUser</errorcode><errorstring xmlns='http://www.msn.com/webservices/AddressBook'>The Passport user specified is invalid SignInName: d~~~~@hotmail.com</errorstring><machineName xmlns='http://www.msn.com/webservices/AddressBook'>BY2ABCHWB217</machineName><additionalDetails><originalExceptionErrorMessage>The Passport user specified is invalid SignInName: d~~~~@hotmail.com</originalExceptionErrorMessage></additionalDetails></detail></soap:Fault>

Hope this may help resolve the problem, as recent versions of Pidgin or Adium are no more useable when an account has this problem.

Is there any mean of totally emptying (or resetting) the blacklist on msn servers ? That could solve the problem for concerned accounts I think ...

comment:7 Changed 9 years ago by Hawk__

I made some more testing, and I found that Pidgin 2.5.5 connects just as 2.5.2 but without raising any error (no window telling an error occured). Connecting won't finish in any newer version of Pidgin (from 2.5.6 an following).

When connecting, I found this in the debug window :

(15:32:19) msn: error 241: Erreur MSN : Code d'erreur inconnu 241

(15:32:19) msn: S: NS 000: <ml><d n="hotmail.com"><c n="d~~~~" /></d></ml>PRP 11 MFN Dominique
(15:32:19) msn: Unhandled command '<ml><d'
(15:32:19) msn: S: NS 000: ADL 9 OK

Trying to remove the invalid buddy from the blocked buddy list still doesn't work and disconnects Pidgin from MSN.

comment:8 Changed 9 years ago by Dimmuxx

Hawk: Run 2.6.2 with the PURPLE_VERBOSE_DEBUG environment variable set and it might be enough to find out what's causing this.

comment:10 Changed 9 years ago by qulogic@…

(In 6fd13fcd41c95794bed286994ba8dc779da0aa01):
Add a timeout which forces the login process to complete. This won't fix the underlying problem of a failed FQY, but at least it will complete the connection and show people online.

Refs #10023. Refs #12210.

comment:11 Changed 9 years ago by rekkanoryo@…

(In 998766ceb74c46b4d1e791c5152c38daa51f49f7):
* Plucked 6fd13fcd41c95794bed286994ba8dc779da0aa01 (qulogic@…): Add a timeout which forces the login process to complete. This won't fix the underlying problem of a failed FQY, but at least it will complete the connection and show people online.

Refs #10023. Refs #12210.

* Plucked bf254d85fb121a0a699992e1f391b65d0e37b05d (qulogic@…): Clear the password on an MSN account if saving is disabled and the password was wrong. This should be in line with what other prpls do.

Fixes #12290.

Plucks requested by Dimmuxx and rob-to86.

comment:12 Changed 3 years ago by dx

  • Resolution set to out of date
  • Status changed from new to closed

The FQY command doesn't exist in newer protocol versions, and older ones don't work anymore. Closing.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!