#433 closed defect (wontfix)

Bitlbee no longer permits auto-login with ChatZilla

Reported by: Chascon Owned by:
Priority: normal Milestone:
Component: BitlBee Version: 1.2.1
Keywords: Cc:
IRC client+version: Client-independent Operating System: Public server
OS version/distro:


ChatZilla's Auto-Perform used to log me in automatically with the identify command. It no longer works and apparently because Bitlbee does not follow standard IRC protocol.

I filed a bug with ChatZilla's bugzilla and one dev had this to say, "I spoke with Rob Marshall about this one, basically Bitlbee doesnt sent a 251 message after the 005 - which is what we use to decide that autoperform is ready.".

As Bitlbee is supposed to be compliant with IRC, that's why it's IRC client agnostic, this should be changed.

The bug is reported at <>.

Attachments (0)

Change History (4)

comment:1 Changed at 2008-07-08T18:52:53Z by mauritsd@…

Could you quote the part of the RFC saying you have to send a 251 after a 005? I can't find anything about it...

Also, why doesn't Chatzilla just trigger its autoperform list on a 005?

comment:2 Changed at 2008-07-08T18:59:51Z by mauritsd@…

Sorry, to clarify my reply: there are several documents specifying the IRC standard in detail. None of them seem to specify that you have to send a 251 (RPL_LUSERCLIENT) after a 004 (RPL_MYINFO). Also, after double-checking, a 005 (RPL_BOUNCE) is sent to indicate that a different server should be connected to, so I guess it's ChatZilla which isn't implementing the standard properly. The only thing I could find about RPL_LUSERCLIENT was this: "In processing an LUSERS message, the server sends a set of replies from RPL_LUSERCLIENT, RPL_LUSEROP, RPL_USERUNKNOWN, RPL_LUSERCHANNELS and RPL_LUSERME. When replying, a server MUST send back RPL_LUSERCLIENT and RPL_LUSERME. The other replies are only sent back if a non-zero count is found for them."

comment:3 Changed at 2008-07-08T19:51:55Z by wilmer

Actually these days all IRC implementations use 005 to announce/detect features supported by the IRCd. It's a somewhat documented new standard. Not sure if any client still interprets the old-style 005. Still, it could've been nice to use 006 or whatever was still available instead.

comment:4 Changed at 2008-12-13T12:20:08Z by wilmer

Resolution: wontfix
Status: newclosed

BitlBee has nothing useful to say in 251 responses, so I don't see why it should be sent. I don't want to have to deal with all the 392175827 different ways in which various IRC clients decide to trigger their auto-identification.

Also, you can auto-identify by sending your identify password using the IRC PASS command (at connect time).

Modify Ticket

as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.