# HG changeset patch
# User Mark Doliner <mark@kingant.net>
# Date 1245780483 0
# Node ID 763247959e00f38abf193617ca21d51a1eee52d8
# Parent  8487bf2c306e489d797118b8c3c8551ddb663d0d
It's ok to always request this connection now.  It probably still doesn't
work for @example.com accounts, but it doesn't show an error anymore.  Maybe
we just stopped showing that error to users?

diff -r 8487bf2c306e -r 763247959e00 libpurple/protocols/oscar/oscar.c
--- a/libpurple/protocols/oscar/oscar.c	Tue Jun 23 18:03:48 2009 +0000
+++ b/libpurple/protocols/oscar/oscar.c	Tue Jun 23 18:08:03 2009 +0000
@@ -3913,20 +3913,9 @@
 			purple_account_get_bool(account, "web_aware", OSCAR_DEFAULT_WEB_AWARE));
 	}
 
+	aim_srv_requestnew(od, SNAC_FAMILY_ALERT);
 	aim_srv_requestnew(od, SNAC_FAMILY_CHATNAV);
 
-	/*
-	 * The "if" statement here is a pathetic attempt to not attempt to
-	 * connect to the alerts servce (aka email notification) if this
-	 * username does not support it.  I think mail notification
-	 * works for @mac.com accounts but does not work for the newer
-	 * @anythingelse.com accounts.  If that's true then this change
-	 * breaks mail notification for @mac.com accounts, but it gets rid
-	 * of an annoying error at signon for @anythingelse.com accounts.
-	 */
-	if (od->authinfo->email != NULL && strchr(username, '@') == NULL)
-		aim_srv_requestnew(od, SNAC_FAMILY_ALERT);
-
 	return 1;
 }