Hello! Sorry that it took so long, but I got sidetracked by other projects and haven't had the time to set up a test machine until now.
* Gilles Chehade on Fri, Aug 05, 2011 at 04:50:59PM +0200: > > | startup [debug mode] > > | [...] > > | smtp: will accept at most 246 clients > > | [...] > > | mta: getting datafd > > | mta: connect IPv6:2001:1418:153:ffff:: > > | mta: new status for me.mys...@example.com: 110 connect error: Host is down > > | mta: connect IPv6:2001:1418:153:ffff:: > > | mta: new status for me.mys...@example.com: 110 connect error: Host is down > > | mta: connect 94.95.177.106 > > | mta: entering smtp phase > > | [...] > > Instead of using the full IPv6 address, it only uses the subnet prefix > > of the smarthost. This of course fails horribly, leading to a two-minute > > timeout, and then finally the mail goes through using IPv4 only. > Did this work before you updated ? The regression must have crept in between the 4.8 and 4.9 releases. Both 4.7 and 4.8 do just fine, and with 4.9 I get the behaviour shown above. I'll try with a recent snapshot too, once the download is done. s//un -- squeak!
