Sample code for 30+ languages & platforms
Xbase++

Delete a Set of POP3 Messages by UIDL

See more POP3 Examples

Demonstrates the Chilkat MailMan.DeleteUidlSet method, which marks the POP3 messages whose UIDLs are listed in a StringTable for deletion. Chilkat processes the UIDL set and sends a DELE command for each located message. This example deletes two messages by UIDL.

Background: When you already know exactly which messages to remove — by their stable UIDLs — DeleteUidlSet deletes them all in one call without first downloading them. It is the efficient counterpart to fetching-then-deleting: for example, after processing messages elsewhere, hand back just their UIDLs to clear them. The deletions are committed when the POP3 session ends (unless ImmediateDelete is set).

Chilkat Xbase++ Downloads

Xbase++
LOCAL nSuccess
LOCAL oMailman
LOCAL oUidls

nSuccess := 0

//  Demonstrates the MailMan.DeleteUidlSet method, which marks the POP3 messages whose UIDLs
//  are listed in a StringTable for deletion.  Chilkat sends DELE for each located message.

oMailman := CreateObject("Chilkat.MailMan")

//  Configure the POP3 server connection.
oMailman:MailHost := "pop.example.com"
oMailman:MailPort := 995
oMailman:PopSsl := 1
oMailman:PopUsername := "user@example.com"
oMailman:PopPassword := "myPassword"

//  Build the set of UIDLs to delete.
oUidls := CreateObject("Chilkat.StringTable")
oUidls:Append("0000000123abcdef")
oUidls:Append("0000000124abcdef")

//  Mark the messages for deletion.

nSuccess := oMailman:DeleteUidlSet(oUidls)
IF (nSuccess == 0)
    ? oMailman:LastErrorText
    oMailman:destroy()
    oUidls:destroy()
    RETURN
ENDIF

//  Unless the ImmediateDelete property is set to 1, the messages are only marked for
//  deletion.  End the POP3 session (which sends the QUIT command) to commit the deletions.
nSuccess := oMailman:Pop3EndSession()
IF (nSuccess == 0)
    ? oMailman:LastErrorText
    oMailman:destroy()
    oUidls:destroy()
    RETURN
ENDIF

? "Deleted the UIDL set from the POP3 server."

//  Note: Explicitly connecting/authenticating is optional.  Chilkat MailMan automatically
//  connects and authenticates -- using the property settings above -- whenever a server
//  operation requires it.  Calling the explicit connect/authenticate methods can still be
//  helpful to determine whether a failure occurs while connecting or while authenticating.

oMailman:destroy()
oUidls:destroy()