Swift
Swift
Delete a Bundle of POP3 Messages
See more POP3 Examples
Demonstrates the Chilkat MailMan.DeleteBundle method, which deletes POP3 messages using the UIDLs stored in the X-UIDL headers of the Email objects in an EmailBundle. An email without an X-UIDL header is skipped. This example fetches all messages and deletes them.
Background:
DeleteBundle is the batch version of DeleteEmail: it marks every message in a downloaded bundle for deletion in one call. A typical "download and clear the mailbox" workflow is to fetch all messages, process them, then delete the whole bundle. Because a bundle can be filtered or built selectively, you can also delete just the subset you no longer need. The deletions commit when the POP3 session ends.Chilkat Swift Downloads
func chilkatTest() {
var success: Bool = false
// Demonstrates the MailMan.DeleteBundle method, which deletes POP3 messages using the UIDLs
// stored in the X-UIDL headers of the Email objects in an EmailBundle. An email without an
// X-UIDL header is skipped.
let mailman = CkoMailMan()!
// Configure the POP3 server connection.
mailman.mailHost = "pop.example.com"
mailman.mailPort = 995
mailman.popSsl = true
mailman.popUsername = "user@example.com"
mailman.popPassword = "myPassword"
// Fetch all messages (headers are enough; each carries an X-UIDL header).
let bundle = CkoEmailBundle()!
success = mailman.fetchAll(keepOnServer: true, headersOnly: true, numBodyLines: 0, bundle: bundle)
if success == false {
print("\(mailman.lastErrorText!)")
return
}
// Delete every message in the bundle.
success = mailman.deleteBundle(bundle: bundle)
if success == false {
print("\(mailman.lastErrorText!)")
return
}
// Unless the ImmediateDelete property is set to true, the messages are only marked for
// deletion. End the POP3 session (which sends the QUIT command) to commit the deletions.
success = mailman.pop3EndSession()
if success == false {
print("\(mailman.lastErrorText!)")
return
}
print("Deleted \(bundle.messageCount.intValue) messages 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.
}