Author |
|
rafaellop Newbie
Joined: 13 September 2007
Online Status: Offline Posts: 26
|
Posted: 07 February 2008 at 2:02am | IP Logged
|
|
|
Hello,
I've spent yesterday evening looking for a bug in my application that worked correctly with the previous version of POP3 client component implementation (not Mailbee). It would take less time if I only had the POP3 logging (Mailbee this time) feature working ok. Finally I had to write my own logger and I found the reason. It's been UID command related.
Previous POP3 component returned UIDs as:
The GetMessageUID() function from Mailbee component returns UIDs as
As you can see there is no message number. This was unexpected and took some time to find out. I can of course handle this by myself and add a message index from my code, but please consider a function that returns this as expected.
Another idea would be a function that could get a list of UIDs for all messages in the POP3 server at once, e.g. GetAllMessagesUID().
Cheers,
Rafal
|
Back to Top |
|
|
Andrew AfterLogic Support
Joined: 28 April 2006 Location: United States
Online Status: Offline Posts: 1189
|
Posted: 07 February 2008 at 2:56am | IP Logged
|
|
|
Quote:
As you can see there is no message number. This was unexpected and took some time to find out. I can of course handle this by myself and add a message index from my code, but please consider a function that returns this as expected. |
|
|
You can get message number for a certain UID via GetMessageNumberFromUID method and vise versa via GetMessageUID method.
Quote:
Another idea would be a function that could get a list of UIDs for all messages in the POP3 server at once, e.g. GetAllMessagesUID(). |
|
|
This already implemented in Search method.
Best regards,
Andrew
|
Back to Top |
|
|