From ArchWiki
Revision as of 16:01, 22 July 2011 by Karol (talk | contribs) (Setup: -)
Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی


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.


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. 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=(... bitlbee ...)

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


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:

How to connect to Jabber using your Gmail account

In your control channel, do the following:

account add jabber mypasswd

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

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

Set the server value of your gmail account:

account 0 set server

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

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

If you get errors like the following:

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

Switching the domain from "" to "" 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 mypasswd

or just use the `set` switch for the `account` command

account list   # find the id for your gtalk account, in this case I'll use '0'
account 0 set  # list all the possible settings for this account
account 0 set username        # change your username
account 0 set password somethingverysecret  # change your passphrase

Gmail uses ssl/tls (ie the url is so you can enable it for some extra security. You'll need to change the connection port too. To do that, you'll need to be disconnected from that account.

<@user> account 0 off
<@root> jabber - Signing off..
<@user> account 0 set ssl true
<@root> ssl = `true'
<@user> account 0 set port 5223
<@root> port = `5223'

Even if you dont do that the stream should change automatically

<@user> account 0 on
<@root> jabber - Logging in: Connecting
<@root> jabber - Logging in: Connected to server, logging in
<@root> jabber - Logging in: Converting stream to TLS

See Also

Screen Irssi Bitlbee