[jdev] about spim techniques

Roberto Della Pasqua roberto at dellapasqua.com
Sat Aug 27 03:21:55 CDT 2005


Hi kind developers,

I like ask a question:

1) user1 at origindomain.com is not listed in the buddylist of
user2 at targetdomain.com
2) user1 at origindomain.com send a message to user2 at targetdomain.com
3) what is the default behavior of the server XMPP of targetdomain.com?
4) it block the message because not found in buddylist?
5) it dispatch a request authorization to user2 at targetdomain.com?

These days I see much traffic about anti-spim techniques.

In my humble opinion jabber need be open as the SMTP, so to be able to
become a full standard without limitations.

Let me tell you that the spam problem of the SMTP is due to the fact that
everybody can send emails without authenticate in any server, just found a
relay server and use it.

Jabber automatically erase the big problem of casual spam, because need an
authenticated user, so will be easy from the server that originate the spam
discover the IP number, dsl location, phone number of the spammer.

I guess about a company that like contact another company knowing only the
JabberID, and easy as sending an email the company can IM immediately the
target without complain about authorization, etc...

What are your opinions? 
What is the default behavior of XMPP now sending IM message to a not-listed
in buddy-list?
Is it on the client side do filter the message as "NEW USER" or the server
filter the message before reach the client? 
I'm scared about adopt techniques that "close" the protocol behavior, so to
advantage big service companies that have into one domain millions of users
and will damage all small, medium service providers, that in my hope will
adopt everyone a XMPP server to extend IM service to their customer (without
change email, user at somedomain become also XMPP). Will be a better overall
open market for everyone, as SMTP permit now.

Thank you for any support.

Roberto Della Pasqua





More information about the JDev mailing list