ID: 10850
User Update by: [EMAIL PROTECTED]
Old-Status: Closed
Status: Open
Bug Type: IMAP related
Operating system: linux
PHP Version: 4.0.5
Description: imap_uid() does not produce an Unique ID Number from POP Servers

As far as I can see,

The following text for the manual says that there will be unique numbers, not numbers 
that change over time, and the only unique numbers that are available for a message is 
the UIDL number from the server,

>From the php manual:

This function returns the UID for the given message sequence number. An UID is an 
unique identifier that will not change over time while a message sequence number may 
change whenever the content of the mailbox changes. This function is the inverse of 
imap_msgno(). 

In other words, an UID is not a seq number that starts with 1, goes on with 2 3 4 5 6 
etc. etc. and then starts all over when the mailbox is empty...

Previous Comments:
---------------------------------------------------------------------------

[2001-05-14 13:19:37] [EMAIL PROTECTED]
uhhh... no, it shouldn't. Those are not UID's.

---------------------------------------------------------------------------

[2001-05-14 09:38:37] [EMAIL PROTECTED]
The following code should echo out the Unique ID's generated by UIDL on the IMAP/POP 
Server, but echo's out a sequencial number starting with 1 instead...

It should probably produce ID's like, 3afffb5300000001, 3afffb5300000002, etc. etc.


$mbox = imap_open ("{your.imap.host:143}", "username", "password");

$headers = imap_headers ($mbox);

if ($headers == true) {
    while (list ($key,$val) = each ($headers)) {
        echo imap_uid($mbox, $key);
    }
} else {
    echo "No messages in inbox";
}

---------------------------------------------------------------------------


Full Bug description available at: http://bugs.php.net/?id=10850


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to