Missing characters in the mails on outlook

[prevost...@gmail.com]

Hello great team,

Caractères are not shown in mail received on Outlook. é à and others special caractères are not shown

é, è, à or other special characters from user details are not visible, repport send to councils are impacted too

Template/email/mycobrand/*.txt files are in UTF8

For information it shown well on my iPhone.

this is very annoying, any solution known ?

[Matthew Somerville]

Hi,

I'm sorry to hear that. As far as I know, the emails FixMyStreet sends
out are valid and contain the correct headers for display by various
email programs. I have just tried some emails containing accented
characters locally and they all appear to work okay. I have also sent
a confirmation email to a friend who uses Outlook and the message
displays okay (see attached screenshot). Is it possible these people
have Outlook configured incorrectly in some way?

The only thing I can see from Googling is
http://answers.microsoft.com/en-us/office/forum/office_2010-outlook/outlook-2010-replaces-in-html-utf-8-charset/47766d0c-a658-e011-8dfc-68b599b31bf5
which says it's fixed by updating Outlook.

Sorry, I'm not sure what to suggest, unless we can get more
information. Is this one occurrence or happening to multiple versions
of Outlook in different places? Could one of the Outlook users view
the message source and forward that on to you so you can check that
they've received the right data? Could they see if there's a way to
manually set the character encoding, see if setting it to UTF-8 fixes
it, and whether their Outlook is set up to not automatically detect
content type? Other things like that.

Yours,
Matthew

[prevost...@gmail.com]

hi,

thanks for your reply,

I tried to pass perllib/FixMystreet/Email.pm to "8bit" encode than "quoted-printable",

@matthew : Note that, when you tried on our serveurs your test, Email.pm was in 8bit, now it is back to "quoted-printable" encode you can then retry your test if you want.

Encode 8 bit in Email.pm solved for email problem-confirm.txt received on our Outlook version but failed to shown well on others platforme.
Councils reports received with 8bit encode all failed to show well.

Same version of Outlook 2007 got me diferent results when mail comes from diferent relay.

Using gmail/Ovh as MTA (failed to show accent in "Quoted-printable" encode but shown ok in "8bit" encode on our outlook MUA).
When used Exchange as MTA ( all was well shown in encode "quoted-printable" but failed in 8bit).
When used GMAIL as MUA in webmail ( all was well shown in encode "quoted-printable" but failed in 8bit).

maybe this came from the fact of using \n \ or \CRLF \LF at the end of line or at tehe end of the mail, i knew "quoted-printable" encode is sensitive about terminaison.

Failed test was on Outlook 2007 last update,

[Matthew Somerville]

Hi,

On 27 May 2016 at 14:36, <prevost...@gmail.com> wrote:
> @matthew : Note that, when you tried on our serveurs your test, Email.pm was
> in 8bit, now it is back to "quoted-printable" encode you can then retry your
> test if you want.

My first test email was quoted-printable, not 8bit, not sure if that
is useful to you.
I don't think quoted-printable can be the issue, that has been around
for a long time.

> maybe this came from the fact of using \n \ or \CRLF \LF at the end of line
> or at tehe end of the mail, i knew "quoted-printable" encode is sensitive
> about terminaison.

I don't believe there is any issue with our email line endings. As far
as I can tell, the emails we are generating are valid, and we haven't
had any complaints anywhere else :(

If your normal mails sent to Outlook via non-FixMyStreet means are
displaying okay, then you need to find out what the difference is in
those emails/headers, or try and provoke the same behaviour with an
outside email. Is the name in the To: line broken as well, or only the
name in the body?

The code currently uses Base64 MIME Encoding for the headers, a
Content-Type of 'text/plain; charset="utf-8"' and a
Content-Transfer-Encoding of 'quoted-printable'.

Can you send emails to your Outlook with different combinations of
those, narrowing down which of them causes the issue? What if the
charset doesn't have quote marks or is in capitals? Or a different
encoding? I'm afraid I don't have Outlook 2007 here in order to help
out. If an ISO-8859-* standard works for you, we could e.g. switch the
code to trying that first before UTF-8, though that should be
unnecessary.

ATB,
Matthew

[prevost...@gmail.com]

thank you so much for your work and feedback, i hope this only affect one as you said.

Sincerely,

Greg

Le vendredi 27 mai 2016 02:14:25 UTC+2, prevost...@gmail.com a écrit :