[Kde-pim] Outlook help needed: RFC2231 encoding test

[Volker Krause]

Hi,

if anyone here has access to a semi-recent Outlook or Exchange and could
verify that the name of the attachment in the attached email is decoded
correctly there ("Däß üst äin Töst.txt"), that would be greatly appreciated.

Background: we have hacks in KMail and KMime to (optionally) generate
attachment names that violate RFC2231, dating back to the end of the last
century. I suspect that nobody uses Outlook 97 nowadays and this isn't an
issue anymore :)

Thanks!
Volker

[Ingo Klöcker]

Post by Volker Krause
Hi,
if anyone here has access to a semi-recent Outlook or Exchange and
could verify that the name of the attachment in the attached email is
decoded correctly there ("Däß üst äin Töst.txt"), that would be
greatly appreciated.

Outlook Web App could open the attachment inside the attached email
correctly. I think it's using Exchange 2010. Tomorrow I'll double-check
Outlook.


Regards,
Ingo

[Andre Heinecke]

Hi,

Post by Volker Krause
Hi,
if anyone here has access to a semi-recent Outlook or Exchange and could
verify that the name of the attachment in the attached email is decoded
correctly there ("Däß üst äin Töst.txt"), that would be greatly appreciated.
Background: we have hacks in KMail and KMime to (optionally) generate
attachment names that violate RFC2231, dating back to the end of the last
century. I suspect that nobody uses Outlook 97 nowadays and this isn't an
issue anymore :)

With German Outlook 2013/ 2016 it is only shown as "Unbenannte Anlage <some
number>".

But weirdly enough it does not appear to make any difference if I enable
Outlook compatible attachment names or not:

Tested:
E35 -> Outlook compatible names / no compatible names, UTF-8 -> broken
KDE 4.14 -> Compatible names / no compatible names, UTF-8 -> broken
KDE 4.14 -> Compatible names, latin-1 -> broken

These tests were all with outlook 2013/2016 So It's probably broken differently
now? :-)

Attached you can find a message sent by Outlook 2016 using your test file.

Regards,
Andre

P.S. If necessrary I can test with 2003, 2007 and 2010, too but this is a bit
more effort because I only have remote access to those.

[Andre Heinecke]

Hi,

Post by Andre Heinecke
Attached you can find a message sent by Outlook 2016 using your test file.

Uh this got mangled rather badly. In my sent mails folder it looks ok But the
mail I received over this list has a broken signature and a completely mangled
attachment name. Probably because I still had Outlook compatible attachment
naming active.

When I get a mail from Outlook I see this as the attachment header:

Content-Type: text/plain;
name="=?iso-8859-1?B?ROTfIPxzdCDkaW4gVPZzdC50eHQ=?="
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="=?iso-8859-1?B?ROTfIPxzdCDkaW4gVPZzdC50eHQ=?="

Regards,
Andre

P.S.
I'm attaching the mail again this time without Outlook Compatible attachment
naming configured in KMail.

[Ingo Klöcker]

Post by Andre Heinecke
Hi,

Post by Andre Heinecke
Attached you can find a message sent by Outlook 2016 using your test file.

Uh this got mangled rather badly. In my sent mails folder it looks ok
But the mail I received over this list has a broken signature and a
completely mangled attachment name. Probably because I still had
Outlook compatible attachment naming active.

Here (using KMail against Exchange 2010 over IMAP) the attachment name
is not mangled in your first message. OTOH, when I look at this message
in OWA then the attachment name is mangled. It seems KMail is more
forgiving.

Content-Type: text/plain;
name*=''D%C3%A4%C3%9F%20%C3%BCst%20%C3%A4in%20T%C3%B6st%2Etxt
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename*=''D%C3%A4%C3%9F%20%C3%BCst%20%C3%A4in%20T%C3%B6st%2Etxt

Post by Andre Heinecke
Content-Type: text/plain;
name="=?iso-8859-1?B?ROTfIPxzdCDkaW4gVPZzdC50eHQ=?="
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="=?iso-8859-1?B?ROTfIPxzdCDkaW4gVPZzdC50eHQ=?="
Regards,
Andre
P.S.
I'm attaching the mail again this time without Outlook Compatible
attachment naming configured in KMail.

For this mail the attachment name looks mangled on my system and in OWA
which isn't surprising given that all non-ASCII characters seem to be
encoded as %EF%BF%BD.

Content-Type: text/plain;
name*=''D%EF%BF%BD%EF%BF%BD%20%EF%BF%BDst%20%EF%BF%BDin%20T%EF%BF%BDst%2Etxt
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename*=''D%EF%BF%BD%EF%BF%BD%20%EF%BF%BDst%20%EF%BF%BDin%20T%EF%BF%BDst%2Etxt


Regards,
Ingo

[Volker Krause]

Post by Volker Krause
Hi,
if anyone here has access to a semi-recent Outlook or Exchange and could
verify that the name of the attachment in the attached email is decoded
correctly there ("Däß üst äin Töst.txt"), that would be greatly appreciated.
Background: we have hacks in KMail and KMime to (optionally) generate
attachment names that violate RFC2231, dating back to the end of the last
century. I suspect that nobody uses Outlook 97 nowadays and this isn't an
issue anymore :)

Thanks a lot for the test results we got so far, on- and off-list!

The results are largely inconclusive though. Summary so far: Some instances of
2010 seem to properly decode the RFC2231 names, one fails on my test mail but
works on self-generated KMail mails. All 2013 instances fail entirely to
decode the test case. 2016 seems to still generate the non-RFC2231 encoding.

Interestingly enough all reports confirm that the Outlook compat naming option
makes no difference. Probably means that option is entirely broken.

So, we found a bunch of new issues here apparently, not exactly what I was
hoping for :-/

Anyone with a GMail account who could check what that generates? Wondering if
that's RFC2231 and how Outlook handles that, considering it's probably the
most commonly used mail client nowadays.

regards,
Volker

[Ingo Klöcker]

Post by Volker Krause
Anyone with a GMail account who could check what that generates?
Wondering if that's RFC2231 and how Outlook handles that, considering
it's probably the most commonly used mail client nowadays.

The relevant parts of a test message sent from GMail look as follows:

--f46d043bdf863fc1520520d2a84f
Content-Type: text/plain; charset="US-ASCII";
name="=?UTF-8?B?RMOkw58gw7xzdCDDpGluIFTDtnN0LnR4dA==?="
Content-Disposition: attachment;
filename="=?UTF-8?B?RMOkw58gw7xzdCDDpGluIFTDtnN0LnR4dA==?="
Content-Transfer-Encoding: base64
X-Attachment-Id: f_if496yu10

SGVsbG8gV29ybGQhCg==

--f46d043bdf863fc1520520d2a84f--


So, except for the different character encoding it looks like mails
generated by Outlook/OWA.


Regards,
Ingo