Bitlbee

From ArchWiki
Revision as of 20:50, 3 February 2011 by Det (Talk | contribs) (Setup)

Jump to: navigation, search

Template:I18n links start Template:I18n entry Template:I18n entry Template:I18n links end

About

Bitlbee is a "console-based IRC to IM chatting gateway, including ICQ/MSN/Jabber". Basically, it allows the user to interact with popular chat networks (ICQ, MSN, Jabber, AIM, YIM) within their IRC client.

The users' buddies appear as normal IRC users in a channel and conversations use the private message facility of IRC.


Setup

First, download and install the package using pacman:

# pacman -S bitlbee

Bitlbee can now run as a daemon of its own! Open up Template:Filename to browse through the settings. Uncomment the Runmode line and change it to the following.

RunMode = ForkDaemon

There is no need to run the bitlbee daemon as root so we should uncomment the following line so it can run as the "bitlbee" user created when the package was installed.

User = bitlbee

Now run

/etc/rc.d/bitlbee start

to start the Bitlbee server. Of course, add bitlbee to your DAEMONS array in Template:Filename to start the server on boot. Note that just starting the server does not log you in to any of your messenger accounts! You must join a channel and issue commands.

You may also start bitlbee every time Arch Linux boots. To do so, just add the bitlbee entry in the file rc.conf as follows:

DAEMONS=(... alsa cups bitlbee ...)

(The three dots mean other daemons that run during bootup)

Configuration

You are now able to connect to this in an IRC client. To connect, just connect to localhost using your favorite IRC client.

Hopefully this will connect and you should immediately join a channel called '&bitlbee'. When you join this channel it will tell to type 'Help' if you're new... type 'Help' ;)

Read through the help offered by Bitlbee to get started. There are some great guides online too:

http://quark.humbug.org.au/publications/internet/bitlbee.pdf

http://princessleia.com/bitlbee.php

How to connect to Jabber using your Gmail account

In your control channel do the following:

account add jabber username@gmail.com mypasswd

After root responds with "Account successfully added" you can check your accounts with "account list".

<@user> account list 
<@root> 0. JABBER, username@gmail.com (connected) 
<@root> End of account list

Set the server value of your gmail account:

account 0 set server talk.google.com

After you have added the account, type "account on 0" and it should log in:

<@user> account 0 on
<@root> JABBER(username@gmail.com) - Logging in: Connecting 
<@root> JABBER(username@gmail.com) - Logging in: Connected 
<@root> JABBER(username@gmail.com) - Logging in: Requesting Authentication Method
<@root> JABBER(username@gmail.com) - Logging in: Authenticating 
<@root> JABBER(username@gmail.com) - Logged in

If you get errors like the following:

<@user> account 0 on 
<@root> JABBER(username@gmail.com) - Logging in: Connecting
<@root> JABBER(username@gmail.com) - Logging in: Connected
<@root> JABBER(username@gmail.com) - Logging in: Requesting Authentication Method
<@root> JABBER(username@gmail.com) - Logging in: Authenticating
<@root> JABBER(username@gmail.com) - Login error: Error 403: Unknown error
<@root> JABBER(username@gmail.com) - Signing off...

Switching the domain from "gmail.com" to "googlemail.com" may help. This seems to be the case for some European countries, especially Germany where Google doesn't own the trademark for the name Gmail [1].

The easiest way to change your account settings is to simply delete the account you created and add it again.

account 0 del
account add jabber username@googlemail.com mypasswd

If you are still unable to connect, try switching the port to 5222. For some reason some people must connect on 5223 while others have to connect on 5222. There appears to be no way to know which one to use other than trial and error.

See Also

Screen Irssi Bitlbee