Java
Chilkat2 Java
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 Java Downloads
import com.chilkatsoft.chilkat2.ChilkatException;
import com.chilkatsoft.chilkat2.EmailBundle;
import com.chilkatsoft.chilkat2.MailMan;
public class ChilkatExample {
public static void main(String[] args) {
// 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.
MailMan mailman = new MailMan();
// Configure the POP3 server connection.
mailman.setMailHost("pop.example.com");
mailman.setMailPort(995);
mailman.setPopSsl(true);
mailman.setPopUsername("user@example.com");
mailman.setPopPassword("myPassword");
// Fetch all messages (headers are enough; each carries an X-UIDL header).
EmailBundle bundle = new EmailBundle();
try {
mailman.fetchAll(true, true, 0, bundle);
// Delete every message in the bundle.
mailman.deleteBundle(bundle);
// 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.
mailman.pop3EndSession();
} catch (ChilkatException e) {
System.out.println(e.getLastErrorText());
return;
}
System.out.println("Deleted " + bundle.getMessageCount() + " 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.
}
}