Exodus defaults wrongly (for me) on unspecified message types

Damon Register <[email protected]> Tue, 24 Feb 2004 16:45:29 -0500

Newsgroups	gmane.network.jabber.exodus.user
Message-ID	<[email protected]>

I have a small problem with Exodus but I don't know if it is just a
matter of not knowing how to tamper with Exodus or if maybe Exodus
needs a new feature.  The problem is when Exodus receives a message
from someone using JabberApplet from
http://jabberapplet.jabberstudio.org .  Exodus treats them as a message
instead of a chat.  I used the debug window of Exodus to see what was
the difference between the messages and I got the following:

from JabberApplet

RECV: <message to='[email protected]' 
from='[email protected]/JabberApplet-1518631214'><body>debug 
test</body></message>

from Exodus

RECV: <message id='jcl_7' to='[email protected]' type='chat' 
from='[email protected]/Exodus'><thread>585c6394324eaf006246d0de14ee47bc6f0eb331</thread><body>test</body><x 
xmlns='jabber:x:event'><composing/></x></message>

It seems that the message from JabberApplet is missing type='chat'.
Is it currently possible for Exodus to be configured to handle an
unspecified message type as a chat?  If not, does this seem like a
good idea for a new feature?

Damon Register