We've had the same problem everyone else has with deliverying mail to Yahoo. We delviery significant volumes of mail daily. The result is a very full queue, and all the remote processes taken by retries/delivery attempts to Yahoo. I appreciate this problem has been under discussion but I've seen no solutions. We needed a fast and quite pragmatic solution. We have taken the approach to implement a general max remote concurrency per domain limit. This means that if at any time a new remote delivery process is required the intended recipient domain is checked against the currently 'in use' remotes. A simple count then determines whether there is a free remote for that domain. If the limit is hit then the post is delayed. This is controlled from qmail-send and behaves exactly as if the remote concurrency lomit had been hit. We have found it works very well and normal delivery has resumed. Yahoo still doesn't get mail but all other delvieries are not held up. The initial patch fixes the problem but could be improved (mainly in obtaining and storing the recip domain in the del struct, which I chose initially to leave well alone). Other approaches could include to have a separate remote domains file and check only those, but that is a reactive approach, and we prefer no domain to ever dominate our queue. Being fairly new to this forum, how are patches generally released (we have an internal patch of the normal form) ? I'm happy to release both an initial patch, which we have running live for about 5 days in a public service 24/7 environment, and the improved patch (in a day or two after testing). Regards, Paul Dale [EMAIL PROTECTED] www.intracus.com All views expressed are my own and do not represent those of Intracus Ltd.
