search

koodaamo / tnefparse

a TNEF decoding library written in python, without external dependencies
GNU Lesser General Public License v3.0
49 stars 37 forks source link

tnefparse utility issue #1

Closed lgwapnitsky closed 12 years ago

lgwapnitsky commented 12 years ago

tried running the tnefparse utility prior to including this in my own script, but am receiving the following errors:

[/home/lwapnitsky/git/tnefparse]% tnefparse (10:02 - 12-05-29) Traceback (most recent call last): File "/usr/local/bin/tnefparse", line 9, in load_entry_point('tnefparse==1.1', 'console_scripts', 'tnefparse')() File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 337, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2279, in load_entry_point return ep.load() File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 1989, in load entry = import(self.module_name, globals(),globals(), ['name']) ImportError: No module named tnef.cmdline

This was installed using python setup.py install using python 2.7 on Debian Wheezy

lgwapnitsky commented 12 years ago

even does this via pip install

lgwapnitsky commented 12 years ago

ahh...no tnef library....

lgwapnitsky commented 12 years ago

got it to work by pointing my project to the folder where tnef.py is, but now getting this:

pydev debugger: starting Wrong TNEF signature: 0x6d6f682f

when initializing my file as tnef.TNEF("winmaill.dat") with a valid file.

lgwapnitsky commented 12 years ago

fixed that(file read), but valid winmail.dat file shows no attachments. verified that this file DOES have attachments.

petri commented 12 years ago

thanks for reporting! There was a bug remaining in the entry point definition, from back when I refactored the pkg. It's now fixed in master, so invoking 'tnefparse' should no longer result in error.

I see that you then used the tnef.TNEF module directly and succeeded in reading your tnef file, but the code did not find your attachments. Can you please open a new issue for that?