ID: 12954
Updated by: joey
Reported By: [EMAIL PROTECTED]
Old Status: Open
Status: Bogus
Bug Type: IMAP related
Operating System: Windows NT 4, SP6
PHP Version: 4.0.6
New Comment:

I'm not sure what's going on in #7486, but if you look
in the documentation for the IMAP c-client library, you'll
see the following entry in bugs.txt:
No POP3 UID support

At least, that's the word up until imap-200a's c-client, which
is the latest I have been able to find...

Not a PHP bug.

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

[2001-08-24 21:48:21] [EMAIL PROTECTED]

This same bug was reported in bug#7486 and its current status is "Bogus", that's why 
I'm reporting this problem again.

Base on RFC1939 (Post Office Protocol - Version 3), a command UIDL can be used to 
retrieve the "unique-id".

According to RFC1939:
"The unique-id of a message is an arbitrary server-determined string, consisting of 
one to 70 characters in the range 0x21 to 0x7E, which uniquely identifies a message 
within a maildrop and which persists across sessions.  This
persistence is required even if a session ends without
entering the UPDATE state.  The server should never reuse an
unique-id in a given maildrop, for as long as the entity
using the unique-id exists."

Although UIDL is an optional command, most POP3 server do support it.  In fact most 
POP3 email clients expect it.

The unique id supplied by UIDL is  NOT a "Message-ID" in the message header.  In fact, 
"Message-ID" uniqueness can not always be guranteed.

Please do check into this again, because without imap_uid() funtioning properly, imap_ 
functionsí usefulness for POP3 are significantly limited.


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



Edit this bug report at http://bugs.php.net/?id=12954&edit=1


-- 
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