On Thu, Jul 30, 2020 at 09:49:07PM -0700, Greg Sims wrote:
> > Instead, you want to *disable* even demand connection caching.
>
> I updated master.cf based on your recommendation:
>
> outlook unix - - n - 6 smtp
> -o syslog_name=outlook
> -o smtp_connection_cache_on_demand=no
>
> We have our ip addresses signed up for both SNDS and JMRP. Are there
> additional white list strategies for Microsoft?
I am not a bulk-mail sender, so I don't know.
> Turning off connection caching is not intuitive from reading the
> CONNECTION_CACHE_README which says:
>
> SMTP Connection caching can also help with receivers that impose rate
> limits on new connections.
Well, *rate* limits != concurrency limits. Are they complaining about
too many connections at the same time, or too many connections per unit
time? I understood the issue to be too many *concurrent* connections.
If it is connections per unit time, then indeed connection caching could
help, but only at the cost of increasing concurrency. Pick your poison.
Better yet, get your limits raised (I don't know how, but there ought
to be a way).
> Perhaps I wanted the connection cache to be the solution for "has
> exceeded the maximum number of connections" when I read the README.
Well is it maximum (concurrent) *number* or maximum rate?
--
Viktor.
