Android™
Android™
Clear the POP3 Session Log
See more POP3 Examples
Demonstrates the Chilkat MailMan.ClearPop3SessionLog method, which clears the current contents of the Pop3SessionLog property. This example performs a POP3 operation (which populates the log) and then clears it.
Background: The
Pop3SessionLog accumulates the raw protocol conversation — the commands Chilkat sent and the server's replies — which is invaluable for diagnosing connection or authentication problems. When performing many operations on one MailMan object, the log grows continuously; ClearPop3SessionLog resets it so you can capture just the exchange for the next operation.Chilkat Android™ Downloads
// Important: Don't forget to include the call to System.loadLibrary
// as shown at the bottom of this code sample.
package com.test;
import android.app.Activity;
import com.chilkatsoft.*;
import android.widget.TextView;
import android.os.Bundle;
public class SimpleActivity extends Activity {
private static final String TAG = "Chilkat";
// Called when the activity is first created.
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
// Demonstrates the MailMan.ClearPop3SessionLog method, which clears the current contents of
// the Pop3SessionLog property.
CkMailMan mailman = new CkMailMan();
// Configure the POP3 server connection.
mailman.put_MailHost("pop.example.com");
mailman.put_MailPort(995);
mailman.put_PopSsl(true);
mailman.put_PopUsername("user@example.com");
mailman.put_PopPassword("myPassword");
// Perform a POP3 operation, which populates the session log.
int count = mailman.GetMailboxCount();
Log.i(TAG, "Mailbox count: " + String.valueOf(count));
// Clear the POP3 session log (for example, before the next operation).
mailman.ClearPop3SessionLog();
Log.i(TAG, "POP3 session log cleared.");
// 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.
}
static {
System.loadLibrary("chilkat");
// Note: If the incorrect library name is passed to System.loadLibrary,
// then you will see the following error message at application startup:
//"The application <your-application-name> has stopped unexpectedly. Please try again."
}
}