Protocols

As well as creating the required redirection firewall rules, IMSpector also needs to be told to handle each protocol you wish it to process:

icq_protocol=on
irc_protocol=on
msn_protocol=on
yahoo_protocol=on
gg_protocol=on
jabber_protocol=on
https_protocol=on

Note that the https_protocol option is only required under the following conditions:

  • You are using IMSpector’s built in HTTP proxy port.
  • You are using MSN.

This is because MSN utilises HTTPS on port 443 in its authentication stage. IMSpector does not imspect this traffic, but it does need to be able to pass it between the client and the server.

By default, IMSpector will not log “typing events”, because they are not usually interesting. None the less, it is possible to log them if you desire:

log_typing_events=on

IRC does not have the concept of typing events and thus IMSpector cannot log them.

IMSpector is able to hide the actual message texts from the logs. This is useful if you want to keep an eye on IM use on the network, but not actually record the messages exchanged.

hide_eventdata=on

This is infact a global option and is applied to all users, on all protocols, and regardless of the actual logging mechanism used. The message “eventdata” (be it the message text, or name of a file that is transfered) will be substituted with “*HIDDEN*”.

  1. kujo2050
    April 3rd, 2010 at 03:36 | #1

    Any thoughts for including the Sametime / Meanwhile Protocol Plugin?

  1. No trackbacks yet.
You must be logged in to post a comment.