Skip Menu |

This queue is for tickets about the Test-Email CPAN distribution.

Report information
The Basics
Id: 48442
Status: resolved
Worked: 1 min
Priority: 0/
Queue: Test-Email

People
Owner: james [...] bitperfect.com
Requestors: akahl [...] iconmobile.com
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.04
Fixed in: (no value)



Subject: Reading from file descriptor and from array broken
Hi, this is my very first CPAN bug report. I'm using Test::Email to verify contents of a sent email received and saved aside locally via Net::Server::Mail::SMTP; since Test::Email is based on MIME::Entity which is in turn based on Mail::Internet to read the mail data, in theory and according to its manual it is possible to either pass in a file descriptor or a two-item array from which the mail header and body would get read. Trying to do so however I get: you cannot use body() to set the encoded contents at t/mail.t line 86 Which gets croak'ed from `sub body` in MIME::Entity which is indeed not designed to set the body; Mail::Internet however provides its own `sub body` which does not get called since Mime::Entity uses: my $self = $class->Mail::Internet::new(@_); in its constructor while Mail::Internet::new does: my $call = shift; (...) my $class = ref($call) || $call; my $self = bless {}, $class; so I guess MIME::Entity's methods have precedence where they shouldn't. I'm not sure whether this is really a bug for the maintainers of MIME::Entity or Mail::Internet but since the behavior gets triggered by Test::Email you have the honor to forward and/or work around this accordingly :) Additional Information ====================== $(uname -a): Linux XXX 2.6.29.4-167.fc11.x86_64 #1 SMP Wed May 27 17:27:08 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux (i.e. Fedora 11 x86_64) $(perl -v): This is perl, v5.10.0 built for x86_64-linux-thread-multi $(rpm -q --whatprovides perl\({Test::Email,MIME::Entity,Mail::Internet}\)): perl-Test-Email-0.04-2.fc11.noarch perl-MIME-tools-5.427-2.fc11.noarch perl-MailTools-2.04-2.fc11.noarch Thanks for any help.
As you say, this seems like a MIME::Entity issue. If you want some help with it, it would probably be best to communicate with either the MIME::Entity user group, or the maintainers of that module. Best of luck. James
Hi James, could you please move this report to the MIME::Entity queue? Thank you Alex
Show quoted text
> could you please move this report to the MIME::Entity queue?
How to do that is not immediately apparent to me. Please go ahead and submit another bug report, this time to MIME::Entity. It should be easy enough. Best, James
nothing more to see here...