Chilkat Examples

ChilkatHOMEAndroid™Classic ASPCC++C#Mono C#.NET Core C#C# UWP/WinRTDataFlexDelphi ActiveXDelphi DLLVisual FoxProJavaLianjaMFCObjective-CPerlPHP ActiveXPHP ExtensionPowerBuilderPowerShellPureBasicCkPythonChilkat2-PythonRubySQL ServerSwift 2Swift 3/4TclUnicode CUnicode C++Visual Basic 6.0VB.NETVB.NET UWP/WinRTVBScriptXojo PluginNode.jsExcelGo

SQL Server Examples

Web API Categories

ASN.1
Amazon Glacier
Amazon S3
Amazon S3 (new)
Amazon SES
Amazon SNS
Amazon SQS
Async
Azure Cloud Storage
Azure Service Bus
Base64
Bounced Email
Box
CAdES
CSR
CSV
Certificates
Compression
DKIM / DomainKey
DSA
Diffie-Hellman
Digital Signatures
Dropbox
Dynamics CRM
ECC
Email Object
Encryption
FTP
FileAccess
Firebase
GMail REST API
Geolocation
Google APIs
Google Calendar
Google Cloud Storage
Google Drive
Google Photos
Google Sheets
Google Tasks
Gzip
HTML-to-XML/Text

HTTP
HTTP Misc
IMAP
JSON
JSON Web Encryption (JWE)
JSON Web Signatures (JWS)
JSON Web Token (JWT)
Java KeyStore (JKS)
MHT / HTML Email
MIME
Microsoft Graph
NTLM
OAuth1
OAuth2
OneDrive
OpenSSL
Outlook
PEM
PFX/P12
POP3
PRNG
REST
REST Misc
RSA
SCP
SFTP
SMTP
SSH
SSH Key
SSH Tunnel
SharePoint
Socket/SSL/TLS
Spider
Stream
Tar Archive
Upload
WebSocket
XAdES
XML
XML Digital Signatures
XMP
Zip
curl

 

 

 

(SQL Server) MailMan GetBadEmailAddrs

Demonstrates how to get the email addresses flagged as invalid during an SMTP send.

Note: An SMTP server can only issue errors for email addresses under it's own domain. For example, if using smtp.gmail.com to send email, the GMail server can only know what emails in the gmail.com domain are invalid. If, for example, the "TO" recipient is "doesNotExist@chilkatsoft.com", then the email would be accepted. If it's not actually a valid email address, it is not flagged as an error during the client-to-SMTP-server conversation. (If the email address turns out to be truly invalid, then a DSN (Delivery Status Notification, or "bounce") email *might* be sent by the final destination mail server to the return address.

Chilkat ActiveX Downloads

ActiveX for 32-bit and 64-bit Windows

CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @sTmp0 nvarchar(4000)
    -- This example assumes the Chilkat API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

    -- Demonstrates how to get the list of invalid email addresses flagged by the SMTP server
    -- at the time of sending (i.e. during the SMTP conversation).

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

    EXEC sp_OASetProperty @mailman, 'SmtpHost', 'outlook.office365.com'
    EXEC sp_OASetProperty @mailman, 'SmtpPort', 587
    EXEC sp_OASetProperty @mailman, 'StartTLS', 1

    -- Set the SMTP login/password
    EXEC sp_OASetProperty @mailman, 'SmtpUsername', 'OFFICE365-SMTP-LOGIN'
    EXEC sp_OASetProperty @mailman, 'SmtpPassword', 'OFFICE365-SMTP-PASSWORD'

    -- Create a new email object
    DECLARE @email int
    EXEC @hr = sp_OACreate 'Chilkat_9_5_0.Email', @email OUT

    EXEC sp_OASetProperty @email, 'Subject', 'Testing for Chilkat API...'
    EXEC sp_OASetProperty @email, 'Body', 'Testing for Chilkat API...'
    EXEC sp_OASetProperty @email, 'From', 'Chilkat Support <my-office365-user@mydomain.com>'
    DECLARE @success int
    EXEC sp_OAMethod @email, 'AddTo', @success OUT, 'Chilkat Admin', 'admin@chilkatsoft.com'
    EXEC sp_OAMethod @email, 'AddTo', @success OUT, 'Non-Existent Recipient 1', 'nonexist1@something.com'
    EXEC sp_OAMethod @email, 'AddTo', @success OUT, 'Non-Existent Recipient 2', 'nonexist2@gmail.com'
    -- To add more recipients, call AddTo, AddCC, or AddBcc once per recipient.

    -- Allow SendEmail to succeed even if some recipients are rejected immediately
    -- by the SMTP server.
    EXEC sp_OASetProperty @mailman, 'AllOrNone', 0

    -- Call SendEmail to connect to the SMTP server and send.
    -- The connection (i.e. session) to the SMTP server remains
    -- open so that subsequent SendEmail calls may use the
    -- same connection.  
    EXEC sp_OAMethod @mailman, 'SendEmail', @success OUT, @email
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @mailman, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @mailman
        EXEC @hr = sp_OADestroy @email
        RETURN
      END

    EXEC sp_OAMethod @mailman, 'CloseSmtpConnection', @success OUT
    IF @success <> 1
      BEGIN

        PRINT 'Connection to SMTP server not closed cleanly.'
      END

    PRINT 'Mail Sent!'

    -- IMPORTANT:  This example uses the Office365 SMTP server.  However, Office365 does not 
    -- reject any invalid emails, even for it's own domain.  This is common behavior.
    -- The same is true for GMail.  In many cases, the recipient email addresses are silently
    -- accepted by the SMTP server, even if known to be invalid.   

    -- Using GetBadEmailAddrs would only make sense for server that explicilty rejects local recipients
    -- known to be invalid.

    -- Examine which email addresses were rejected by the SMTP server during the SMTP conversation. 
    -- (i.e. during the SendEmail)
    DECLARE @badAddrs int
    EXEC sp_OAMethod @mailman, 'GetBadEmailAddrs', @badAddrs OUT
    DECLARE @numBadAddrs int
    EXEC sp_OAGetProperty @badAddrs, 'Count', @numBadAddrs OUT
    DECLARE @i int
    SELECT @i = 0
    WHILE @i < @numBadAddrs
      BEGIN


        EXEC sp_OAMethod @badAddrs, 'GetString', @sTmp0 OUT, @i
        PRINT 'Rejected recipient ' + @i + ': ' + @sTmp0
        SELECT @i = @i + 1
      END
    EXEC @hr = sp_OADestroy @badAddrs


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


END
GO

 

© 2000-2019 Chilkat Software, Inc. All Rights Reserved.