javamail imap message content encoding

I'm trying to download mail from an imap server and I keep getting Unknown Encoding exceptions.  Here's the exception:

java.io.IOException: Unknown encoding: 7Bit;
      javax.mail.internet.MimePartDataSource.getInputStream(MimePartDataSource.java:108)
      com.sun.mail.handlers.text_plain.getContent(text_plain.java:90)
      javax.activation.DataSourceDataContentHandler.getContent(Unknown Source)
      javax.activation.DataHandler.getContent(Unknown Source)
      javax.mail.internet.MimeMessage.getContent(MimeMessage.java:1395)
      net.mainsequence.email.MailMessage.loadMessage(MailMessage.java:176)
      net.mainsequence.email.MailMessage.<init>(MailMessage.java:110)

Any ideas on how to fix this?
Object content = message.getContent();
			if(content instanceof String){
				mailContent = (String) content;
				textSegment = mailContent;
				htmlSegment = "";
			}else if(content instanceof InputStream){
				InputStream in = (InputStream) content;
				byte[] c = new byte[in.available()];
				in.read(c);
				String temp = new String(c);
				mailContent = temp;
				textSegment = mailContent;
				htmlSegment = "";
			}else if(content instanceof Multipart){
				Multipart multipart = (Multipart) message.getContent();	
				getMultiPart(multipart);
			}

Open in new window

csalem01Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

CEHJCommented:
Looks like you might have a malformed header with a stray or extra semicolon. You might need to catch the exception and extract the message to deal with it
0
Mick BarryJava DeveloperCommented:
encoding should be 7bit
0
CEHJCommented:
Encoding is not case sensitive
0
CompTIA Network+

Prepare for the CompTIA Network+ exam by learning how to troubleshoot, configure, and manage both wired and wireless networks.

csalem01Author Commented:
i caught the exception and printed the message to a file using the messages getrawinputstream function and it seems like all the messages that I'm having a problem with were caught as spam by spamassassin.  I don't see any problem with the headers though.  Looking through the error log though I see there's also an exception thrown for a message with content type "utf-8" and one message with content type "iso-8859-10".  I attached one of the messages that was throwing the exception with "7Bit", any ideas with what the problem with that message is?
269094365369276.txt
0
CEHJCommented:
The problem is exactly what i told you above. I've just saved some of my mails+headers to file 'ct' and run the following (note the absence of semicolons):
goose@seegobin:/tmp$ grep 'Content-Transfer-Encoding' ct
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
  h=Received:X-YMail-OSG:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding;
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: base64
goose@seegobin:/tmp$ 

Open in new window

0
Mick BarryJava DeveloperCommented:
transfer encoding is incorrect as I pointed out above :)
It should be "7bit", not "7bit;"
0
csalem01Author Commented:
Thanks alot, that worked.  I attached the code that made it work.  

I'm also getting errors with these content types (I attached the messages for each):

Content-Type: text/plain;
 charset="iso-8859-10"

Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: utf-8

Any ideas on how to fix these?
String xEncoding[] = message.getHeader("Content-Transfer-Encoding");
			if(xEncoding != null){
				if(xEncoding.length > 0){
					if(xEncoding[0].equalsIgnoreCase("7Bit;")){
						tempMessage = new MimeMessage((MimeMessage)message);
						tempMessage.removeHeader("Content-Transfer-Encoding");
						tempMessage.addHeader("Content-Transfer-Encoding", "7Bit");
					}
				}
			}

Open in new window

980348665832080.txt
318235670833124.txt
0
CEHJCommented:
Those charsets are relatively exotic. I certainly don't have support for ISO-8859-10 in my runtime, but do have support for KOI8-R in one runtime. Make sure you've selected full internationalization support on install.

You could probably ignore the mails that are either wrong or unsupported
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
csalem01Author Commented:
The problem with the KOI8-R mail is the "Content-Transfer-Encoding: utf-8".

"utf-8" isn't in the mime spec.  I guess I'll just have to ignore those mails.

thanks alot for your help
0
CEHJCommented:
:-)
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Protocols

From novice to tech pro — start learning today.