Below is a detailed list of every error code ever discovered. Some of the commands have never before been encountered, but exist nonetheless. Each error code has details on every way I have seen them used, but it is quite possible that there are missing situations.
200201FLN would be an example. >>> CHG 19 FLN 0\r\n <<< 201 19\r\nADD an invalid email address. >>> ADD 20 FL a@b a@b\r\n <<< 201 20\r\n205ADD a nonexistent, but valid, account name. >>> ADD 21 AL non_existent_account@passport.com non_existent_account@passport.com\r\n <<< 205 21\r\n206207USR after already logging in, this error will be sent in response. >>> USR 20 TWN I example@passport.com\r\n <<< 207 20\r\n >>> USR 21 TWN S 6b05a0f5b1aa0959e128cfdd513ccf5c\r\n <<< 207 21\r\n208CAL which specifies an invalid account name. >>> CAL 2 @@a\r\n <<< 208 2\r\n209REA when there is a blocked word/phrase in the new nickname or when the Passport has not yet been confirmed. >>> REA 18 principal@passport.com look%20msn\r\n <<< 209 18\r\n210ADD command if the FL is already full. The principal will not be added. Currently (as of March 23, 2003), the limit is 150 principals, as doubled from a previous 75. >>> ADD 23 FL principal@passport.com principal@passport.com 0\r\n <<< 210 23\r\n215ADD a principal to a list, but the principal is already in that list. >>> ADD 26 AL principal@passport.com principal@passport.com\r\n <<< ADD 26 AL 824 principal@passport.com principal@passport.com\r\n >>> ADD 27 AL principal@passport.com principal@passport.com\r\n <<< 215 27\r\nADD a principal to your FL in a group that the principal is already in. >>> ADD 28 FL principal@passport.com principal@passport.com 2\r\n <<< ADD 28 825 FL principal@passport.com principal@passport.com 2\r\n >>> ADD 29 FL principal@passport.com principal@passport.com 2\r\n <<< 215 29\r\nCAL) a principal into a switchboard session that has already been invited and/or is already present. >>> CAL 5 example@passport.com\r\n <<< CAL 5 RINGING 286195\r\n >>> CAL 6 example@passport.com\r\n <<< 215 6\r\n216REMs that try to remove principals that are not in the list. Also sent if you try to remove nonexistent or invalid account names because, naturally, they couldn't be in your list. >>> REM 14 FL principal_not_in_list@msn.com\r\n <<< 216 14\r\nCALs) to principals that either have you in their BL or have their BLP settings so that you are automatically in their BL. This is only sent when the principal is on-line, but you're not allowed to know their on-line status. >>> CAL 2 example@passport.com\r\n <<< 216 2\r\nREAs that try to rename principals that are not in any of your lists. >>> REA 48 random_principal@randomdomain.com nickname\r\n <<< 216 48\r\n217CALs) to principals that are currently either offline or appearing offline. This error will also be sent in reply to invitations to nonexistent account names. >>> CAL 2 myname@msn.com\r\n <<< 217 2\r\n >>> CAL 3 nonexistent@passport.com\r\n <<< 217 3\r\n218GTC or a BLP if it tries to change the mode to the mode it is already in. In other words, if the GTC value is already set to A, and the client sends the GTC command setting it to A again, it will receive this error. >>> GTC 15 A\r\n <<< GTC 15 150 A\r\n >>> GTC 16 A\r\n <<< 218 16\r\n >>> BLP 17 BL\r\n <<< BLP 17 151 BL\r\n >>> BLP 18 BL\r\n <<< 218 18\r\n219ADD that causes the same principal to be in the BL and the AL at the same time. Obviously, that cannot be possible, and the principal will not be added. >>> ADD 15 AL example@passport.com example@passport.com\r\n <<< ADD 15 AL 108 example@passport.com Mike\r\n >>> ADD 16 BL example@passport.com example@passport.com\r\n <<< 219 16\r\n223ADG) so that you have more than 30 groups (the maximum). The group with the ID of zero counts toward the limit. >>> ADG 38 thirtyfirst%20group 0\r\n <<< 223 38\r\n224ADD a principal to your FL with a nonexistent group ID. Also sent in reply to REMs to nonexistent groups. Also sent in reply if you try to remove (RMG) or rename (REG) a nonexistent group. >>> RMG 24 15\r\n <<< RMG 24 12065 15\r\n >>> ADD 25 FL example@passport.com example@passport.com 15\r\n <<< 224 25\r\n >>> REM 26 FL example@passport.com 15\r\n <<< 224 26\r\n >>> RMG 27 15\r\n <<< 224 27\r\n >>> REG 28 15 New%20Name 0\r\n <<< 224 28\r\n225REM) a principal from an existent group that they are not currently in. >>> REM 27 FL example@passport.com 3\r\n <<< 224 27\r\n229ADG) with more than 61 bytes in the name. >>> ADG 50 this%20group's%20name%20is%20sixty%20two%20bytes%20in%20length 0\r\n <<< 229 50\r\n230RMG) the group with the ID of zero. >>> RMG 28 0\r\n <<< 230 28\r\n231280281300302500 >>> USR 28 TWN S 1938acd78b5524ce56a0ab6a01f3239\r\n <<< 500 28\r\n501502 >>> FND 3 fname=Bill lname=Gates city=* state=* country=US\r\n <<< 502 3\r\n510520540QRY that is invalid. The server will close the connection after sending the error. <<< CHL 0 15570131571988941333\r\n >>> QRY 10 msmsgs@msnmsgr.com 32\r\n
4f2f5a91b72102cd28355e9fc9000d6e <<< 540 10\r\n600601USR to the NS if the server is somehow "unavailable". >>> USR 10 TWN I example@passport.com\r\n <<< 601 10\r\n602603604605707710CVR if you send an invalid LCID. >>> CVR 1 0x0809 winnt 5.1 i386 MSNMSGR 6.0.0602 MSMSGS example@passport.com\r\n <<< 710 1\r\n711712713>>> CAL 5 blocking_you@passport.com\r\n<<< 216 5\r\n>>> CAL 5 blocking_you@passport.com\r\n<<< 216 5\r\n>>> CAL 5 blocking_you@passport.com\r\n<<< 216 5\r\n>>> CAL 5 blocking_you@passport.com\r\n<<< 216 5\r\n>>> CAL 5 blocking_you@passport.com\r\n<<< 216 5\r\n>>> CAL 5 blocking_you@passport.com\r\n<<< 713 5\r\n
714715PRP setting an invalid phone type of three or less characters. >>> PRP 30 PHV 555-0690\r\n <<< 715 30\r\nREA) on an unverified Passport account. >>> REA 31 me@passport.com newname\r\n <<< 715 31\r\n717731 >>> CVR 2 foo\r\n <<< 731 2\r\n <o> Server Closes Connection\r\n800REA) too rapidly, this error message will be sent in response to the commands that the server rejects. This does not affect renaming other principals. >>> REA 100 me@passport.com NAME\r\n <<< REA 100 2000 me@passport.com NAME\r\n >>> REA 101 me@passport.com NAME\r\n <<< REA 101 2001 me@passport.com NAME\r\n >>> REA 102 me@passport.com NAME\r\n <<< REA 102 2002 me@passport.com NAME\r\n >>> REA 103 me@passport.com NAME\r\n <<< REA 103 2003 me@passport.com NAME\r\n >>> REA 104 me@passport.com NAME\r\n <<< 800 104\r\nCHG) too rapidly. >>> CHG 105 NLN 0\r\n <<< CHG 105 NLN 0\r\n >>> CHG 106 HDN 0\r\n <<< CHG 106 HDN 0\r\n >>> CHG 107 NLN 0\r\n <<< CHG 107 NLN 0\r\n >>> CHG 108 HDN 0\r\n <<< CHG 108 HDN 0\r\n >>> CHG 109 NLN 0\r\n <<< 800 109\r\n910 >>> USR 28 TWN S t=53*1hAu8ADuD3TEwdXoOMi08sD . . . \r\n <<< 910 28\r\n911USR command to the DS. Also sent if the account name is invalid. >>> USR 3 TWN S example@passport.com\r\n <<< 911 3\r\n >>> USR 4 TWN I passport.com\r\n <<< 911 4\r\nTWN value sent in the second USR command to the NS. Also sent if the account name is invalid or nonexistent. >>> USR 6 TWN S t=some_invalid_value\r\n <<< 911 6\r\nUSR or ANS. >>> USR 1 myname_123@hotmail.com 486979.1047702516.105\r\n <<< 911 1\r\n >>> ANS 1 myname_123@hotmail.com 849102291.520491932 11752098\r\n <<< 911 1\r\n912913HDN status which the principal is currently in. The only known command that is prohibited when offline is XFR >>> XFR 13 SB\r\n <<< 913 13\r\n914915916917918919920921 >>> USR 28 TWN S t=53*1hAu8ADuD3TEwdXoOMi08sD . . . \r\n <<< 921 28\r\n922923USR to the NS if client is logging in with a Kids Passport without parental consent to chat online. >>> USR 29 TWN S t=53*1hAu8ADuD3TEwdXoOMi08sD . . . \r\n <<< 923 29\r\n924928USR to the NS if your ticket is invalid. Mostly seen if you don't handle redirections properly with the login server connection and use an @msn or @hotmail account
>>> USR 29 TWN S my_invalid_passport\r\n <<< 928 29\r\n