Patrick Proniewski: > Jun 17 12:34:20 postfix-mailgw/smtp[77347]: 57F56EB256: > to=<login@exchg.domain>, orig_to=<userpart@domain>, > relay=Exchange-VIP[Exchange-VIP]:25, delay=0.01, delays=0.01/0/0/0, > dsn=5.6.7, status=bounced (SMTPUTF8 is required, but was not offered by host > Exchange-VIP[Exchange-VIP]) >
It is required (in this case, by RFC 6531..6533). With "smtputf8_enable = yes" (the default) Postfix must return mail as undeliverable when: - a sending SMTP client requested SMTPUTF8 in the MAIL FROM command(*), - and a receiving SMTP server does not announce SMTPUTF8 support. However, Postfix ignores this requirement when a message has no UTF8 in the header, sender, or recipient envelope address. Options: - SMTPUTF8 support in Microsoft Exchange Server protocol revision 14.0 (from 2018) or later. https://en.wikipedia.org/wiki/Extended_SMTP#SMTPUTF8 - Postfix: set "smtputf8_enable = no" so that Postfix will not be able to receive such email messages (i.e. they will be returned to the sender before they reach Postfix). There is no defined conversion from SMTPUTF8 mail to historical email, and I decided not to invent one because it would solve only a temporary problem. > smtputf8_autodetect_classes = verify (*) smtputf8_autodetect_classes enables SMTPUTF8 autodetection for the smtpd service. this 'detects' UTF8 in MAIL FROM, RCPT TO, and in the header. But you don't have it enabled for any Postfix service that receives email, therefore smtputf8_autodetect_classes was not part of your problem. Wietse
