Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Email-MIME-Attachment-Stripper CPAN distribution.

Report information
The Basics
Id: 13867
Status: resolved
Priority: 0/
Queue: Email-MIME-Attachment-Stripper

People
Owner: Nobody in particular
Requestors: tallison [...] tacocat.net
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 1.3
Fixed in: (no value)



Subject: Unable to get body for parsed message from attached email
Error reports from the following code where $mail_as_string is the included file. my $mail_as_mime = Email::MIME->new($mail_as_string); print $mail_as_mime->body,"\n"; my $stripper = Email::MIME::Attachment::Stripper->new ($mail_as_mime, 'force_filename' => 1); print $stripper->message->header('Subject'),"\n"; Error on last line above appears as follows: Can't call method "body" on an undefined value at /usr/share/perl5/Email/MIME/Modifier.pm line 244 (#1) (F) You used the syntax of a method call, but the slot filled by the object reference or package name contains an undefined value. Something like this will reproduce the error: $BADREF = undef; process $BADREF 1,2,3; $BADREF->process(1,2,3); Uncaught exception from user code: Can't call method "body" on an undefined value at /usr/share/perl5/Email/MIME/Modifier.pm line 244. Email::MIME::parts_set('Email::MIME=HASH(0x8b37db0)', 'ARRAY(0x8925ca4)') called at /usr/share/perl5/Email/MIME/Attachment/Stripper.pm line 114 Email::MIME::Attachment::Stripper::_detach_all('Email::MIME::Attachment::Stripper=HASH(0x89e521c)') called at /usr/share/perl5/Email/MIME/Attachment/St ripper.pm line 88 Email::MIME::Attachment::Stripper::message('Email::MIME::Attachment::Stripper=HASH(0x89e521c)') called at bin/imap.t line 62 1..12 # Looks like your test died just after 12.
Download DANG.eml
message/rfc822 733.3k

Message body is not shown because it is too large.

From: tallson [...] tacocat.net
[guest - Mon Jul 25 22:00:38 2005]: This error applies to VERSION 1.31. It was erroneously reported as VERSION 1.3
I cannot reproduce this with the latest versions. -- rjbs