Rust

Delete a Set of POP3 Messages by UIDL

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 Rust Downloads

Download Chilkat for Rust

Rust


// 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.

let mailman = chilkat::MailMan::new();

// Configure the POP3 server connection.
mailman.set_mail_host("pop.example.com");
mailman.set_mail_port(995);
mailman.set_pop_ssl(true);
mailman.set_pop_username("user@example.com");
mailman.set_pop_password("myPassword");

// Build the set of UIDLs to delete.
let uidls = chilkat::StringTable::new();
let _ = uidls.append("0000000123abcdef");
let _ = uidls.append("0000000124abcdef");

// Mark the messages for deletion.

if mailman.delete_uidl_set(&uidls).is_err() {
    println!("{}", mailman.last_error_text());
    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.
if mailman.pop3_end_session().is_err() {
    println!("{}", mailman.last_error_text());
    return;
}

println!("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.