Hello everyone,
It's very strange, but without changing anything in the configuration of
Postfix, we have corrupted SMTP transactions from Thunderbird bêta
(Windows) and Outlook (MacOS) but not from command line (Linux) and not
from Thunderbird release (Windows).
The transaction looks like t
P. S. The logs in my previous email are from Thunderbird Windows bêta,
here are the logs from MacOS Outlook :
Apr 14 11:07:44 mailsvr postfix/smtps/smtpd[19395]: connect from
185.81.185.81.rev.sfr.net[81.185.81.185]
Apr 14 11:07:44 mailsvr postfix/smtps/smtpd[19395]: match_hostaddr:
81.185.8
P. S. daemon started -- version 2.9.6
Le 14.04.2021 à 11:55, (lists) Denis BUCHER a écrit :
P. S. The logs in my previous email are from Thunderbird Windows
bêta, here are the logs from MacOS Outlook :
Apr 14 11:07:44 mailsvr postfix/smtps/smtpd[19395]: connect from
185.81.185.81.rev.sfr
On 14 Apr 2021, at 5:47, (lists) Denis BUCHER wrote:
Hello everyone,
It's very strange, but without changing anything in the configuration
of Postfix, we have corrupted SMTP transactions from Thunderbird bêta
(Windows) and Outlook (MacOS) but not from command line (Linux) and
not from Thunde
Dnia 14.04.2021 o godz. 08:51:23 Bill Cole pisze:
>
> Your problem is consistent with your 'smtps' service (port 465) not
> having the critical "-o smtpd_tls_wrappermode=yes" argument enabled
> in master.cf. The differences between clients is likely due to
> different configurations and/or differe
On 14.04.21 11:55, (lists) Denis BUCHER wrote:
P. S. The logs in my previous email? are from Thunderbird Windows
bêta, here are the logs from MacOS Outlook :
we don't need logs from thunderbird/outlook.
we need plaintext logs, possibly in plaintext mail
(well, outlook is much worse here becaus
On 2021-04-14 06:27, Simon Wilson wrote:
Like you I use amavis to DKIM sign outbound email, not opendkim. I
just prefer the way it handles it.
I know it's a different setup to yours, but may provide an alternate
route.
amavisd could support metacpan Mail::DMARC
with imho could help simplify
After today's occurrence of missing tls_wrappermode configuration
I was thinking about Postfix SMTP server support to detect a TLS
handshake where an SMTP command is expected.
Such a feature should be enabled by default, otherwise it would not
be useful. It should also be configurable by default,
TL;DR: the idea is to change the smtpd_forbidden_commands default
setting to something like:
CONNECT GET POST pcre:{/^\x16/ Possible TLS handshake}
Which would match current TLS protocols.
Wietse
On Wed, Apr 14, 2021 at 02:24:23PM -0400, Wietse Venema wrote:
> TL;DR: the idea is to change the smtpd_forbidden_commands default
> setting to something like:
>
> CONNECT GET POST pcre:{/^\x16/ Possible TLS handshake}
>
> Which would match current TLS protocols.
I guess subject to "#ifdef H
Viktor Dukhovni:
> On Wed, Apr 14, 2021 at 02:24:23PM -0400, Wietse Venema wrote:
> > TL;DR: the idea is to change the smtpd_forbidden_commands default
> > setting to something like:
> >
> > CONNECT GET POST pcre:{/^\x16/ Possible TLS handshake}
> >
> > Which would match current TLS protocols
Hi Bill,
Le 14.04.2021 à 14:51, Bill Cole a écrit :
On 14 Apr 2021, at 5:47, (lists) Denis BUCHER wrote:
It's very strange, but without changing anything in the configuration
of Postfix, we have corrupted SMTP transactions from Thunderbird
bêta (Windows) and Outlook (MacOS) but not from comma
On 14 Apr 2021, at 15:55, (lists) Denis BUCHER wrote:
> smtps inet n - - - - smtpd
> -o syslog_name=postfix/smtps
> -o smtpd_sasl_auth_enable=yes
> -o smtpd_client_restrictions=permit_sasl_authenticated,reject
Seems short.
smtps inet n
13 matches
Mail list logo
