Loading...
 
Skip to main content

Development

Forum List Topic List

 
Thread actions
Print this page
  • Print all pages

    • CAN-SPAM compliance

    Posted by Tagg posts: 21 ☆ ☆ ☆ United States

    I suspect that businesses transmitting email to/within the USA have concerns about complying with the CAN-SPAM Act of 2003 http://www.ftc.gov/bcp/conline/pubs/buspubs/canspam.htmQuestion.

    For transmitted messages, I at least want to:

    • prefix all transmitted message subject lines with the business name,
    • as appropriate, append a "clear and conspicuous notice that the message is an advertisement or solicitation,"
    • append the business mailing address (and optionally our telephone number),
    • as appropriate, append a declaration that the message is transactional and not list driven, and/or provide recipients an opt-out method by providing a return email address specifically for that purpose, e.g. OPT-OUT@, and/or provide a hyperlink/URL for opting-out from being sent future email messages to that email address, e.g. tiki-opt-out.php


    Currently, I am in the process of manually modifying each message template found under:
    templates/mail

    Within a Web site Administrator's primarily language(s), the task is more annoying than difficult. However, cascading those changes into other languages may be difficult to effectively impossible.

    To ensure compliance with a person's request/demand to not receive further email messages, I would like to maintain a list of opted-out email addresses. Ideally, an opted-out recipient address would not be accepted for new account registrations or account contact email address changes, and the tiki-emailer would not send a message to any opted-out recipient address. (An option to re-route those to an internal mailbox would be nice. Companies pursuing CRM might want to assign a Customer Care representative to research the issue.)

    Reads: 2043
    Posted by sylvie greverend posts: 1092 ☆ ☆ ☆

    > I suspect that businesses transmitting email to/within the USA have concerns about complying with the CAN-SPAM Act of 2003 http://www.ftc.gov/bcp/conline/pubs/buspubs/canspam.htmQuestion.
    Welcome. It is open source. So everybody is welcome to add something that will insure security...

    >
    > For transmitted messages, I at least want to:
    > * prefix all transmitted message subject lines with the business name,
    Check each template. but a lot already includes the domain name .. Is it enough?

    > * as appropriate, append a "clear and conspicuous notice that the message is an advertisement or solicitation,"

    Each messages going trough tw are not of this type. Except message from other user when you have a forward. But how to control other user message. Better to disable the messaging feature. For the other ones, it is administrator configuration, user wish (notification...).

    > * append the business mailing address (and optionally our telephone number),
    As I said before, it is a bug is not

    > * as appropriate, append a declaration that the message is transactional and not list driven, and/or provide recipients an opt-out method by providing a return email address specifically for that purpose, e.g. OPT-OUT@, and/or provide a hyperlink/URL for opting-out from being sent future email messages to that email address, e.g.
    tiki-opt-out.php

    If you want to check each template welcome

    >
    > Currently, I am in the process of manually modifying each message template found under:
    > templates/mail
    >
    > Within a Web site Administrator's primarily language(s), the task is more annoying than difficult. However, cascading those changes into other languages may be difficult to effectively impossible.

    Almost each mail template is processed through the fetchLang function (pretty sure is everywhere but bug can happen), it means that if you update each your_language/language.php file (for each language of your site), you will send to the user the message in his preferered language


    >
    > To ensure compliance with a person's request/demand to not receive further email messages, I would like to maintain a list of opted-out email addresses. Ideally, an opted-out recipient address would not be accepted for new account registrations or account contact email address changes, and the tiki-emailer would not send a message to any opted-out recipient address. (An option to re-route those to an internal mailbox would be nice. Companies pursuing CRM might want to assign a Customer Care representative to research the issue.)

    A lot (not all perhaps) contain the sentence - if you don't want to receive/watch... message, do this. If you want to help to check which one is not inserting the "sentence" welcome. This missing "sentence" is considered as bug too.

    Each bug can be submitted at dev.tikiwiki.org 😉 or you can join the team to fix the problem.
    sylvie

    Posted by Tagg posts: 21 ☆ ☆ ☆ United States

    "It is not a bug."

    Generally, I do not bother with reporting "bugs" or coding errors in open-source software. Instead, I make a fix and post a proven fix for a known, reproducible error condition.

    My original post for this topic, within the "Tikiwiki Development" sub-forum, was not intended as a bug report. Rather, it is intended as a source of material inspiration for future Tikiwiki development. Legal and financial penalties of failing to comply with the CAN-SPAM Act of 2003 are non-trivial and can be devestating to a small business.

    http://www.ftc.gov/bcp/conline/pubs/buspubs/canspam.htmQuestion
    "Each violation of the above provisions is subject to fines of up to $11,000"
    "Additional fines are provided for commercial emailers who not only violate the rules described above, but also: ... use scripts or other automated ways to register for multiple email or user accounts to send commercial email"

    As such, I believe it to be valid candidate as a future development node.