NikhilMIT2013 / java-libpst

Automatically exported from code.google.com/p/java-libpst
0 stars 0 forks source link

Attachment is empty - error #38

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.Extract individual mails from pst. 
2.Few emails throw error as- attachment is empty
3.Find that pst that those emails and attachment. 

One of the possible scenario where it throws error is when email has 0KB file 
and it thinks that attachment is not present. 

But in some email attachment is present, it is throwing error. 

Error stack trace: 
com.pff.PSTException: Attachment is empty!
    at com.pff.PSTAttachment.getFileInputStream(PSTAttachment.java:88)

PST file location: 
http://edrm.net/resources/data-sets/enron-data-set-files
EDRM-Enron-PST-001.zip -> benjamin_rogers_000.pst

Description Node ID of the mail which gives exception: 2130532

Original issue reported on code.google.com by manish.b...@gmail.com on 31 Mar 2011 at 12:09

GoogleCodeExporter commented 8 years ago

Original comment by rjohnson...@gmail.com on 31 Mar 2011 at 9:01

GoogleCodeExporter commented 8 years ago
Hmm, just tried this with the code currently in SVN and it appeared to extract 
the attachment for 2130532 (Coal Presentation 11.3.00.ppt).

Have you tried with the code from SVN?

Original comment by rjohnson...@gmail.com on 31 Mar 2011 at 9:54

GoogleCodeExporter commented 8 years ago
We were getting the error while doing the parsing of it. 
We did use the svn project. 

May be i gave you the wrong description id. Did the pst did not throw error at 
all?

Original comment by manish.b...@gmail.com on 1 Apr 2011 at 1:35

GoogleCodeExporter commented 8 years ago
nope, but I did only try that ID.  I'll try going through the whole thing and 
seeing if that throws anything up.

Original comment by rjohnson...@gmail.com on 1 Apr 2011 at 12:49

GoogleCodeExporter commented 8 years ago
okay, went through the whole file this time and came across a couple of empty 
attachments.  Fixes in SVN (please test!).

Sheesh he had some questionable stuff in his email...

Original comment by rjohnson...@gmail.com on 2 Apr 2011 at 12:25