Send HTML Email with CSS as a Related Item (Content-Location)
See more SMTP Examples
Package a CSS stylesheet as a related MIME item and reference it using Content-Location. This sends a real message. Replace the recipient with an address you control.
Related CSS is a MIME packaging demonstration, not a guarantee of rendering. Many email clients ignore or strip stylesheet links. Use inline CSS for broadly compatible HTML email and test the recipient clients you support.
Microsoft 365 work/school: The account needs an Exchange Online mailbox. SMTP submission uses smtp.office365.com:587 with STARTTLS. An administrator must allow SMTP AUTH for the mailbox under the tenant's security policy; a valid OAuth token cannot enable a disabled protocol. Security defaults can block SMTP AUTH: have the administrator choose an approved configuration or mail API rather than disabling protections just to run a sample. See SMTP AUTH settings. Personal Outlook.com accounts instead use smtp-mail.outlook.com and delegated user authorization.
First authorize the account with https://outlook.office.com/SMTP.Send and offline_access, then refresh the access token when needed. This example reads qa_data/tokens/office365.json from a private working directory. Microsoft Graph permissions such as Mail.Send or Mail.Read do not authorize these mail protocols. Do not print tokens or authentication logs.
Microsoft reference documentation
Chilkat SQL Server Downloads
-- 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
DECLARE @iTmp1 int
DECLARE @sTmp0 nvarchar(4000)
DECLARE @success int
SELECT @success = 0
-- Assumes Chilkat is unlocked. See Global Unlock Sample.
DECLARE @token int
EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @token OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
EXEC sp_OAMethod @token, 'LoadFile', @success OUT, 'qa_data/tokens/office365.json'
IF @success <> 1
BEGIN
PRINT 'Could not read qa_data/tokens/office365.json from the private working directory.'
EXEC @hr = sp_OADestroy @token
RETURN
END
EXEC sp_OAMethod @token, 'JsonTypeOf', @iTmp0 OUT, 'access_token'
EXEC sp_OAMethod @token, 'StringOfEquals', @iTmp1 OUT, 'access_token', '', 1
IF (@iTmp0 <> 1) or (@iTmp1 = 1)
BEGIN
PRINT 'An OAuth access token is required. Authorize or refresh the account first.'
EXEC @hr = sp_OADestroy @token
RETURN
END
DECLARE @mailbox nvarchar(4000)
SELECT @mailbox = 'user@example.com'
DECLARE @mailman int
EXEC @hr = sp_OACreate 'Chilkat.MailMan', @mailman OUT
EXEC sp_OASetProperty @mailman, 'SmtpHost', 'smtp.office365.com'
EXEC sp_OASetProperty @mailman, 'SmtpPort', 587
EXEC sp_OASetProperty @mailman, 'SmtpSsl', 0
EXEC sp_OASetProperty @mailman, 'StartTLS', 1
EXEC sp_OASetProperty @mailman, 'RequireSslCertVerify', 1
-- Microsoft SMTP submission uses STARTTLS on port 587, not implicit TLS on 465.
EXEC sp_OASetProperty @mailman, 'SmtpUsername', @mailbox
EXEC sp_OASetProperty @mailman, 'SmtpPassword', ''
EXEC sp_OAMethod @token, 'StringOf', @sTmp0 OUT, 'access_token'
EXEC sp_OASetProperty @mailman, 'OAuth2AccessToken', @sTmp0
DECLARE @email int
EXEC @hr = sp_OACreate 'Chilkat.Email', @email OUT
EXEC sp_OASetProperty @email, 'From', @mailbox
EXEC sp_OASetProperty @email, 'Subject', 'Sample HTML message'
EXEC sp_OAMethod @email, 'AddTo', @success OUT, 'Recipient', 'recipient@example.net'
IF @success <> 1
BEGIN
PRINT 'Could not add the recipient.'
EXEC @hr = sp_OADestroy @token
EXEC @hr = sp_OADestroy @mailman
EXEC @hr = sp_OADestroy @email
RETURN
END
DECLARE @contentId nvarchar(4000)
EXEC sp_OAMethod @email, 'AddRelatedString', @contentId OUT, 'styles.css', 'p { color: blue; }', 'utf-8'
EXEC sp_OAGetProperty @email, 'LastMethodSuccess', @iTmp0 OUT
IF (@iTmp0 <> 1) or (@contentId = '')
BEGIN
PRINT 'Could not add the related MIME item.'
EXEC @hr = sp_OADestroy @token
EXEC @hr = sp_OADestroy @mailman
EXEC @hr = sp_OADestroy @email
RETURN
END
-- This new email has one related item, at index zero.
EXEC sp_OAMethod @email, 'AddRelatedHeader', NULL, 0, 'Content-Location', 'styles.css'
EXEC sp_OAGetProperty @email, 'LastMethodSuccess', @iTmp0 OUT
IF @iTmp0 <> 1
BEGIN
PRINT 'Could not set Content-Location.'
EXEC @hr = sp_OADestroy @token
EXEC @hr = sp_OADestroy @mailman
EXEC @hr = sp_OADestroy @email
RETURN
END
EXEC sp_OAMethod @email, 'SetHtmlBody', NULL, '<html><head><link rel="stylesheet" href="styles.css"></head><body><p>Sample text.</p></body></html>'
-- This sends a real message. Replace the recipient with an address you control.
EXEC sp_OAMethod @mailman, 'SendEmail', @success OUT, @email
IF @success <> 1
BEGIN
EXEC sp_OAMethod @mailman, 'CloseSmtpConnection', @success OUT
PRINT 'SMTP send failed. Check the token, mailbox, recipient, and SMTP AUTH policy.'
-- Inspect LastErrorText privately if needed; do not publish authentication/session logs.
-- A lost connection after DATA can leave acceptance uncertain. Avoid blindly retrying.
EXEC @hr = sp_OADestroy @token
EXEC @hr = sp_OADestroy @mailman
EXEC @hr = sp_OADestroy @email
RETURN
END
EXEC sp_OAMethod @mailman, 'CloseSmtpConnection', @success OUT
IF @success <> 1
BEGIN
PRINT 'Microsoft accepted the message, but closing the connection failed. Do not resend it.'
EXEC @hr = sp_OADestroy @token
EXEC @hr = sp_OADestroy @mailman
EXEC @hr = sp_OADestroy @email
RETURN
END
PRINT 'Microsoft accepted the message for delivery.'
EXEC @hr = sp_OADestroy @token
EXEC @hr = sp_OADestroy @mailman
EXEC @hr = sp_OADestroy @email
END
GO