Re: Connection Caching Per-Destination

2020-07-31 Thread Greg Sims
> Your real problem is however your IP reputation. If you're sending > unsolicited email, or you have relay customers sending unsolicited mail, > then your difficulties delivering it are a desirable feature of > Microsoft's email service. If you're sending email outlook.com > customers want, then

Re: Connection Caching Per-Destination

2020-07-31 Thread Greg Sims
The situation with outlook got much worse in our overnight runs. We transferred 7K subscriber emails to relays ending in outlook.com and saw the following feedback in our logs: MaxConnections: 83, Connection: 1386, RateLimited: 6392 where the following regexp is used in our log post-processor:

Re: Forwarding best practices

2020-07-31 Thread @lbutlr
On 31 Jul 2020, at 14:18, John Regan wrote: > This mail server has an SPF record for itself, but no DKIM or DMARC. It also > has a working reverse DNS. Mail is received by this system from two postfix > relays protected with spamassassin and monitored closely. Yahoo doesn’t care, and IME will r

Forwarding best practices

2020-07-31 Thread John Regan
Hi, I have a postfix-3.4.10 system being used as a relay for a subdomain where most users are forwarding their mail through it instead of sending and receiving email on it directly using a ~/.forward file and procmail. Users can send and receive mail using their desktop email client connected thro

Re: Connection Caching Per-Destination

2020-07-31 Thread Wietse Venema
Viktor Dukhovni: > On Fri, Jul 31, 2020 at 02:16:54PM -0400, Wietse Venema wrote: > > > Logged as conn_use=xxx. By default, reuse happens only for plaintext > > connections. > > > > > >smtp_tls_connection_reuse=yes > > > > Logged as TLS handshake results plus conn_use=xxx. > > One thing we

Re: Connection Caching Per-Destination

2020-07-31 Thread Viktor Dukhovni
On Fri, Jul 31, 2020 at 02:16:54PM -0400, Wietse Venema wrote: > Logged as conn_use=xxx. By default, reuse happens only for plaintext > connections. > > > >smtp_tls_connection_reuse=yes > > Logged as TLS handshake results plus conn_use=xxx. One thing we could likely improve in TLS connectio

Re: Connection Caching Per-Destination

2020-07-31 Thread Wietse Venema
@lbutlr: > On 30 Jul 2020, at 12:53, Wietse Venema wrote: > > main.cf: > >smtp_connection_cache_on_demand=yes Logged as conn_use=xxx. By default, reuse happens only for plaintext connections. > >smtp_tls_connection_reuse=yes Logged as TLS handshake results plus conn_use=xxx. Wi

Re: Connection Caching Per-Destination

2020-07-31 Thread Viktor Dukhovni
On Fri, Jul 31, 2020 at 11:47:57AM -0600, @lbutlr wrote: > On 30 Jul 2020, at 12:53, Wietse Venema wrote: > > main.cf: > >smtp_connection_cache_on_demand=yes > >smtp_tls_connection_reuse=yes > > Do these setting show up in anyway int he logs (that is, does the log look > any different if

Re: Connection Caching Per-Destination

2020-07-31 Thread @lbutlr
On 30 Jul 2020, at 12:53, Wietse Venema wrote: > main.cf: >smtp_connection_cache_on_demand=yes >smtp_tls_connection_reuse=yes Do these setting show up in anyway int he logs (that is, does the log look any different if a TLS connection is reused or a connection is using cache_on_demand.

Re: Connection Caching Per-Destination

2020-07-31 Thread Wietse Venema
Greg Sims: > The situation with outlook got much worse in our overnight runs. We > transferred 7K subscriber emails to relays ending in outlook.com and > saw the following feedback in our logs: > > MaxConnections: 83, Connection: 1386, RateLimited: 6392 > > where the following regexp is used in

Re: Connection Caching Per-Destination

2020-07-31 Thread Viktor Dukhovni
On Fri, Jul 31, 2020 at 09:37:12AM -0700, Greg Sims wrote: > RateLimited -- "^.*The mail server .* has been temporarily rate > limited due to IP reputation.*$" There's your problem. You need a better IP reputation. > (1) smtpd_tls_security_level = none & smtp_tls_security_level = none > in mai

Re: Connection Caching Per-Destination

2020-07-31 Thread Wietse Venema
Viktor Dukhovni: > > On Jul 31, 2020, at 12:33 PM, Wietse Venema wrote: > > > >> No, you *do not* want to do that. That can increase connection > >> concurrency beyond your process limit, in the form of idle connections > >> that have a different nexthop than the one to which you're currently > >

Re: Connection Caching Per-Destination

2020-07-31 Thread Viktor Dukhovni
> On Jul 31, 2020, at 12:33 PM, Wietse Venema wrote: > >> No, you *do not* want to do that. That can increase connection >> concurrency beyond your process limit, in the form of idle connections >> that have a different nexthop than the one to which you're currently >> delivering email. > > We

Re: Connection Caching Per-Destination

2020-07-31 Thread Wietse Venema
Viktor Dukhovni: > > We would like to use Per-Destination Connection Caching to increase > > our throughput for "outlook:". > > No, you *do not* want to do that. That can increase connection > concurrency beyond your process limit, in the form of idle connections > that have a different nexthop t

Re: Connection Caching Per-Destination

2020-07-31 Thread Greg Sims
> > We would like to use Per-Destination Connection Caching to increase > > our throughput for "outlook:". > > No, you *do not* want to do that. That can increase connection > concurrency beyond your process limit, in the form of idle connections > that have a different nexthop than the one to whi