> Apart from mislabeling what is most-likely in fact a CTE of "8bit" rather > than binary, what problem does this actually cause?
The problem is that Postfix frequently dropping connection of connection exchange server with error 502 5.5.2 Error: command not recognized I checked from the tcpdump that headers contain the following line. Content-Transfer-Encoding: binary And some of the characters in the binary data causing Postfix to interpret as end of data character. and remaining content is detected as error. 'non-compatible SMTP command'. > The transport of true BINARYMIME content generally also requires > CHUNKED encoding, which is also not supported by Postfix. I dimly > remember dealing with a bug in Exchange along these lines a long > time ago, and thought it was fixed not long after. How ancient is > the Exchange system in question. It is Exchange 2007 > No, but it does not matter, it certainly does not advertise such > support in the EHLO response, so sending system can legitimately > send such content into Postfix. So, connecting client can send the data using SMTP extension which is not published by SMTP server?
