Sample code for 30+ languages & platforms
SQL Server

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 SQL Server Downloads

SQL Server
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    --  Demonstrates the MailMan.ClearPop3SessionLog method, which clears the current contents of
    --  the Pop3SessionLog property.

    DECLARE @mailman int
    EXEC @hr = sp_OACreate 'Chilkat.MailMan', @mailman OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    --  Configure the POP3 server connection.
    EXEC sp_OASetProperty @mailman, 'MailHost', 'pop.example.com'
    EXEC sp_OASetProperty @mailman, 'MailPort', 995
    EXEC sp_OASetProperty @mailman, 'PopSsl', 1
    EXEC sp_OASetProperty @mailman, 'PopUsername', 'user@example.com'
    EXEC sp_OASetProperty @mailman, 'PopPassword', 'myPassword'

    --  Perform a POP3 operation, which populates the session log.
    DECLARE @count int
    EXEC sp_OAMethod @mailman, 'GetMailboxCount', @count OUT

    PRINT 'Mailbox count: ' + @count

    --  Clear the POP3 session log (for example, before the next operation).
    EXEC sp_OAMethod @mailman, 'ClearPop3SessionLog', NULL


    PRINT '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.

    EXEC @hr = sp_OADestroy @mailman


END
GO