in reply to Re^3: MIME::Parser parse_data
in thread MIME::Parser parse_data

The issue appears to be that this call: 
    my $tmpMessage = $parser->parse_data($body);

[download]
Is returning decoded strings for some emails but not for others. Some of the emails require the output of this call: 
       $tmp_part->bodyhandle->as_string;

[download]
to be decoded manually and others do not. I don't understand why sometimes this call 
     $tmp_part->bodyhandle->as_string;

[download]
Returns a human readable decoded string on some emails with base64 encoding but not on all emails with base64 encoding. This is a headache for me because if I change the code to just output the string it breaks on emails that need the string manually decoded. All I am doing is calling "parse_data" and then "bodyhandle->as_string". I'm not sure where the decoding process happens. The original data is definitely base64 encoded which I can see by looking at the raw email data.

Replies are listed 'Best First'.
Re^5: MIME::Parser parse_data
by boosth (Initiate) on Jan 17, 2013 at 23:15 UTC
    For reference sake I used this method: 
    
if($tmp_part->bodyhandle->as_string =~ m/^(?: [A-Za-z0-9+\/]{4} ) * (?
+:[A-Za-z0-9+\/]{2} [AEIMQUYcgkosw048] = | [A-Za-z0-9+\/] [AQgw] ==)?\
+z/x) {
                                                        $MessageBody =
+ " -  ". decode('UTF-8',decode_base64($tmp_part->bodyhandle->as_strin
+g));
                                                } else {
                                                        $MessageBody =
+ " -  ". $tmp_part->bodyhandle->as_string;
                                                }

    [download]
[reply]
[d/l]

In Section Seekers of Perl Wisdom