I read that warning, but wasn't sure I understood it properly. I know that
setting destination recipient limit to anything above one defines a
destination as a domain, so by setting it to 2 we're saying wait 1s
between every delivery to a Yahoo domain,
right? And if every message sent is
I read that warning, but wasn't sure I understood it properly. I
know that setting destination recipient limit to anything above
one defines a destination as a domain, so by setting it to 2
we're saying wait 1s between every delivery to a Yahoo domain,
As for what settings work better with
On 1/18/2013 7:06 AM, Wietse Venema wrote:
I read that warning, but wasn't sure I understood it properly. I
know that setting destination recipient limit to anything above
one defines a destination as a domain, so by setting it to 2
we're saying wait 1s between every delivery to a Yahoo
On Fri, Jan 18, 2013 at 5:06 AM, Wietse Venema wie...@porcupine.org wrote:
As for what settings work better with high-volume receivers, I
suggest a search query for aol postmaster, yahoo postmaster etc.
Agreed - but Yahoo is really the only one we're having issues with (even
after complying
Am 18.01.2013 18:49, schrieb Steve Jenkins:
Agreed - but Yahoo is really the only one we're having issues with (even
after complying with all their guidelines here)
last time i had to do this , yahoo needs 3 weeks for whitelisting
the new ip, used for a mail list server
at the end if you
On Fri, Jan 18, 2013 at 09:49:34AM -0800, Steve Jenkins wrote:
Agreed - but Yahoo is really the only one we're having issues with (even
after complying with all their guidelines here):
http://help.yahoo.com/kb/index?page=contenty=PROD_MAIL_MLlocale=en_USid=SLN3435
Yes, they are willing to
On Fri, Jan 18, 2013 at 11:36 AM, Viktor Dukhovni
postfix-us...@dukhovni.org wrote:
Yes, they are willing to cripple SMTP and expect everyone to cope,
because they are too big to ignore. :-)
Sad, but true.
At that point you may not even need rate delays, just set a modest
concurrency,
On Fri, Jan 18, 2013 at 07:46:45PM -0800, Steve Jenkins wrote:
At that point you may not even need rate delays, just set a modest
concurrency, and typical SMTP transaction latency of 0.2-0.5s (
with spam checks, RBL lookups, ...) will give you at most 2-5
messages per unit concurrency per
Steve Jenkins:
yahoo_destination_concurrency_limit = 4
yahoo_destination_recipient_limit = 2
yahoo_destination_rate_delay = 1s
As documented, rate_delay enforces a delay BETWEEN deliveries to
the same destination, and therefore, the concurrency to that
destination is always 1. I see no way to
On Thu, Jan 17, 2013 at 1:03 PM, Wietse Venema wie...@porcupine.org wrote:
Steve Jenkins:
yahoo_destination_concurrency_limit = 4
yahoo_destination_recipient_limit = 2
yahoo_destination_rate_delay = 1s
As documented, rate_delay enforces a delay BETWEEN deliveries to
the same
10 matches
Mail list logo
