Prev: Retriction order - a little advice please
Next: How to forward mail when mailbox not localy existing
From: Gary Smith on 1 May 2010 15:15
>
> Do you realize the entries you just posted are misspelled domains? They
> are not sbcglobal.net, comcast.net, or earthlink.net.
>
> -Mike

Mike, um, belay my last... My eyes are tired from clearing out queue's.

Yes, those are wrong, looks like they have some typos, but they queues that were effected were the real ones. The log files are about 50mb so I'm just eyeballing them.

I have added Noel's suggestion for syslog on the rate limiter and it is indeed being hit, which is a good thing. I might create a few separate limiters and limit them to one's and two's. This only affects any bulk mail we have going out, which is an authenticated separate server, so it should be fine.

I will also look at the dead domain reject issue Noel mentioned.

Thanks guys.

From: Wietse Venema on 1 May 2010 18:43
Gary Smith:
> Lately I have found that my outgoing queues are getting a little clogged for yahoo and sbcglobal.net. This usually coincides with a bulk set of news letters sent out from a couples clients. Typically we are seeing that they dump about 2000msg/per batch, with no more than one batch per week (usually on Friday nights). The problem is they do it in one fatal swoop. When this happens, we seem to get rate limited from yahoo/sbcglobal for a few hours, which directly affects our other users.
>
> Some time ago I put a rate limiter in place for AOL/yahoo/sbcglobal/gmail so we wouldn't be bombarding but I don't think that it's being honored, probably because I missed something. When I do a postconf I don't see my rate limiter, which is in main.cf, listed there. I'm not sure if that's by design or part of a misconfiguration on my part. Mail goes out from different sets of servers, with the same public IP, so rate limiting will only affect the bulk mail queue.
>
> Is there something obvious that I missed?
>
> master.cf:
> ratelimit unix - - n - 3 smtp
>
> rate_limit_transport:
> aol.com ratelimit:
> yahoo.com ratelimit:
> sbcglobal.net ratelimit:
> gmail.com ratelimit:
>
> main.cf:
> ratelimit_destination_concurrency_failed_cohort_limit = 100
> ratelimit_destination_concurrency_limit = 10

This DOES NOT limit your delivery RATE!!

This limits only the delivery CONCURRENCY.

To limit the delivery RATE, see
http://www.postfix.org/postconf.5.html#transport_destination_rate_delay.


Wietse

From: Gary Smith on 1 May 2010 22:43
> This DOES NOT limit your delivery RATE!!
>
> This limits only the delivery CONCURRENCY.
>
> To limit the delivery RATE, see
> http://www.postfix.org/postconf.5.html#transport_destination_rate_delay.
>

Looking into it now. Thanks for the pointer Wietse. If I'm running multiple outgoing relays, does it make sense to have some type of concurrency rate for the outgoing messages in this case?

From: Noel Jones on 1 May 2010 23:50
On 5/1/2010 9:43 PM, Gary Smith wrote:
>> This DOES NOT limit your delivery RATE!!
>>
>> This limits only the delivery CONCURRENCY.
>>
>> To limit the delivery RATE, see
>> http://www.postfix.org/postconf.5.html#transport_destination_rate_delay.
>>
>
> Looking into it now. Thanks for the pointer Wietse. If I'm running multiple outgoing relays, does it make sense to have some type of concurrency rate for the outgoing messages in this case?
>
>

As a general rule, reducing concurrency to the usual problem
domains is enough to keep mail flowing at a reasonable rate
(which is one reason I didn't address the concurrency vs. rate
delay issue). It's common for them to temporarily 4xx some of
the mail but eventually it all should go through, even with
default postfix settings.

You should sign up for "feedback loops" at each mail provider
if you haven't already. This may or may not give preference
to your mail, but is a necessary first step if you're doing
any kind of bulk mail.

If that still doesn't help, then implement the rate delay as
explained in the link Wietse gave you above. Read the link
carefully; the intent of the rate delay feature is to
significantly slow down mail delivery to the target domain.
And some domains will *still* 4xx some of the mail.

As far as multiple outgoing relays is concerned, the answer is
"maybe". The only way to know what works for *your* situation
is to try; first with the default settings, then reduce
concurrency to see if long-term delivery is any better. If the
average throughput of a mail run is significantly less than 1
delivery per second, implementing rate delays *may* allow you
to send more mail by not triggering evasive action at the
target mail server.

-- Noel Jones

From: Gary Smith on 2 May 2010 00:59
> >> This DOES NOT limit your delivery RATE!!
> >>
> >> This limits only the delivery CONCURRENCY.
> >>
> >> To limit the delivery RATE, see
> >> http://www.postfix.org/postconf.5.html#transport_destination_rate_delay.
> >>
....
> If that still doesn't help, then implement the rate delay as
> explained in the link Wietse gave you above. Read the link
> carefully; the intent of the rate delay feature is to
> significantly slow down mail delivery to the target domain.
> And some domains will *still* 4xx some of the mail.
>

Just to make sure I'm reading the docs correctly, in my case where I use the transport of ratelimit (as per the former email) I would be adding ratelimit_destination_rate_delay to main.cf. And if my understanding is correct, these are global settings so I shouldn't set them on the transport in master.cf.

Can you guys confirm that this assumption is correct?

First  |  Prev  | 
Pages: 1 2
Prev: Retriction order - a little advice please
Next: How to forward mail when mailbox not localy existing