http://qs321.pair.com?node_id=207864


in reply to Re: Dealing with "Detachments"
in thread Dealing with "Detachments"

heh! I'm doing almost exactly the same thing. I tested this and it works for me:
use strict; use warnings; use MIME::Parser; ## my alias line: ## menu: \menu, "|/usr/perl/mime.parser.p" ## '\menu' keeps a copy in the inbox for account menu my $parser = new MIME::Parser; ## The secret here is that the directory must pre-exist ## and must be writable by the daemon that runs the ## parsing script. In my case user=daemon group=other ## I determined the correct values by initially making ## /tmp/mimemail using permissions 777. $parser->output_dir("/tmp/mimemail"); my $entity = $parser->read(\*STDIN) or die "\n\nCouldn't parse MIME stream\n\n";
For actual use I'd create the directory internally from the program and then remove it when finished. You'll also want to come up with some dynamic means of choosing the directory name since you don't want to try and delete the directory while another instance of the program is trying to write to it.

All you have to do now is figure out how to scarf the other portions of the original message using MIME::Parser before resending with MIME::Lite.

--Jim

Replies are listed 'Best First'.
Re: Dealing with "Detachments"
by hacker (Priest) on Oct 25, 2002 at 11:09 UTC
    For actual use I'd create the directory internally from the program and then remove it when finished. You'll also want to come up with some dynamic means of choosing the directory name since you don't want to try and delete the directory while another instance of the program is trying to write to it.

    I've got that figured out perfectly, in fact. I'm currently doing the following:

    use strict; # the usual suspects use Date::Manip; # date functions use Digest::MD5 qw(md5_hex); # convert date to md5 use File::Path; # mkpath/rmtree my $workpath = "/var/lib/pler"; # yes, pler =) my $date = UnixDate("today","%b %e, %Y at %T"); my $md5file = md5_hex($date); sub grok_data { # not the real name mkpath(["$workpath/$md5file"], 0, 0711); ... process data rmtree(["$workpath/$md5file"], 0, 1); }

    So far, this works flawlessly in another script that deals with the template as a file, but I'm converging the two separate scripts (and their functionality) into one, switchable by keys found inside the template.

    Thanks for the tips, I'll give this a try today.