comparison libpurple/protocols/oscar/clientlogin.c @ 29386:e1dd357fc494

Add back Paul's error message from revision 219b3128f3d96b126a9ed9aff2d2f3277e69dbd4 (disapproved in revision e2fb4cc366c55b86f89304bddac780a92ff73394) with a slightly improved error message. Thanks for adding this in the first place, Paul! Sorry it took me months to re-instate it after I complained! Hopefully AOL won't start asking users to fill out CAPTCHAs in order to log in, because that would be messy (both our implementation and the user experience).
author Mark Doliner <mark@kingant.net>
date Sun, 07 Feb 2010 09:30:49 +0000
parents c833ae72599b
children d932f43cde86
comparison
equal deleted inserted replaced
29385:acf7f7637669 29386:e1dd357fc494
411 411
412 if (status_code == 330 && status_detail_code == 3011) { 412 if (status_code == 330 && status_detail_code == 3011) {
413 purple_connection_error_reason(gc, 413 purple_connection_error_reason(gc,
414 PURPLE_CONNECTION_ERROR_AUTHENTICATION_FAILED, 414 PURPLE_CONNECTION_ERROR_AUTHENTICATION_FAILED,
415 _("Incorrect password")); 415 _("Incorrect password"));
416 } else if (status_code == 330 && status_detail_code == 3015) {
417 purple_connection_error_reason(gc,
418 PURPLE_CONNECTION_ERROR_AUTHENTICATION_FAILED,
419 _("Server requested that you fill out a CAPTCHA in order to "
420 "sign in, but this client does not currently support CAPTCHAs."));
416 } else if (status_code == 401 && status_detail_code == 3019) { 421 } else if (status_code == 401 && status_detail_code == 3019) {
417 purple_connection_error_reason(gc, 422 purple_connection_error_reason(gc,
418 PURPLE_CONNECTION_ERROR_OTHER_ERROR, 423 PURPLE_CONNECTION_ERROR_OTHER_ERROR,
419 _("AOL does not allow your screen name to authenticate here")); 424 _("AOL does not allow your screen name to authenticate here"));
420 } else { 425 } else {