Objective-C
Objective-C
Fetch One POP3 Message by UIDL
See more POP3 Examples
Demonstrates the Chilkat MailMan.FetchByUidl method, which retrieves one message by UIDL and stores it in an Email object. The arguments are the UIDL, headerOnly, numBodyLines, and the Email. The message remains on the POP3 server. This example fetches a specific message by its UIDL.
Background: Because a UIDL is stable across sessions, fetching by UIDL is the reliable way to retrieve exactly the message you mean — the foundation of "leave on server" clients that remember which UIDLs they've already processed and download only the new ones. You can obtain the mailbox's UIDLs from
FetchUidls or GetMailboxInfoXml.Chilkat Objective-C Downloads
#import <CkoMailMan.h>
#import <CkoEmail.h>
BOOL success = NO;
// Demonstrates the MailMan.FetchByUidl method, which retrieves one message by UIDL and
// stores it in an Email object. The arguments are the UIDL, headerOnly, numBodyLines, and
// the Email. The message remains on the server.
CkoMailMan *mailman = [[CkoMailMan alloc] init];
// Configure the POP3 server connection.
mailman.MailHost = @"pop.example.com";
mailman.MailPort = [NSNumber numberWithInt:995];
mailman.PopSsl = YES;
mailman.PopUsername = @"user@example.com";
mailman.PopPassword = @"myPassword";
// Fetch a specific message by UIDL in full. headerOnly=ckfalse (fetch the entire message).
// Note: numBodyLines only applies when headersOnly is true (it sets how many lines of the
// body to include along with the headers). When headersOnly is false, the entire message
// is fetched and numBodyLines is ignored.
CkoEmail *email = [[CkoEmail alloc] init];
success = [mailman FetchByUidl: @"0000000123abcdef" headerOnly: NO numBodyLines: [NSNumber numberWithInt: 0] email: email];
if (success == NO) {
NSLog(@"%@",mailman.LastErrorText);
return;
}
NSLog(@"%@%@",@"Subject: ",email.Subject);
// 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.