UTF-8 charset doesn't work with javax.mail

85,439

Solution 1

For all e-mails

There are a couple of system properties related to mailing, that can probably simplify your code. I am talking about this specific property actually: "mail.mime.charset".

The mail.mime.charset System property can be used to specify the default MIME charset to use for encoded words and text parts that don't otherwise specify a charset. Normally, the default MIME charset is derived from the default Java charset, as specified in the file.encoding System property. Most applications will have no need to explicitly set the default MIME charset. In cases where the default MIME charset to be used for mail messages is different than the charset used for files stored on the system, this property should be set.

As you can read above, by default there is no value for the mail.mime.charset and the file encoding (file.encoding property) is used.

For a specific e-mail

However, if you want to specify a specific encoding for a specific e-mail, then you should probably use the 2 parameter setSubject(subject,charset) and setText(text,charset) methods.

If that doesn't work, then probably your input is already corrupted before it reached this point. In other words, you probably used the wrong encoding to collect your data.

Mime types are complicated

The setContent(content, "UTF-8") (as other sources claim) will just not work. Just look at the signature of this method: setContent(Object content, String mimetype). Mime type and charset are 2 totally different things. Imho, you should really be using one of the setText(...) methods with a charset parameter.

But if you persist in using a mimetype to set the charset setContent(content,mimetype), then use the correct format. (not just "UTF-8", but something like "text/plain; charset=UTF-8"). But more importantly, be aware that every mime-type has its own way of handling charsets.

  • As specified in RFC-2046 the default charset for text/plain is US-ASCII, but can be overruled with an additional charset parameter.
  • However, in RFC-6657 makes clear that the text/xml type determines the charset using the content of the message. The charset parameter will just be ignored here.
  • And in RFC-2854 is stated that text/html should really always specify a charset. But if you don't, then it will use ISO-8859-1 (=Latin-1).

Solution 2

Maybe You should provide also UTF-8 here

mimeMessage.setContent(message, "text/plain; charset=UTF-8");

You have to look at http://www.coderanch.com/t/274480/java/java/JavaMail-set-content-utf

Solution 3

After spending a lot of time on debugging, and searching the internet for a clue, I have found a solution to my problem.

It seems that whenever I sended data through a web request, my application didn't encode the characters with UTF-8 encoding. This meant that the data which was send from my contact form, which contained æ, ø and å characters, couldn't be handled correct by the character encoding.

The solution seemed to setup a Character Encoding Filter, in my Deployment Descriptor, which would encode all incoming request from the web to be with the character encoding UTF-8.

private void registerCharacterEncodingFilter(ServletContext servletContext) {
    CharacterEncodingFilter encodingFilter = new CharacterEncodingFilter();
    encodingFilter.setEncoding("UTF-8");
    encodingFilter.setForceEncoding(true);
    FilterRegistration.Dynamic characterEncodingFilter = servletContext.addFilter("characterEncodingFilter", encodingFilter);
    characterEncodingFilter.addMappingForUrlPatterns(null, false, "/*");
}

This filter sets the encoding to be UTF-8 and force the encoding to all requests comming at the url ' /* '.

Solution 4

It's easy, run your project with parameter -Dfile.encoding=UTF-8 ex: java -Dfile.encoding=UTF-8 -jar MyProject.jar

//Fix a typo

Solution 5

Before sending your String to the send method, you must convert the String into UTF-8

If you are receiving a "request" parameter, you can use "setCharacterEncoding":

request.setCharacterEncoding("utf-8");
String subject = request.getParameter("subject");
String content = request.getParameter("content");
...
MimeMessage mineMessage = new MimeMessage(session);
        mineMessage.setFrom(new InternetAddress(myAccountEmail));
        mineMessage.setRecipient(Message.RecipientType.TO, new InternetAddress(recepient));
        mineMessage.setSubject(subject, "UTF-8");
        mineMessage.setContent(content, "text/plain;charset=UTF-8");

Otherwise, convert your String into UTF-8 format with the following method:

String subject = new String(subject.getBytes(Charset.forName("ISO-8859-1")), Charset.forName("UTF-8"));
String content = new String(content.getBytes(Charset.forName("ISO-8859-1")), Charset.forName("UTF-8"));
...
MimeMessage mineMessage = new MimeMessage(session);
    mineMessage.setFrom(new InternetAddress(myAccountEmail));
    mineMessage.setRecipient(Message.RecipientType.TO, new InternetAddress(recepient));
    mineMessage.setSubject(subject, "UTF-8");
    mineMessage.setContent(content, "plain/plain;charset=UTF-8");

