Re: Disabling TLSv1

Hello! Viktor Dukhovni schrieb am 05.03.20 um 18:52:55 Uhr: > On Fri, Mar 06, 2020 at 12:26:06AM +0100, ratatouille wrote: > > > I have just too TLSv1 connections this month: > > ... > > 11 TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits) > > 9 TLSv1.2 with cipher CAMELLIA256-SHA (256/25

Re: problem with transport

Hi Is it possible to second add header_checks after milter check ? milter_protocol = 2 milter_default_action = accept milter_connect_macros = j {daemon_name} v {if_name} _ smtpd_milters = unix:/run/spamass-milter/spamass-milter.sock,inet:localhost:12301 non_smtpd_milters = unix:/run/spamass-milte

Setting up internal catch-all address

Hello, All of my mailboxes are virtual, e.g. `al...@example.com` and `b...@example.com`. I would like to set up a catch-all virtual mailbox `catch...@example.com` such that mail sent to any other address `*@example.com` gets sent to `catch...@example.com`. Here is an excerpt of my config: > ==

Re: problem with transport

natan maciej milaszewski: > Hi > Is it possible to second add header_checks after milter check ? milter_header_checks are applied to headers that are added by a Milter. This can be used to ignore, log, or replace header text. Wietse

Re: problem with transport

Hi Thenx for replay :) Working perfectly :) On 06.03.2020 13:07, Wietse Venema wrote: > natan maciej milaszewski: >> Hi >> Is it possible to second add header_checks after milter check ? > milter_header_checks are applied to headers that are added by a > Milter. This can be used to ignore, log, or

Re: Disabling TLSv1

On 06.03.20 00:11, Daniel Ryšlink wrote: I tried disabling TLSv1.0 and TLSv1.1 on our Postfix mailservers at the beginning of the year (since there were advisories that anything older than 1.2 is considered weak and broken), and it did not end well, there were numerous complaints from what turn

Re: Disabling TLSv1

> On 5 March 2020, at 17:15, Viktor Dukhovni wrote: > > On Thu, Mar 05, 2020 at 03:57:59PM -0800, Doug Hardie wrote: > >> Small mail server with 3 weeks of logs: >> >> 1761 TLSv1 >> 18 TLSv1.1 >> 20414 TLSv1.2 >> 6343 TLSv1.3 >> >> That's not what I expected. I thought v1 and v1.1 wo

unreasonable packet length

Hello have running a little postix 2.11.3 with Dovecot and ClamAv-Milter the integration with Clammilter running over TCP, but receive the following Warning messages. Mar 6 13:38:53 mail postfix/smtpd[2091]: warning: milter inet:[127.0.0.1]:3310: unreasonable packet length: 1431194446 > 1073

Re: unreasonable packet length

mauri...@caloro.ch: > Hello > > have running a little postix 2.11.3 with Dovecot and ClamAv-Milter > > the integration with Clammilter running over TCP, but receive the following > Warning messages. > > > > Mar 6 13:38:53 mail postfix/smtpd[2091]: warning: milter > inet:[127.0.0.1]:3310: unr

Re: Disabling TLSv1

On Fri, Mar 06, 2020 at 05:51:19AM -0800, Doug Hardie wrote: > > An interesting question in your case is what fraction of the TLSv1 > > connections are non-spam. Perhaps you're able to correlate the TLSv1 > > connections with legitimate vs. junk email. > > Results for 3 weeks of log files: > >