Enhancement #493
postfix: value of strict_mime_encoding_domain parameter
100%
Description
One user complained that he didn't received one mail sent by boutique-wifi@orange.com
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[80.12.70.34]; from=<boutique-wifi@orange.com> to=<gawan@duckcorp.org>
The default value of Postfix parameter strict_mime_encoding_domain
is 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.
The command 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
?
History
Updated by Marc Dequènes almost 7 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 almost 7 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
- Security set to No
- Help Needed set to No
toushirou
and orfeo
:
/etc/postfix/main.conf
update value ofstrict_mime_encoding_domain
: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
/etc/init.d/postfix reload
Ansible configuration wasn't updated, there isn't a postfix/mail server role yet.