To see the content of the returned object try this code:
$stream = imap_open($server, $username, $password);
$header = imap_fetchheader($stream, $uid, FT_UID);
$obj = imap_rfc822_parse_headers( $header);
print "<html><head></head><body><pre>\n";
print_r($obj);
print "</pre></body></html>";
imap_close($stream);
imap_rfc822_parse_headers
Description
object imap_rfc822_parse_headers ( string headers [, string defaulthost] )This function returns an object of various header elements, similar to imap_header(), except without the flags and other elements that come from the IMAP server.
add a note
User Contributed Notes
Oliver
16-Apr-2006 08:50
16-Apr-2006 08:50
Kevin Casper <casperke at gmail dot com>
02-Feb-2005 02:23
02-Feb-2005 02:23
I was lightly probing this function's behavoir.
It handles rfc882 fields:
date
subject
message_id
to
from
reply-to
sender - will generate using 'from' field if not in
header
references
in-reply-to
cc
doesn't handle rfc882 fields:
return-path
received
resent- I think this field may be obsolete
keywords
If there are other rfc822 fields or behavoirs for the function, then I can't speak of them as they weren't in my test.
As it is relevent to what I'm currently doing I may add more about this function from time to time.
jh at junetz dot de
14-Sep-2004 11:22
14-Sep-2004 11:22
But what you /will/ get is a complete To field, i.e. unfolded as specified for long header fields in RFC 822. So if you want to replace imap_headerinfo() by this function, you can run it on imap_fetchheader().
Sven dot Dickert at planb dot de
22-May-2002 07:28
22-May-2002 07:28
The object you get from imap_rfc822_parse_headers differs from the object you get from imap_headerinfo/imap_header in the following points. You won't get the:
* flags
* msgno
* size
* Maildate
* udate
* fetchfrom
* fetchsubject
udate can be simulated with
$headerobj=imap_rfc822_parse_headers ($header);
$udate=strtotime($headerobj->date);