This is the result in Spanish.

Share:
85,439
Rohwedder
Author by

Rohwedder

I am an enthusiastic person, who loves to develop. You can check out my public github account here

Updated on July 08, 2022

Comments

  • Rohwedder
    Rohwedder almost 2 years

    I have used Java Mail API, for sending emails. I am using a contact formular to send the input, which has to be send to a specific email.

    The email is send without problems, though I am a danish guy, and I am therefore in need of three danish characters which is 'æ', 'ø' and 'å', in the subject and the email text.

    I have therefore seen that I can use UTF-8 character encoding, to provide these characters, but when my mail is send I only see some strange letters - 'ã¦', 'ã¸' and 'ã¥' - instead of the danish letters - 'æ', 'ø' and 'å'.

    My method to send the email is looking like this:

    public void sendEmail(String name, String fromEmail, String subject, String message) throws AddressException, MessagingException, UnsupportedEncodingException, SendFailedException
    {
        //Set Mail properties
        Properties props = System.getProperties();
        props.setProperty("mail.smtp.starttls.enable", "true");
        props.setProperty("mail.smtp.host", "smtp.gmail.com");
        props.setProperty("mail.smtp.socketFactory.port", "465");
        props.setProperty("mail.smtp.socketFactory.class", "javax.net.ssl.SSLSocketFactory");
        props.setProperty("mail.smtp.auth", "true");
        props.setProperty("mail.smtp.port", "465");
        Session session = Session.getDefaultInstance(props, new javax.mail.Authenticator() {
            @Override
            protected PasswordAuthentication getPasswordAuthentication() {
                return new PasswordAuthentication("my_username", "my_password");
            }
        });
    
        //Create the email with variable input
        MimeMessage mimeMessage = new MimeMessage(session);
        mimeMessage.setHeader("Content-Type", "text/plain; charset=UTF-8");
        mimeMessage.setFrom(new InternetAddress(fromEmail, name));
        mimeMessage.setRecipient(Message.RecipientType.TO, new InternetAddress("my_email"));
        mimeMessage.setSubject(subject, "utf-8");
        mimeMessage.setContent(message, "text/plain");
    
        //Send the email
        Transport.send(mimeMessage);
    }
    

    Please help me find out how I can correct this 'error'.

    • Joop Eggen
      Joop Eggen about 11 years
      setText(message, "UTF"), so both for subject and content the encoding must be set.
    • Rohwedder
      Rohwedder about 11 years
      I did that and it didn't work. Though I get an error when sending email, when writing only UTF as the encoding as you suggest.
  • Rohwedder
    Rohwedder about 11 years
    Sorry I have tried a lot of things from your link inclusive your own 'solution', and it doesn't seem to work :(
  • bvdb
    bvdb over 9 years
    @Rohwedder, your filter may solve your specific problem. But it is not the answer to your initial question. Your question was about sending e-mails, not about handling web requests.
  • Airwavezx
    Airwavezx over 5 years
    Please fix your typo: -Dfile.ecoding=UTF-8 -> -Dfile.encoding=UTF-8
  • Amitk
    Amitk almost 4 years
    Very good explaination. when i faced the issue i changed this: message.setContent(body, "text/html"); to this: message.setContent(body, "text/html;charset=utf-8");
  • Đỗ Công Bằng
    Đỗ Công Bằng over 3 years
    Hello, does that mean the javax mail encodes the content (strings) in that charset before sending the mail? On the mail client, if we read the mail in a different encoding, it will not display correctly, isn't it?
  • bvdb
    bvdb over 3 years
    @ĐỗCôngBằng the mimetype will be sent along in the header of the e-mail. The receiving client then first extracts the mimetype from the header. That tells the client how to parse the message. But as mentioned in my answer, while the encoding can be specified in the mime-type, in some cases it will actually go through a number of more complex rules to finally determine the encoding. As soon as it knows the encoding it will then be able to parse the full message. All of which is the responsibility of your mail client.
  • Đỗ Công Bằng
    Đỗ Công Bằng over 3 years
    @bvdb I agree that mail client uses charset specified in the header. However, is the charset in header also the one used by Java mail to encode the content before sending? When I use setContent(text, "text/html"); I have the email on OUTLOOK with its content encoded in ISO-8859-1 but its header says that text/html; charset=UTF-8. It leads OUTLOOK to use UTF-8 to decode the mail, but it was encoded with ISO-8859-1, so I have bizarre characters. In com.sun.mail.handlers.text_plain.getCharset(String), us-ascii (ISO-8859-1) is used to encode the mail before sending if no charset is specified.