> -----Original Message-----
> From: Wayne R. Boyer [mailto:[log in to unmask]]
> 
> AOL Instant Messenger and some other similar creatures have 
> some sort of protocol for discovering who is 'online' and then exchanging 
> messages.

Generally, when a person logs on, the IM client contacts a server to indicate they are "on" the system; the server logs this in a database, and the client then "looks for" each of the "buddies" to see what their current state is (there may also be a "heartbeat" type function where the central server checks to see if the user is really "still there" or if perhaps the comm lines have been dropped...)

> spamers of this world have now discovered this protocol and 
> are making use of it to send out spam IM messages[...] From
> the junk that I have been getting it is clear that there is 
> some custom written code doing the automated messaging.
> 
> Thoughts...
> 
> 1) knowing the protocol, it would be fairly easy (?) to 
> create such a text based messaging utility for MPE

Yes, most of these protocols are documented, or at least discovered by, a group producing an "open source" version of a mega-client: jabber [this was mentioned in another response]  Actually, "jabber" has it's own protocol [which is XML encapsulated] however the jabber client is also capable of signing on to various other services thus allowing for AOL-to-MSN chatting...
 
> 2) there are nice legitimate business uses for IM type messaging.

Since an IM tends to be short, what is wrong with :TELL or :WARN[f]?  Sure, it is a bit more typing on the client side [you have to fully address the message recipient, you can't simply "point-n-click"] but it accomplishes the goal of (nearly) instantaneous transfer of short messages; complete with a facility for recipients to set an "I'm away and won't be listening" mode [QUIET]
 
> Anyone seen anything resembling specs for this protocol?

The problem with many of these protocols is that they tend to be closed/proprietary and viewed as an Intellectual-Property "asset", [though I don't really need to be telling YOU this :) ] so to "protect" their asset, the owners of the protocol make subtle changes from time to time.  Since AOL or MSN controls the distribution of the "client", they can easily send out a "changed" version that will support an upcoming protocol change (i.e., as a "fixpack" or whatever), wait a week or two to ensure everyone "gets" it, then drop in the new protocol.

Then in about three or four days, the folks at places like jabber will reverse engineer the protocol and fix/redistribute the client :)  Likewise, the spammers will operate on a similar timeframe... :(

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *