Add a New Comment (Rich Markup)
Comment Type & Canned Response: None No canned response available
Actually, I just tested this some more. It seems that the order in which the servers autoconnect is the cause. Unless Bitlbee is the last in order to autoconnect (not connect) - it will not identify correctly.
Bitlbee.autoconnect = on Bitlbee.command = "/msg &bitlbee identify password"
Bitlbee will identify if it is the only server set to autoconnect. If another server is set to autoconnect too, Bitlbee will not identify correctly. The Bitlbee.command is not sent.
If Bitlbee is not set to autoconnect, and you connect via /connect Bitlbee, it will identify correctly.
(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)
Attach Files: Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Only logged-in users can vote.
Please enter the title of George Orwell's famous dystopian book (it's a date):
Follow 6 latest changes.
Copyright © 2022 Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team. Source Code
Powered by Savane 3.9