[RESOLVED] Retrieved and displayed information different

mittra

I'm using Zend\Mail to retrieve email from my gmail account and process it.

I need some basic info from the email, including, but not limited to, name and email address. For testing purposes, I created a basic script that pulls the email and reads it and displays the results on the screen. For troubleshooting and testing purposes, I am running that basic script through Runscope so I can see errors better and have a better idea of what the script is seeing/reading.

I'm finding that what it displays (using echo or print) is different than what Runscope shows it's getting.

I suppose I can live with that if you could help me strip what's actually getting pulled down to its essentials.

So here's the basic script (private/personal information has been stripped/modified for the forum, of course)

<?php
	$nummsgs = 0;

require('../include/zf2/autoload.php');

$zmail_config = array('host' => 'imap.gmail.com',
					  'port' => 993,
					  'ssl' => 'ssl',
					  'user' => 'support@[gmail account].com',
					  'password' => 'password');

$zmail = new Zend\Mail\Storage\Imap($zmail_config);

$nummsgs = $zmail->countMessages();

if ($nummsgs == 1)
	print "Found " . $nummsgs . " message. \n";
else
	print "Found " . $nummsgs . " messages. \n";


for($i = $nummsgs; $i > 0; $i--) { //process messages in reverse.
	if($mailmsg = $zmail->getMessage($i)) print "Message ".$i." retrieved. \n";
		$headerinfo = $mailmsg->getHeaders();

		$from = $mailmsg->from;
		$name = $mailmsg->getHeaderField('From', 'name');
		$email = $mailmsg->getHeaderField('From', 'email');

		echo '<pre>';
		echo "\$from: ".$from." \n";
		echo "\$name: ".$name." \n";
		echo "\$email: ".$email." \n";
		print_r($mailmsg);
		echo '</pre>';

} //end message processing

?>

Nothing too fancy, right?

(continued in the next post due to length restrictions)

mittra

Here's what it displays on the screen (due to length, I'm removing unrelated fields):

Found 1 message. Message 1 retrieved.
$from: John Smith

$name:

$email:

Zend\Mail\Storage\Message Object
(
[flags:protected] => Array
(
)

)

(continued in the next post due to thread length restrictions)

mittra

And this is what Runscope shows was actually retrieved:

Found 1 message.
Message 1 retrieved.

<pre>$from: John Smith
<jsmith@live.com>
$name:

$email:

Zend\Mail\Storage\Message Object
(
[flags:protected] => Array
(
)

[removed for length]
)

      </pre>

Obviously, $name = $mailmsg->getHeaderField('From', 'name'); doesn't work (I used something similar for retrieving the charset elsewhere and hoped it would work). So what I need to do is remove all of the spaces, the < and >, and then the other alpha-numeric characters from the "from" field to isolate just the sender's name and email addresses separately, i.e., where it says "John Smith <jsmith@live.com>" I need to be able to isolate it to "John Smith" and "jsmith@live.com" for the Name and Email respectively.

I can't use simply trim(), rtrim(), or ltrim(), right (because the name and email addresses themselves aren't special characters)?

johanafm

Assuming things are as simple as "from header field value containing zero or one occurences of <" you could easily distinguish between the two cases. Using [man]explode[/man] on '<'.
Case 1. Without <, the result is the email address.
Case 2. With <, you now have two parts
- The first containing phrase content (i.e. a name), possibly containing trailing WS. Use trim
- The second containing an address along with a trailing >. Remove the trailing >, for example using rtrim($address_part, '>') and you're done.

This may or may not be enough for your particular purposes. When it comes to email, you always have to go look at the RFCs to find out what things actually may look like. If you don't, your application may receive valid values that it cannot handle properly.

RFC822 seems to define things so that what you call the "name" part allows the < character. Moreover, this also seems to be allowed for the local part of what you call "email address". In practice, you are probably unlikely to encounter these problems.

The header field value may also be folded. Folding is breaking up the header field value on multiple lines with a CRLF character and the next line starting with at least one LWSP (space or htab) character followed by the rest of the header field value. Folding is allowed anywhere linear white space is allowed (including inside quoted-string). Straight from RFC 822

To:  "Joe & J. Harvey" <ddd @Org>, JJV @ BBN

    can be represented as:

To:  "Joe & J. Harvey" <ddd @ Org>,
                    JJV@BBN

    and

To:  "Joe & J. Harvey"
                            <ddd@ Org>, JJV
             @BBN

    and

To:  "Joe &
             J. Harvey" <ddd @ Org>, JJV @ BBN

mittra

I've modified the script to use explode and for the moment everything appears to be functioning properly.

Your assistance is greatly appreciated. Hopefully this thing works now.