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

Thu Dec 1 18:30:18 GMT 2011

#4119: Answering to mails sent through messages.openstreetmap.org not correctly
paresd when using MIME emails with multipart/alternative
-----------------------------+----------------------------------------------
 Reporter:  Kurt Krampmeier  |       Owner:  rails-dev@…                
     Type:  defect           |      Status:  new                        
 Priority:  major            |   Milestone:                             
Component:  website          |     Version:                             
 Keywords:                   |  
-----------------------------+----------------------------------------------
 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=&quot
 ;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

-- 
Ticket URL: <https://trac.openstreetmap.org/ticket/4119>
OpenStreetMap <http://www.openstreetmap.org/>
OpenStreetMap is a free editable map of the whole world