As Davide said, those numbers are only valid for the specific POP3 session that you received them in. Future sessions are not guaranteed to have the same numbers for the same messages.
You should use the UIDL numbers. Retrieve them as: +OK Maildrop has 4 messages (12788 bytes) UIDL +OK 4 1 1028745740408.1556.karen 2 1062432866368.1924.karen 3 1062433302173.1404.karen 4 1067127927549.1956.karen These numbers (1028745740408.1556.karen) are guaranteed not to change between sessions. At 17:48 3/30/2005, Dustin C. Hatch wrote: >Okay, I guess I should clarify what I mean by message ID numbers. PHP >downloads the messages over POP3 as you would using telnet. The message >IDs that it uses are just like you would using the command line to read mail: > >LIST >+OK 15 70871 >1 5427 >2 1826 >3 16834 >4 4043 >5 3875 >6 2373 >7 15345 >8 1642 >9 3229 >10 2662 >11 3882 >12 3052 >13 3524 >14 1382 >15 1775 > >The problem is that these IDs do not stay the same if new mail arrives. I >may be able to re-write the program to use the "Message-ID: " header, if >this is unchangeable. If someone has a better suggestion, let me know. > >Dustin C. Hatch >http://www.dchweb.com > > > On Wed, 30 Mar 2005, Dustin C. Hatch wrote: > > > > > > > > I recently developed a webmail client for POP3/POP3S so that I could use > > > native XMail support and webmail. The way the inbox is designed, > > > messages are released in reverse order of their MTA assigned ID number, > > > ie 1 is on the bottom, 2 next, a googol on the top, etc. This worked > > > fine for a while, until I started getting many messages in my inbox. > > > Then I started noticing that the messages were no longer arranged in > > > order of their dates. I thought it was no big deal and just modified the > > > code to sort the messages by date after converting them to a UNIX > > > timestamp, etc. This worked for a while. The problem further complicated > > > itself one day while I was reading a message, and, for a reason I now > > > have forgotten, I refrehed the page, and the email changed! A new > > > message > > > had arrived while I was reading and had taken over the old message's ID > > > number. This forced the message I was reading, and all subsequent > > > messages, to increment their IDs. > > > > > > I was wondering if this is a flaw in XMail, or if that is the way all > > > MTAs work. I have never used anything else, so I don't know if others > > > just generate seemingly random IDs for incoming messages. If it is a > > > flaw, can it be fixed? Because my client fully relies on the message ID > > > number for all functions, like deletion, forwarding, and replying, I > > > need to have messages have constant ID numbers. > > > > You are aware that POP3 server are not guaranteed to preserve message IDs > > across session, yes? That's why UIDL have been added to the protocol, and > > XMail supports it. > > > > > > > > - Davide > > > > - > > To unsubscribe from this list: send the line "unsubscribe xmail" in > > the body of a message to [EMAIL PROTECTED] > > For general help: send the line "help" in the body of a message to > > [EMAIL PROTECTED] > > > > >- >To unsubscribe from this list: send the line "unsubscribe xmail" in >the body of a message to [EMAIL PROTECTED] >For general help: send the line "help" in the body of a message to >[EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
