[#OP-132] Cannot reply to an email without any charset defined

Reproduction steps
usera has an emails in its INBOX without any charset (see attachment)
usera synchronize its INBOX with any device
usera reply to this email

14:44:20.269 [ERROR] {o.o.p.ActiveSyncServlet$$EnhancerByGuice$$8e1d1d01} [t4554/cSmartReply/r5077/thilaire@linagora.com] charsetName
java.lang.NullPointerException: charsetName
        at java.io.InputStreamReader.<init>(InputStreamReader.java:99) ~[na:1.7.0_65]
        at org.obm.push.mail.ReplyEmail.getBodyValue(ReplyEmail.java:135) ~[push-mail-3.0.3-SNAPSHOT.jar:na]
        at org.obm.push.mail.ReplyEmail.quoteAndAppendRepliedMail(ReplyEmail.java:107) ~[push-mail-3.0.3-SNAPSHOT.jar:na]
        at org.obm.push.mail.ReplyEmail.<init>(ReplyEmail.java:89) ~[push-mail-3.0.3-SNAPSHOT.jar:na]
        at org.obm.push.mail.MailBackendImpl.replyEmail(MailBackendImpl.java:563) ~[push-mail-3.0.3-SNAPSHOT.jar:na]
        at org.obm.breakdownduration.BreakdownDurationInterceptor.invoke(BreakdownDurationInterceptor.java:58) ~[breakdown-duration-3.0.1-al
pha3.jar:na]
        at org.obm.push.handler.SmartReplyHandler.doTheJob(SmartReplyHandler.java:66) ~[push-core-3.0.3-SNAPSHOT.jar:na]
        at org.obm.push.handler.MailRequestHandler.process(MailRequestHandler.java:107) ~[push-core-3.0.3-SNAPSHOT.jar:na]
        at org.obm.push.handler.MailRequestHandler.process(MailRequestHandler.java:86) ~[push-core-3.0.3-SNAPSHOT.jar:na]
        at org.obm.push.ActiveSyncServlet.processActiveSyncMethod(ActiveSyncServlet.java:253) ~[push-core-3.0.3-SNAPSHOT.jar:na]
        at org.obm.push.ActiveSyncServlet.doPost(ActiveSyncServlet.java:176) ~[push-core-3.0.3-SNAPSHOT.jar:na]

Expected behavior
the email is well sent, there is no exception in the log file

5.2. Content-Type Defaults Default RFC 822 messages without a MIME Content-Type header are taken by this protocol to be plain text in the US-ASCII character set, which can be explicitly specified as: Content-type: text/plain; charset=us-ascii This default is assumed if no Content-Type header field is specified. It is also recommend that this default be assumed when a syntactically invalid Content-Type header field is encountered. In the presence of a MIME-Version header field and the absence of any Content-Type header field, a receiving User Agent can also assume that plain US-ASCII text was the sender's intent. Plain US-ASCII text may still be assumed in the absence of a MIME-Version or the presence of an syntactically invalid Content-Type header field, but the sender's intent might have been otherwise.

[OP-132] Cannot reply to an email without any charset defined Created: 05/Nov/14 Updated: 19/Mar/18 Resolved: 06/Nov/14
Status:	Closed
Project:	Opush
Component/s:	None
Affects Version/s:	3.0.2
Fix Version/s:	3.0.4

[OP-132] Cannot reply to an email without any charset defined Created: 05/Nov/14 Updated: 19/Mar/18 Resolved: 06/Nov/14