(SQL Server) Verify Email Recipients

A way to possibly determine valid/invalid email addresses. I would recommend being very careful about doing this because your IP address may be flagged as a potential spammer by the mail server (because you are probing for valid/invalid email addresses). This Chilkat functionality existed for many years, before this kind of activity became a problem. The functionality remains only because it is useful for some to test with their own SMTP servers.

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @iTmp0 int
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    -- This example requires the Chilkat API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

    DECLARE @mailman int
    -- Use "Chilkat_9_5_0.MailMan" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.MailMan', @mailman OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    -- SMTP connection settings...
    EXEC sp_OASetProperty @mailman, 'SmtpHost', 'smtp.example.com'
    EXEC sp_OASetProperty @mailman, 'SmtpUsername', 'MY_SMTP_USERNAME'
    EXEC sp_OASetProperty @mailman, 'SmtpPassword', 'MY_SMTP_PASSWORD'
    EXEC sp_OASetProperty @mailman, 'SmtpSsl', 1
    EXEC sp_OASetProperty @mailman, 'SmtpPort', 465

    -- Create a new email object
    DECLARE @email int
    -- Use "Chilkat_9_5_0.Email" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.Email', @email OUT

    EXEC sp_OASetProperty @email, 'Subject', 'This is a test'
    EXEC sp_OASetProperty @email, 'Body', 'This is a test'
    EXEC sp_OASetProperty @email, 'From', 'myemail@example.com'
    DECLARE @success int
    EXEC sp_OAMethod @email, 'AddTo', @success OUT, 'person1', 'person1@example.com'
    EXEC sp_OAMethod @email, 'AddTo', @success OUT, 'person2', 'person2@example.com'
    EXEC sp_OAMethod @email, 'AddTo', @success OUT, 'person3', 'person3@example.com'
    -- The SMTP server smtp.example.com won't know anything about an email address @somewhere_else.com
    EXEC sp_OAMethod @email, 'AddTo', @success OUT, 'person3', 'person4@somewhere_else.com'
    -- ...

    -- Verify recipients.
    -- **** See the warning about using this API method in the description above.
    -- (An SMTP server only knows valid email address for its own domain.  For example,
    -- smtp.example.com *may* only know if person1@example.com is valid or invalid, but does
    -- not know anything about the validity of email addresses having other domains.)
    DECLARE @badAddrs int
    -- Use "Chilkat_9_5_0.StringArray" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.StringArray', @badAddrs OUT

    EXEC sp_OAMethod @mailman, 'VerifyRecips', @success OUT, @email, @badAddrs
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @mailman, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @mailman
        EXEC @hr = sp_OADestroy @email
        EXEC @hr = sp_OADestroy @badAddrs
        RETURN
      END

    DECLARE @i int
    SELECT @i = 0
    EXEC sp_OAGetProperty @badAddrs, 'Count', @iTmp0 OUT
    WHILE @i < @iTmp0
      BEGIN
        EXEC sp_OAMethod @badAddrs, 'GetString', @sTmp0 OUT, @i
        PRINT @sTmp0
        SELECT @i = @i + 1
      END


    PRINT 'done.'

    EXEC @hr = sp_OADestroy @mailman
    EXEC @hr = sp_OADestroy @email
    EXEC @hr = sp_OADestroy @badAddrs


END
GO