|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Barak Yakir (barak
tehila.gov.il)
Date: Mon Feb 11 2008 - 12:54:22 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thanks for the reply.
Please let me rephrase my problem.
The talked about ISP policy is as follow :
1. No more then 12 TCP connection per minute. Result in a 5 minutes ban.
2. No more then 250 recipients per message. Result in discarding the
entire message.
At any given time there might be ( and had been ) more then 12 different
domains to deliver to, which are hosted behind the ISP MX host.
Constructing transport table with the hosted domain is a nightmare
because we are talking about a hundreds of domains.
How can i limit the number of connections to his MX host as well the
number of recipients per message to avoid breaking of his policy.
Thanks,
Barak Yakir
Victor Duchovni wrote:
> On Mon, Feb 11, 2008 at 08:47:36AM -0500, Wietse Venema wrote:
>
>
>> Barak Yakir:
>>
>>> Hi all,
>>>
>>> I'm trying to set my postfx 2.3.2-2 to cache destination by network address.
>>>
>>> One of our major ISP's has a primary mx record which host hundreds of
>>> domains.
>>>
>>> If I'm using smtp_connection_cache_destinations = foo.com it's working,
>>> but it's forcing me to set the list with new domain every time I'm
>>> getting an error from his mail server.
>>>
>>>
>
> You are perhaps really trying to limit concurrency to this ISP, connection
> caching alone won't dramatically reduce the concurrency demand. The Postfix
> queue manager groups/schedules messages by destination *domain*, not MX host.
>
> So unless you can construct a table of domains that resolve to the ISP's
> MX host (such a table good be built over time and used to route all the
> mail in question to a transport with a suitable process limit), you can't
> solve (what I suspect is) your real problem.
>
>
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]