Am 02.10.2012 17:37, schrieb Wietse Venema:
> Robert Schetterer:
>>> Therefore, instead of using FILTER, and instead of using filters
>>> per gmx MX record, I would use a transport map with ``gmx.net->slow:''.
>>
>> it was asked to avoid list of domains ( may getting huge ) for slow
>> transport,
Robert Schetterer:
> > Therefore, instead of using FILTER, and instead of using filters
> > per gmx MX record, I would use a transport map with ``gmx.net->slow:''.
>
> it was asked to avoid list of domains ( may getting huge ) for slow
> transport, so i tested
> check_recipient_mx_access for avoi
Am 02.10.2012 17:02, schrieb Wietse Venema:
> Robert Schetterer:
>> smtpd_data_restrictions = check_recipient_mx_access
>> hash:/etc/postfix/check_recipient_mx_access
>
> Postfix has no multi-recipient lookup feature, so the above is a
> NOOP for multi-recipient mail.
>
>> mx0.gmx.net FILTER slow
Robert Schetterer:
> smtpd_data_restrictions = check_recipient_mx_access
> hash:/etc/postfix/check_recipient_mx_access
Postfix has no multi-recipient lookup feature, so the above is a
NOOP for multi-recipient mail.
> mx0.gmx.net FILTER slow:mx0.gmx.net
> mx1.gmx.net FILTER slow:mx1.gmx.net
Absen
Am 02.10.2012 15:51, schrieb Wietse Venema:
> Robert Schetterer:
>> master.cf
>> ...
>> slow unix - - n - - smtp
>>
>> main.cf
>> slow_destination_concurrency_limit = 3
>> slow_destination_rate_delay = 1s
>> slow_destination_recipient_limit = 6
>
> With slow_destinat
Robert Schetterer:
> master.cf
> ...
> slow unix - - n - - smtp
>
> main.cf
> slow_destination_concurrency_limit = 3
> slow_destination_rate_delay = 1s
> slow_destination_recipient_limit = 6
With slow_destination_recipient_limit > 1, the scheduler controls
delays, c
Am 02.10.2012 11:23, schrieb Tom Kinghorn:
> On 02/10/2012 11:21, Robert Schetterer wrote:
>> guess this might be better
>>
>> check_recipient_mx_access type:table
>> Search the specified access(5) database for the MX hosts for the
>> RCPT TO domain, and execute the corresponding action. Note:
On 02/10/2012 11:21, Robert Schetterer wrote:
guess this might be better
check_recipient_mx_access type:table
Search the specified access(5) database for the MX hosts for the
RCPT TO domain, and execute the corresponding action. Note: a result of
"OK" is not allowed for safety reasons. Inst
Am 02.10.2012 11:15, schrieb Robert Schetterer:
> Am 02.10.2012 11:00, schrieb Tom Kinghorn:
>> On 02/10/2012 10:39, Ralf Hildebrandt wrote:
>>> * Tom Kinghorn :
>>> domainname domainname:
>>>
>>> domainname is a copy of the "smtp...smtp" line in master, renamed to
>>> "domainname.
Am 02.10.2012 11:00, schrieb Tom Kinghorn:
> On 02/10/2012 10:39, Ralf Hildebrandt wrote:
>> * Tom Kinghorn :
>> domainname domainname:
>>
>> domainname is a copy of the "smtp...smtp" line in master, renamed to
>> "domainname...smtp"
>>
>> and then use domainname_concurrency_limit
On 02/10/2012 10:39, Ralf Hildebrandt wrote:
* Tom Kinghorn :
domainname domainname:
domainname is a copy of the "smtp...smtp" line in master, renamed to
"domainname...smtp"
and then use domainname_concurrency_limit
Thanks Ralph.
I think my explanation of the problem was inc
On Tue, Oct 02, 2012 at 10:30:27AM +0200, Tom Kinghorn wrote:
> Good morning List.
[..]
> Is there a way to set the smtp_concurrency_limit for these domains
> without creating thousands of lines with
>
> domainnametransport:
Something like:
mx1.bigisp.com trans
* Tom Kinghorn :
> Good morning List.
>
> I have a problem with a service provider rejecting connections due to
> "too many concurrent connections".
> They have a huge hosting platform with thousands of domains served by
> their mail servers.
>
> Is there a way to set the smtp_concurrency_limit f
Good morning List.
I have a problem with a service provider rejecting connections due to
"too many concurrent connections".
They have a huge hosting platform with thousands of domains served by
their mail servers.
Is there a way to set the smtp_concurrency_limit for these domains
without cre
14 matches
Mail list logo
