postfix: value of strict_mime_encoding_domain parameter
One user complained that he didn't received one mail sent by
The postfix log contains:
bq. /var/log/mail.log:May 26 20:10:13 orfeo postfix/cleanup28928: 3rFxyF5MZxz2J9G: reject: mime-error invalid message/* or multipart/* encoding domain: quoted-printable from relais-nor34.orange.com[184.108.40.206]; from=<firstname.lastname@example.org> to=<email@example.com>
The default value of Postfix parameter
no. The current value is
yes. The Postfix documentation states:
This feature should not be enabled on a general purpose mail server, because it will reject mail after a single violation.
zgrep "reject: mime-error" /var/log/mail.log* allows to identify 11 rejected mails, possibly: 7 spams and 4 valid mails.
Duck, what do you think about using the default value for the @strict_mime_encoding_domain ?
Updated by Marc Dequènes over 3 years ago
I hate poorly written softwares. But I guess you're right we should be conservative in what you send, be liberal in what you accept.
The amount of rejected SPAMs is not that significant, so we won't load too much the pipeline and can change this setting.
Please not the ticket reference above the changed setting so that I'm not tempted to change it again.
Updated by Pierre-Louis Bonicoli over 3 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
- Security set to No
- Help Needed set to No
/etc/postfix/main.confupdate value of
strict_mime_encoding_domain = yes
was replaced by:
# Keep default value for strict_mime_encoding_domain, see issue #493 strict_mime_encoding_domain = no
- take in account the modification
Ansible configuration wasn't updated, there isn't a postfix/mail server role yet.