Return-Path: Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 97790 invoked by uid 500); 22 Aug 2003 02:36:56 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 97767 invoked from network); 22 Aug 2003 02:36:56 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 22 Aug 2003 02:36:56 -0000 Received: (qmail 24029 invoked by uid 50); 21 Aug 2003 15:32:13 -0000 Date: 21 Aug 2003 15:32:13 -0000 Message-ID: <20030821153213.24028.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: dev@ant.apache.org Cc: Subject: DO NOT REPLY [Bug 15434] - MimeMailer doesn't work properly with national charset X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15434 MimeMailer doesn't work properly with national charset ------- Additional Comments From antoine@apache.org 2003-08-21 15:32 ------- While working on another email issue, I realized that the charset attribute should be used in the headers in the PlainMailer. So I have put this piece of code in PlainMailer. if (message.getCharset() != null) { mailMessage.setHeader("Content-Type", message.getMimeType() + "; charset=\"" + message.getCharset() + "\""); } else { mailMessage.setHeader("Content-Type", message.getMimeType()); } PlainMailer did not specify the charset before. I have tested this by sending to myself with ant an email message in hebrew. Works like a charm. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org