On Fri, Jul 29, 2016 at 05:41:25PM -0400, Alex wrote:
> 279628D68138D 33026 Fri Jul 29 17:09:21 salest...@example.com
> (host mailstore1.secureserver.net[72.167.238.32] refused to talk to
> me: 421 p3plibsmtp01-06.prod.phx3.secureserver.net bizsmtp Connection
> refused, too many sessions from 66.104.132.100. Please lower the
> number of concurrent sessions. IB007 <http://x.co/rlbounce>)
Note that the nexthop domain "example.com" is not
"mailstore1.secureserver.net", which the MX host for the nexthop
domain.
> /etc/postfix/transport_limit:
> /secureserver\.net$/ turtle:
Transport lookups are by nexthop domain, not MX hostname. Also
the regexp is not sufficiently specific, but that's not important,
since you'll end up deleting this transport table.
> I've tried to configure destination concurrency, but I must not be
> doing it correctly. Can someone review my changes and let me know what
> I'm doing wrong?
>
> transport_maps = regexp:/etc/postfix/transport_limit
This is useless unless you're sending a lot of mail to recipients
in domains that end in "secureserver.net". This is likely not your
problem.
> turtle_initial_destination_concurrency = 1
> turtle_destination_concurrency_limit = 1
> turtle_destination_rate_delay = 4s
Once you set "destination_rate_delay", the concurrency is automatically
set to 1.
> turtle_destination_recipient_limit = 2
The lower you set this, the more mail you end up sending when you
have messages with multiple recipients. For RFC 5321 interoperability,
they are required to accept 100 recipients. Surely they accept at
least 10 or even 50 (which is what Postfix sends by default).
> I realize that by setting initial_destination_concurrency to 1 it's on
> a per-domain basis, which is what I believe I need.
The two are unrelated. Wietse's comment was hasty, he misread your
message to say a *recipient* concurrency of 1, but that's 2.
Postfix has no per-MX-host rate limits, the scheduler (qmgr) is
not MX-aware.
--
Viktor.
