The Federal Trade Commission (US) has opened up a window (http://ftc.gov/opa/2005/05/canspamfrn.htm) for public comment on the CAN-SPAM Act introduced in 2003.
The FTC is seeking to clarify definitions in the act, such as person, sender and some guidelines on postal addresses for opt-out procedures (in addition to the electronic opt-out options).
There are also some other areas being proposed for modification based on some rulemaking notices in 2004.
For those that deal with email marketing, bulk mail or simply want to learn more, extensive coverage for consumers and business is available related to the act.
I have covered spam and email platforms in Open Sourcery and continue to see this as a serious issue not only for the end user but for administrators as well. This is worth a read and possibly some thoughtful comments regardless of where you reside.
There are some guidelines:
If filing on paper, comments should refer to “CAN-SPAM Act Rulemaking, Project No. R411008”, and should be included both in the text and on the envelope, and should be mailed to the following address:
Federal Trade Commission, CAN-SPAM Act, Post Office Box 1030, Merrifield, VA 22116-1030.
If filing electronically, they should be submitted by clicking on the following Web link:
https://secure.commentworks.com/ftc-canspam/
and following the instructions on the Web-based form. Comments must be received by June 27, 2005.
If you liked this blog, share the love:
Learn about this Book
FREE Sample
December 15th, 2005 at 12:49 am
[…] This has been a very brief overview of what it’s like coding in Ruby on Rails. There are some great tutorials out there (check the comments to my previous blog post) that will hold your hand through creating a complete application, but in short, once you’ve grasped the way Rails implements the model-view-controller application structure, learning Rails is simply a matter of learning the naming conventions and all the built-in methods that are there to help you. Tags: Ruby on Rails […]