Both postfix servers announce ‘250-8BITMIME’ support.
And no special rules have been defined for handling 8bit character encoding.
So that doesn't explain what is happening.
Am 10.03.2025 um 21:51 schrieb Wietse Venema via Postfix-users:
Wietse Venema via Postfix-users:
Andreas Kuhlen via Postfix-users:
I have two mail servers that use different content transfer encodings
for the same content. Based on the configuration, I can't work out
why this is the case.
When Postfix bounces an 8bitmime message, then the bounce message
will also be 8bitmime.
Otherwise, the encoding is chosen by the mail sending software,
and Postfix is just the messenger.
The Postfix SMTP client will by default convert 8bitmime to
quoted-printable, if it sees that the next-hop MTA (or SMTP-based
content filter) does not announce 8BITMIME support in the EHLO
response. That is controlled with:
disable_mime_input_processing
disable_mime_output_conversion
Postfix may also be configbured to forcibly convert 8bitmime to
quoted-printable. That is controlled with:
disable_mime_input_processing
force_mime_input_conversion
I wrote that code over 20 years ago, so there may be more details
that I forget to mention.
Wietse
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
