>Bastards,  I'm sure we will start seeing more and more of this kind of
>thing happening as the Corporations become greedier and greedier.
>Maybe its time to start supporting an ICQ client more.

Last I checked, AOL owned ICQ.
Jabber is an open protocol, and the most recent versions of internet_im.pm support Jabber, IIRC. 

While checking into this, I noticed a slight issue with internet_im.pm.

When the bot "AOL System Msg" sends anything to the MH-hosted AIM Bot, MH will respond with the "Unauthorized access" message.

This results in MH and the AOL bot going back and forth yelling at each other.
The AOL bot will send a message if an account is signed in two or more times, or for advertisements and announcements (ie: the announcement of the recently added shopping bot and movie bot).
I'm not sure if other networks have this issue, as I only use the AIM one with MisterHouse.

My proposed fix (working with the internet_im.pm that comes with 2.100):
at or around line 149 you will see this:

print "IM: RUN a=$authority,$im_data{password_allow}{$from} from=$from text=$text\n" if $main::Debug{im};
return if $text =~ /^i\'m away/i;
return if $text =~ /^Sorry, I ran out for a bit/i;
return if $text =~ /^I am currently away from the computer/i;

adding the following lines here fixes the problem:
# Fix for AOL: bot to bot infinite loop - stops replies to AOL's bot.
return if $from =~ /AOL System Msg/i;

Don't know if that is the 'proper' way to do it, but it works on my copy.  Basically, just prevent the script from replying to the bot, and you skip the whole infinite loop thing.

I suspect this oversight might have something to do with your ban, Tim.  If your copy of MH got a message from AOL System Msg (during a restart, or whatever), and went into this infinite loop back and forth, it may have gotten the attention of AOL and your account shut down to stop the loop.  Probably happened automatically with no human intervention. 
You can check this in your logs (by default in your mh/data/logs directory).  Internet_im.pm puts stuff in both the print log (print.log) and a file called net_im.$date.log