id summary reporter owner description type status priority milestone component version resolution keywords cc irc_client os os_version 607 Jabber port list restriction Matthew Cengia "I think that the limits imposed on the ports that can be used for Jabber are unnecessary and can potentially be a hindrance. I for example connect to a private server at my workplace, which I have to port forward via SSH to my local system. These port restrictions mean that I need to forward to one of the listed ports (5222, 5223, 5220, 5221, 5224, 5225, 5226, 5227, 5228, 5229, 80, 443). As it is the system I use BitlBee on already has services on ports 5222, 80, and 443. I have commented out the section of code that checks for port validity (jabber.c:202-211), and everything seems to work fine. Is there any particular reason why this restriction is in place? If nothing else, I think that rather than just an ""Illegal port number"" error, the accepted ports should be listed so the user know what BitlBee considers to be ""legal""." defect closed normal BitlBee 1.2.6 duplicate Client-independent Linux