{"id":1910,"date":"2019-04-02T01:06:57","date_gmt":"2019-04-02T01:06:57","guid":{"rendered":"https:\/\/agile-ed.com\/?p=1910"},"modified":"2025-04-08T10:24:11","modified_gmt":"2025-04-08T16:24:11","slug":"complying-with-can-spam","status":"publish","type":"post","link":"https:\/\/agile-ed.com\/resources\/complying-with-can-spam\/","title":{"rendered":"Complying with CAN-SPAM"},"content":{"rendered":"
\n
<\/div>\n
\n

The CAN-SPAM Act was first enacted in 2003 and updated in 2009. The law establishes the rules for commercial email and commercial messages. It gives recipients the right to have a business stop emailing them, and outlines the penalties incurred for those who violate the law. Complying with the CAN-SPAM Act is quite easy.<\/p>\n

    \n
  1. Don\u2019t use false or misleading header information. Your \u201cFrom,\u201d \u201cTo,\u201d \u201cReply-To,\u201d and routing information must be accurate and identify the person or business who initiated the message.<\/li>\n
  2. Don\u2019t use deceptive subject lines. The subject line must accurately reflect the content of the message.<\/li>\n
  3. Include a physical address. Your message must include your valid physical postal address. This can be your current street address, a post office box you\u2019ve registered with the U.S. Postal Service, or a private mailbox you\u2019ve registered with a commercial mail receiving agency established under Postal Service regulations.<\/li>\n
  4. Identify the message as an ad. The law gives you a lot of leeway in how to do this, but you must disclose clearly and conspicuously that your message is an advertisement. Some e-mailers choose to include a note in the footer or pre-header text that says \u201cThis is an advertisement\u201d. However, this is not specifically required by CAN-SPAM. In most cases, the fact that you are making an offer and clearly promoting a product or service is sufficient enough to comply with the law.<\/li>\n
  5. Tell recipients how to opt-out of receiving future email from you. Your message must include a clear and conspicuous explanation of how the recipient can opt-out of getting email from you in the future. When you use Agile to send your email we will insert this opt-out language and link for you.<\/li>\n
  6. Honor opt-out requests promptly. Any opt-out mechanism you offer must be able to process opt-out requests for at least 30 days after you send your message. You must honor a recipient\u2019s opt-out request within 10 business days. You can\u2019t charge a fee, require the recipient to give you any personally identifying information beyond an email address, or make the recipient take any step other than sending a reply email or visiting a single page on an Internet website as a condition for honoring an opt-out request. Once people have told you they don\u2019t want to receive more messages from you, you can\u2019t sell or transfer their email addresses, even in the form of a mailing list. The only exception is that you may transfer the addresses to a company you\u2019ve hired to help you comply with the CAN-SPAM Act.<\/li>\n<\/ol>\n

    For more information, review a guide from the Federal Trade Commission<\/a>.<\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

    The CAN-SPAM Act was first enacted in 2003 and updated in 2009. The law establishes the rules for commercial email and commercial messages. It gives recipients the right to have a business stop emailing them, and outlines the penalties incurred for those who violate the law. Complying with the CAN-SPAM Act is quite easy. Don\u2019t […]<\/p>\n","protected":false},"author":8,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_eb_attr":"","om_disable_all_campaigns":false,"footnotes":""},"categories":[8],"tags":[36,31],"class_list":["post-1910","post","type-post","status-publish","format-standard","hentry","category-knowledge-center","tag-can-spam","tag-email-marketing"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agile-ed.com\/wp-json\/wp\/v2\/posts\/1910","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agile-ed.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/agile-ed.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/agile-ed.com\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/agile-ed.com\/wp-json\/wp\/v2\/comments?post=1910"}],"version-history":[{"count":0,"href":"https:\/\/agile-ed.com\/wp-json\/wp\/v2\/posts\/1910\/revisions"}],"wp:attachment":[{"href":"https:\/\/agile-ed.com\/wp-json\/wp\/v2\/media?parent=1910"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agile-ed.com\/wp-json\/wp\/v2\/categories?post=1910"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agile-ed.com\/wp-json\/wp\/v2\/tags?post=1910"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}