In-Reply-To: <20100829050214.GI19067@daedalus.andrew.net.au> X-RT-Interface: Web Content-Disposition: inline References: <20100812100631.3160.7839.reportbug@xo15-sascha.sascha.silbe.org> <20100829050214.GI19067@daedalus.andrew.net.au> Message-ID: Content-Transfer-Encoding: binary X-RT-Original-Encoding: utf-8 X-Mailer: MIME-tools 5.508 (Entity 5.508) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" RT-Send-CC: Content-Length: 494 Hello Andrew: We had slated to address this issue in our upcoming 4.4.0 release under a another ticket, rt16171, which complained of the same problem. Apparently, we lost track of the fact that this issue was solved under rt19660 by adding a parameter, intitial-delay