|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
|
|
Feature request - TNEF parsingHeya,
how can setup balsa so it can parse incoming emails with attached winmail.dat (TNEF) ? With parsing I mean in GUI Message Parts display tree. I do have ytnef installed. Currently I have to save winmail.dat attachment and run it through -> Example: ytnef -v winmail.dat Parse with verbose output, don't save ytnef -f . winmail.dat Parse and save all attachments to local directory (.) TIA, -- T-Com Odjel za upravljanje mrežom i uslužnim platformama / / Network and Service Platform Operations Department. Mario Mikočević Draškovićeva 26, Zagreb, 10000 +385 1 4913 800 +385 1 4913 860 (fax) +385 98 470 801 (GSM) mario dot mikocevic at t-com dot hr http://www.t-com.hr _______________________________________________ balsa-list mailing list balsa-list@... http://mail.gnome.org/mailman/listinfo/balsa-list |
|
|
Re: Feature request - TNEF parsingHey Mario:
On 10/19/2009 05:54:07 AM Mon, Mario Mikocevic wrote: > Heya, > > how can setup balsa so it can parse incoming emails with attached > winmail.dat (TNEF) ? > > With parsing I mean in GUI Message Parts display tree. > I do have ytnef installed. > > Currently I have to save winmail.dat attachment and run it through -> > > Example: > ytnef -v winmail.dat > Parse with verbose output, don't save > ytnef -f . winmail.dat > Parse and save all attachments to local directory (.) appears to do what you want (except that it hard-codes an incorrect path to the ytnef executable). Some Debian notes suggested that adding #################################################################### # TNEF Attachments :0 * ^X-MS-TNEF-Correlator { :0 fw B * winmail.dat |/usr/bin/ytnefprocess.pl } to your .procmailrc would call it when necessary, but that's pure guesswork on my part--procmail rules are totally inscrutable to me :( I'm waiting for a TNEF attachment to test it... Best, Peter _______________________________________________ balsa-list mailing list balsa-list@... http://mail.gnome.org/mailman/listinfo/balsa-list |
|
|
Re: Feature request - TNEF parsingOn 10/20/2009 06:01:17 PM Tue, Peter Bloomfield wrote:
> Hey Mario: > > On 10/19/2009 05:54:07 AM Mon, Mario Mikocevic wrote: >> Heya, >> >> how can setup balsa so it can parse incoming emails with attached >> winmail.dat (TNEF) ? [ snip ] > The f11 ytnef package contains a Perl filter, ytnefprocess.pl, which > appears to do what you want (except that it hard-codes an incorrect path > to the ytnef executable). Some Debian notes suggested that adding > > #################################################################### > # TNEF Attachments > :0 > * ^X-MS-TNEF-Correlator > { > :0 fw B > * winmail.dat > |/usr/bin/ytnefprocess.pl > } > > to your .procmailrc would call it when necessary ytnefprocess.pl > some-file, I can add some-file as an mbox and the message has the contents of the TNEF part added as extra MIME parts. But that procmail rule doesn't do anything :( Help, anyone? Peter _______________________________________________ balsa-list mailing list balsa-list@... http://mail.gnome.org/mailman/listinfo/balsa-list |
|
|
Re: Feature request - TNEF parsingOn 10/21/2009 03:01:07 PM, Peter Bloomfield wrote:
>> #################################################################### >> # TNEF Attachments >> :0 >> * ^X-MS-TNEF-Correlator >> { >> :0 fw B >> * winmail.dat >> |/usr/bin/ytnefprocess.pl >> } >> >> to your .procmailrc would call it when necessary > > Well, no, that doesn't seem to work. If I pipe a message through > ytnefprocess.pl > some-file, I can add some-file as an mbox and the > message has the contents of the TNEF part added as extra MIME parts. > But that procmail rule doesn't do anything :( The recipe above runs ytnefprocess.pl as a filter for every message provided that it has X-MS-TNEF-Correlator header and its body contains winmail.dat string. The exit result of yynefprocess.pl is checked and the message is discarded if the message is nonzero. I am not familiar with ypnetprocess.pl - maybe it returns non-zero exit result? The ytnef documentation (/usr/share/doc/ytnef-2.6/README) suggest to use a basically identical rule: If you want to use ytnefprocess.pl, then make sure to do the following: 1) Make a directory ~/.ytnef 2) Make a directory ~/.ytnef/output 3) Install the MIME::Parser perl module. You can do this with: perl -MCPAN -e shell (let it load) install MIME::Parser 4) Copy ytnefprocess.pl & ytnef to a place like /usr/bin. 5) Create a .procmailrc something like this: PATH=/bin:/usr/bin :0fw * > 0 | /usr/bin/ytnefprocess.pl _______________________________________________ balsa-list mailing list balsa-list@... http://mail.gnome.org/mailman/listinfo/balsa-list |
|
|
Re: Feature request - TNEF parsingOn Oct 21, 2009, at 12:22 PM, Pawel Salek wrote:
[ snip ] > The recipe above runs ytnefprocess.pl as a filter for every message > provided that it has X-MS-TNEF-Correlator header and its body contains > winmail.dat string. The exit result of yynefprocess.pl is checked and > the message is discarded if the message is nonzero. Ahhh...so it matches only if the X-MS-TNEF-Correlator header is among the *top-level* headers--I was testing it with some old mail that I forwarded to myself, and it was an *embedded* header. Actually, looking for "winmail.dat" isn't really relevant, since using that file-name isn't required. We should really check for an "application/ms-tnef" mime part, so something like this is probably better: #################################################################### # TNEF Attachments :0 fw B * ^Content-Type:[ \t]*application/ms-tnef; |/usr/bin/ytnefprocess.pl or if we wanted to avoid scanning every message body and we wanted to decode the part only when the original sender is the TNEF-Correlator, perhaps #################################################################### # TNEF Attachments :0 * ^X-MS-TNEF-Correlator { :0 fw B * ^Content-Type:[ \t]*application/ms-tnef; |/usr/bin/ytnefprocess.pl } Thanks! Peter _______________________________________________ balsa-list mailing list balsa-list@... http://mail.gnome.org/mailman/listinfo/balsa-list |
| Free embeddable forum powered by Nabble | Forum Help |