On Tue, Apr 04, 2023 at 09:00:16PM +0200, A. Schulze via Postfix-users wrote:
> Mime-Version: 1.0
> Content-Type: multipart/signed;
> boundary="mua-name=_some_random";
> protocol="application/pkcs7-signature";
> micalg=sha-256
> Content-Transfer-Encoding:
Hello,
an SMTP Server with strict_mime_encoding_domain=yes blocked some messages
(which was ... unexpected)
# postconf mail_version
mail_version = 3.7.4
# postconf -n
alias_maps =
maillog_file = /dev/stdout
smtpd_recipient_restrictions = defer
strict_mime_encoding_domain = yes
# postconf -M
Pretend I'm an idiot. (For most people who know me this won't be hard.)
Could somebody please explain to me... in a way that takes into account
my idiocy... what this strict_mime_encoding_domain option actually does,
i.e. if you turn it on?
What exactly constitutes invalid Content-Transfer
Ronald F. Guilmette:
Pretend I'm an idiot. (For most people who know me this won't be hard.)
Could somebody please explain to me... in a way that takes into account
my idiocy... what this strict_mime_encoding_domain option actually does,
i.e. if you turn it on?
It stops some malformed
