Get parameters info from imap_fetchstructure

[The_Chancer]

Can anyone help to explain about the parameters info given from imap_fetchstructure.. ??

I have this...

$struct=imap_fetch_structure($this->stream,$this->msg_uid, FT_UID);

Which gives me the structure of the message...

The structure comes out as

type 1
encoding 0
subtype MIXED
description
id
lines
bytes
disposition
ifdparameters 0
dparameters
dparameters=>filename
dparameters=>value
parameters 0
parts 25

OK - all parts are attachments...

So we need to look in the parameters Object to find the info to "see" the attached files...

So $struct->parts[1]->parameters gives OBJECT

Each object is made up of an Attribute and a value..

So $struct->parts[1]->parameters->attribute or $struct->parts[1]->parameters->value should give something - but they dont...

What am I missing ???

Do I have to refer to each part of the parameter as parameter[$x] ?? (I have tried but it doesn't seem to work....)

Any help / ideas ??

Thanks,

[The_Chancer]

How silly...

Just use

$struct->parts[$i]->dparameter[0]->value.....

(For one method anyway) As the mail was sent with each part as an attachment within its own part. Look for the disposition variable $struct->disposition for the main part, or $struct->parts[$i]->disposition for recursive ones and it is all there.

To get a full look at the mail look at imap_body($stream,$msg_uid,FT_UID) which gives all the message as plain text, including boundaries from which you should be able to pick up what to do...

[Wien]

why parts[1] ? ?

but anyway parameter is an arrays of objects

Have you tried $struct->parameter[$i]->value

and $struct->parameter[$i]->attribute

[The_Chancer]

I was just using parts[1] as an example...

I actually have

if ($struct->type == 1) //mulktipart message
		{
			while(list($index, $sub_structure) = each($struct->parts)) 
			{ 
				for($i=0; $i< count($struct->parts); $i++) {
					$prefix=$i.".";
					if ($prefix.$index==$i.".0"){$number=$i;}else{$number=$i.".".$index;}
					echo "number $number Encoding ".$struct->parts[$number]->encoding." Subtype ".$struct->parts[$number]->subtype." Disposition ".$struct->parts[$number]->disposition." Name ".$struct->parts[$number]->dparameters[0]->value."<br>";
					if ($struct->parts[$number]->encoding ==3) {
						if (strtolower($struct->parts[$number]->subtype) != 'html' || strtolower($struct->parts[$number]->subtype) != 'plain' || strtolower($struct->parts[$number]->subtype) != 'alternative')
						{
							if ($struct->parts[$number]->ifdisposition)
							{
								//attachment type
								for($z=0; $z< count($struct->parts[$number]->dparameters); $z++) {
									if (strtolower($struct->parts[$number]->dparameters[$z]->attribute) == "filename"){
										$filename[$number]= $this->decodeHeader($struct->parts[$number]->dparameters[$z]->value);
										break;

								}
							}

						}
					}
			   		$arr["body"] = imap_base64(imap_fetchbody($this->stream, $this->msg_uid, $number, FT_UID));
			   		if(strtolower($struct->parts[$number]->subtype) == 'html') $html = 1;
			   	}

Which would have seemed a lot more complicated to explain...

In this example, the normal parameters array is empty, as it is all done through the content-disposition, so I was using the dparameters array of objects to get the same result.

I am still waiting on getting a full torture test going so I can test all the different MIME types and email sending types... (what a minefield)..