Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Answering to mails sent through messages.openstreetmap.org not correctly paresd when using MIME emails with multipart/alternative #4119

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 2 comments

Comments

@openstreetmap-trac
Copy link

Reporter: Kurt Krampmeier
[Submitted to the original trac issue database at 6.03pm, Thursday, 1st December 2011]

Answering a mail, that was sent through the OSM message system (e. g. http://www.openstreetmap.org/message/new/Kurt%20Krampmeier), causes unwanted results for the reader, when the reply is a multipart/alternative email. Creating multipart/alternative email is unfortunately the default setting in many popular mail clients and web mailers.

In such cases, the whole mail body (both parts in their transfer encoding along with their headers and boundaries) is interpreted as the message text. So a simple answer like "Hello World!" might show up as

"This is a multi-part message in MIME format.
--------------050501020709070602040306
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hello World!

--------------050501020709070602040306
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hello World!
</body>
</html>

--------------050501020709070602040306--" in the receiver's mail. The display on the OSM website is also wrong in a similar way.

The wrong use of HTML entities shown in this example is caused by another bug: http://trac.openstreetmap.org/ticket/4118

@openstreetmap-trac
Copy link
Author

Author: Kurt Krampmeier
[Added to the original trac issue at 6.33pm, Thursday, 1st December 2011]

Trac has replaced the boundary lines by thin gray horizontal rules. The result is still bad enough to show the problem clearly.

@openstreetmap-trac
Copy link
Author

Author: TomH
[Added to the original trac issue at 7.55pm, Thursday, 1st December 2011]

Fixed - we now only use one part. Will be deployed shortly.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant