Hi,
This look like more client's related to retrieve and edit the mails rather than postfix itself, and you might require to look deeper into the email once corrupted. Does the corrupted is identical/similar between the Webmail VS your email client? Postfix does by default allow and understand such of formatting, however you might require to enable/force the UTF-8 support on postfix. postconf "smtputf8_enable <http://www.postfix.org/postconf.5.html#smtputf8_enable> = yes" http://www.postfix.org/SMTPUTF8_README.html#enabling you can verify if this is well announced at the ehlo command Postfix SMTP server announces SMTPUTF8 support in the EHLO response. Good luck. Nicolas. On 22 November 2017 at 08:46, wodel youchi <wodel.you...@gmail.com> wrote: > Hi, > > I need some clarification about Content-Type on an email. > > Who does fix the Content-Type of an email? > The mail client? or the sending server or both? > > We have postfix as our MTA and we use Horde Groupware for the web mail and > both outllook and thuderbird as mail client. > > And know we are in phase of integrating a new application, developed by a > third party, in our company that uses our mail server to send mail to our > clients. > > The problem : if we edit mails using the webmail or the mail clients using > non ASCII characters, they're well interpreted, but when using the > application to send emails via our mail server, the non ASCII characters > are not show properly. > > The third party says that it's a problem with our mail server, they need > to know the : *SMTP Server encoding, and the UTF-8 encoding details*. > > I searched the net about postfix and utf-8 but I didn't find any thing > about showing the SMTP server encoding neither UTF-8 encoding details. > > Any idea? > > Regards. > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Garanti > sans virus. www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > <#m_4131765726631382984_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >
