> On Nov 22, 2017, at 3:46 AM, wodel youchi <wodel.you...@gmail.com> wrote: > > 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.
That is, your server is working fine. > 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. The third party's support people you're talking to are clueless bozos, or (worse) their application developers are clueless bozos, or both. > 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? The content of email messages is created and read by user agents, all MTAs do is move it around from source to destination, and in some cases apply an 8-bit to 7-bit content transfer encoding when relaying mail from an 8BITMIME source to an ASCII-only destination. We're assuming that you don't have any header_checks rules that damage the MIME structure of received messages (unlikely since regular mail works fine). MIME content transfer encodings do not change the content seen by users, the receiving user agent will undo any transfer encoding (either base64 or quoted-printable). You need to capture (with "tcpdump" or similar) the SMTP stream between the application and your SMTP server and see whether the application is emitting correctly encoded messages. http://www.postfix.org/DEBUG_README.html#sniffer -- Viktor.
