Re: Connection Caching for One Transport

2020-07-22 Thread Greg Sims
> > We have main.cf configured as follows: > > > > sender_dependent_default_transport_maps = > > randmap:{r192,r193,r194,r195,r196,r197,r198} > > smtp_connection_cache_on_demand=no > > Can you share your reason for avoiding connection caching in general? Our current mail server uses one ip address

Re: Get MUA from Logs?

2020-07-22 Thread Gerald Galster
> Is it possible to determine the Mail User Agents in use via logging in > Postfix and / or Dovecot? Assert you're using header-checks with pcre in main.cf: header_checks = pcre:/etc/postfix/header_checks Then add the following to /etc/postfix/header_checks and reload postfix: /^(User-Agent|X

RE: Get MUA from Logs?

2020-07-22 Thread Paolo Schiro
Hallo Asai,MUA informations are not passed trough POP or IMAP protocol therefore there is no way to get it recorded into logs as I know.SMTP is almost the same but MUAs are known to insert a range of different mime headers and values into generated messages.In theory you may try to log them usin

Re: Get MUA from Logs?

2020-07-22 Thread Ralph Seichter
* a...@globalchangemusic.org: > Is it possible to determine the Mail User Agents in use via logging in > Postfix and / or Dovecot? You can configure Postfix to log headers like "User-Agent", but not all MUAs generate this type of information. -Ralph

Re: postfix 3.5.4 centos 8 hardcoded crypto settings?

2020-07-22 Thread Leonardo Rodrigues
Em 22/07/2020 12:45, Viktor Dukhovni escreveu: The plan is to soon not require Postfix users to go down that particular rabbit hole. Instead Postfix will disable any TLS protocol lower/upper bounds inherited from system policy, and apply its own, based on whichever of: lmtp_tls_protocols,

Connection Caching for One Transport

2020-07-22 Thread Greg Sims
We are distributing a daily email to our subscribers -- which generates a large burst of email. We have main.cf configured as follows: sender_dependent_default_transport_maps = randmap:{r192,r193,r194,r195,r196,r197,r198} smtp_connection_cache_on_demand=no Distributing the traffic across seven ip

Re: postfix 3.5.4 centos 8 hardcoded crypto settings?

2020-07-22 Thread Viktor Dukhovni
On Wed, Jul 22, 2020 at 11:11:27AM -0400, Xavier Belanger wrote: > It is, the idea is to define exception in the system crypto policy > used by the system. There is multiple ways to do this: > > [ > https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening

Re: Connection Caching for One Transport

2020-07-22 Thread Viktor Dukhovni
On Wed, Jul 22, 2020 at 07:38:52AM -0700, Greg Sims wrote: > We have main.cf configured as follows: > > sender_dependent_default_transport_maps = > randmap:{r192,r193,r194,r195,r196,r197,r198} > smtp_connection_cache_on_demand=no Can you share your reason for avoiding connection caching in gener

Re: Connection Caching for One Transport

2020-07-22 Thread Wietse Venema
Greg Sims: > This seems like a good scenario to > use smtp_connection_cache_on_demand=yes. Is it possible to configure this > for just majortransport? It seems turning on the connection_cache for the > entire installation will reduce the randomness and effectiveness of the > randmap. To overrid

Re: postfix 3.5.4 centos 8 hardcoded crypto settings?

2020-07-22 Thread Xavier Belanger
Hi, Kris Deugau wrote: > It should be possible to set options like this in /etc somewhere, which > shouldn't be overwritten on package upgrades. I'm not sure where > CentOS/RHEL/Fedora have put the relevant OpenSSL configuration recently, > but on Debian and derivatives this can be set in /e

Re: postfix 3.5.4 centos 8 hardcoded crypto settings?

2020-07-22 Thread Kris Deugau
Xavier Belanger wrote: Hi, Leonardo Rodrigues wrote:     You nailed it, Viktor and Xavier, it was the default system-wide setup on the CentOS 8 OS from file /usr/share/crypto-policies/DEFAULT/opensslcnf.txt     setting MinProtocol to TLSv1 there did the trick.     Thank you guys!