Can't connect to top tracker;won't connect to other trackers

[Pigeon]

My ISP filters very, very heavily. I have a proxy set up to connect to trackers. I can't connect to UDP trackers at all, and many http trackers will time out. (occasionally other problems - torrent not authorized etc) When this happens, deluge will attempt to re-connect to the same tracker that didn't work.

Connecting to a tracker is a painful, manual process of going into the 'edit trackers' dialog, deleting all the udp trackers, and finding a working tracker with trial and error by moving a potentially working tracker to the top of the list and deleting it if it doesn't work.

Is this a bug? If not, how can I configure deluge to automatically move on to a different tracker if the top tier tracker is unavailable for any reason?

I run Gentoo ~x86. Deluge is version 1.3.2, rb_libtorrent is 0.15.6, python is 2.7.1-r1. Connecting to peers works fine if they use a non-standard port and encryption is enabled. I use the client/server mode; deluged running in the background, and connect to it with deluge-console/deluge-gtk.

[Cas]

The trackers are decided upon by libtorrent so you would need to ask on IRC chan or create bug ticket

http://www.rasterbar.com/products/libto ... l#trackers