On Wed, Apr 05, 2000 at 08:15:24AM -0400, Bryan White wrote:
> > In what way are you "struggling"? Sure there may be plenty of emails in
> your queue,
> > but is it really hurting? Or do you just not like that idea of
> qmail-remote failing
> > and seeing the corresponding log entry? Remote delivery is very cheap with
> qmail so
> > you don't need to be too concerned unless the yahoo mail is consuming all
> of your
> > concurrencyremote. If it's not, then you can sleep soundly as it's no big
> deal.
>
> We run some rather large opt-in email 'ezines'. Throughput matters. The
> more remotes sitting waiting on yahoo the less there are to handle the rest.
> This morning I have 6 boxes each sitting pegged at 250 remotes. My total
> throughput is typically about 300,000 per hour. Yesterday morning it was
> 140,000 per hour. It is somewhat better this morning (about 180,000 per
> hour).
Well, that's more of a problem. The only *easy* solution is to force the
timeout values on the MX addresses in tcpto. I think that someone once posted
some perl or a program to do this.
Or, as I suggested earlier, put a bogus smtproutes entry in there that forces
qmail-remote to write a tcpto value on your behalf.
What both of these solutions mean though is that no attempts will be made to send
to yahoo.com
An alternative strategy is to create an instance of qmail that just deals with
yahoo.com
and have all the other systems smtproute to it.
Regards.
