CAN-SPAM Compliance

[jaswrks]

---

KB Article Creation Checklist

• [x] Write initial draft for this KB Article; label this issue draft and either questions or tutorials
• [x] Add required YAML configuration
• [x] Add Tags for this KB Article to the YAML config (see YAML Keys (Explained))
• [x] Edit and finalize draft for publishing (remove draft label, add draft-finalized label)
• [x] Assign Issue to yourself and create Markdown file (remove draft-finalized label, add pending)
• [x] Project Lead: Review and Publish KB Article (remove pending label, add published label)

  Additional TODOs

Additional TODO list items go here.

---

KB Article Published @ comment-mail.com
:page_with_curl: See: CAN-SPAM Compliance

:octocat: View Markdown File | :pencil2: Edit Markdown File

---

[jaswrks]

This article should also detail the way Comment Mail automatically attaches an unsubscribe link to every email that it sends.

[raamdev]

I suggest not blockquoting the list underneath "Among other things, the CAN-SPAM Act requires that:"; those points seem like one of the primary pieces of the article and they look greyed out (because they're in blockquotes).

[jaswrks]

Done. Thanks! :-)

[kristineds]

@jaswsinc @raamdev Is this article still relevant even if references to "CAN-SPAM Act" had been removed from the plugin? Referencing: https://github.com/websharks/comment-mail/issues/122

If yes, maybe we could update the instructions on the article? Currently it says this (title on the panel has been changed):

On the article:

What we have on the plugin now:

[raamdev]

@kristineds Yes, this article is still relevant, however we do need to update the screenshots and the text to reference the new name of his panel ("Postmaster / Contact Info").

[kristineds]

@jaswsinc @raamdev I updated the text (should say "Postmaster / Contact Info") and the screenshot on the site. https://github.com/websharks/comment-mail-kb/commit/783e07cd4ad6e46e97f3de5c5a801d621919feb2

• http://comment-mail.com/kb-article/can-spam-compliance/

[jaswrks]

Cool :-)

[raamdev]

@kristineds I reviewed this. Thank you!

For future reference, you may want to try to keep your email address out of screenshots that will be posted publicly--I usually use example@example.com or something like that. No big deal, but I thought I'd point it out. :-)

[kristineds]

you may want to try to keep your email address out of screenshots that will be posted publicly

@jaswsinc Copy that. Will keep that in mind. :) I updated that screenshot. http://comment-mail.com/kb-article/can-spam-compliance/