OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Subject: Re: site destiination queue overflow
From: Jeff Schneiter (jeffsmarketfirst.com)
Date: Mon Oct 02 2000 - 17:55:56 CDT

I am having a difficult time understanding your answer.

What is the "It" that is "preventing YAHOO from blocking all
your other mail delivery".

We tend to have three or four day burts of 4 million messages
going out, many of them to yahoo, getting the same problems as
Drew (but including dropped connections when sending DATA).

How does setting qmgr_site_hog_factor = 100 help the rest of our
email? I would have thought that setting it to something lower would
free up resources that yahoo would otherwise take...am i thinking
backwards?

Why would Drew or I want yahoo to saturate the active queue?
Does setting the hog_factor to 100 get the yahoo mail quickly from
incoming to defer (or fallback_relay in our case)?

Thanks for any elaborations,
jeff

Wietse Venema wrote:
>
> Drew Bloechl:
> > Right now I have a MASSIVE backlog of mail for yahoo.com (I'm trying to
> > track down where it came from), and my maillog is full of things like
> >
> > Sep 29 11:53:18 dns postfix/qmgr[3320]: F18DE110B7: to=<xxxxxxxxxxyahoo.com>, relay=none, delay=58293, status=deferred (site destination queue overflow)
> >
> > Yahoo's mail server seem to be horribly unreliable, but is there
> > anything I can do to make qmgr happy? I'm getting around 10 of these
> > per second in the maillog.
>
> It's just preventing YAHOO from blocking all your other mail delivery.
>
> Specify
>
> /etc/postfix/main.cf
> qmgr_site_hog_factor = 100
>
> to allow YAHOO to saturate your active queue.
>
> You may also want set
>
> /etc/postfix/main.cf:
> smtp_destination_concurrency_limit = 0
>
> at least until this episode is done with.
>
> Wietse