On Mon, Oct 02, 2000 at 11:18:22AM +0100, Paul Dale wrote:
> 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.

Perhaps that's what Yahoo should be doing? Be that as it may...

> We have taken the approach to implement
...
> 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.

...there are ways to do this which don't require any patches at all.

Install a second instance of qmail which is only used to
deal with recalcitrant domains such as yahoo.com. Set the
concurrencyremote down to some suitable number on this
instance and then let it handle the deliveries. Bind this instance
to something like localhost:26 for smtp.

On your main instance of qmail place an entry in smtproutes for
yahoo.com, pointing to the second instance. Something like
yahoo.com:localhost:26

If your patch doesn't help deliver to yahoo.com, then this
solution wont help either. But it will free up the concurrencyremote
on your main qmail instance so that it can get on with delivering
to domains that have sufficient resources to handle their mail
volumes.

> Being fairly new to this forum, how
> are patches generally released (we have
> an internal patch of the normal form) ?

Sending the URL and description to the webmaster at qmail.org usually
does the trick. There is no formal location for all qmail patches and
no formal process of integrating them into qmail.


Regards.

Reply via email to