This page describes my use of the Gammadyne Mailer.
I use the Gammadyne Mailer for all of the ezines I operate.
My Gammadyne History
When I began emailing to my first list ( Snippets ) I hosted with Topica. But in the middle of 2002, Topica began to include, not only ads at the bottom of the emails, but also ads at the top. This change caused me to begin to look for options.
In late August 2002 I began testing WorldCast software from Fairlogic Systems to host the mailing list myself. That didn't work out. The software had a number of unacceptable issues.
I then moved to the Gammadyne Mailer and have been very pleased.
It is possible to use it very simply, almost out of the box. But it also features a very complete internal programming language to let you do just about anything you want.
For example, it lets me keep all the information on my PC in an Access database. I know that the information is secure and under my control. It also lets me program much of the interaction.
Since my initial adoption I've made a series of changes:
It is screaming software.
I strongly recommend Gammadyne Mailer.
Special Functions I Have Coded for My Implementation of Gammadyne Mailer
In programming my implementation of Gammadyne Mailer I've provided for many situations.
How You Can "Test" My Implementation of Gammadyne Mailer
I created a test ezine ( TestZine) to let me test my customizations of the Gammadyne Mailer.
But you can also subscribe/unsubscribe and receive a "sample issue". You can even try out some of the tests I perform, like subscribing twice in a row, or subscribing when I'm already subscribed or unsubscribing when I'm not subscribed, just to see how it handles these "special conditions". If you'd like to try this, just go to my TestZine page.
Information Collected for My ezines
When you join any of my email/ezine lists (e.g., TestZine and TestZine and HEFS Bulletin), I keep your email address (because it really wouldn't make much sense to have an email/ezine list if I didn't keep your email address).
And I keep information necessary to provide an audit trail in order to comply with the CAN-SPAM Act of 2003.
Here is a list of Subscription Information that I keep for all email/ezine lists I host on my site using the Gammadyne Mailer system:
Personal and Status Information
Current Issue Information
Subscription Process Information
Unsubscription Process Information
Pending Confirmation Information
Here is a summary list of my privacy practices for TestZine (and for every ezine I manage):
I have a much longer, more legalistic version.
In fact, I have several of them:
General Privacy Page
The general privacy page provides an overview of all of my privacy policies. Although it is lengthy and thorough, I still think it is easy to read. You might even find a bit of humor if you look for it.
It also provides links to my specific privacy pages including:
On Wednesday, 26.Jul.2000, Senators Spence Abraham, John McCain and John Kerry introduced the Consumer Internet Privacy enhancement Act (CIPEA). This proposed legislation never made it into the law. But I used the law as a model to construct a privacy statement which would comply. I did it as an exercise in learning more about privacy principles.
I have created a CIPEAprivacy disclosure page (which I call CIPEATone) to clarify the the notices proposed by CIPEA(Consumer Internet Privacy enhancement Act). All of the disclosures on the CIPEATone page are functional duplicates of disclosures on my privacy page, but they have been "organized" according to the structure of CIPEA. This page also provides background and impact information regarding CIPEA and links to other articles and resources for CIPEA.
I have created a COPPA Privacy Disclosure page (which I call COPPA Cabana) to provide the notices required by COPPA (Children's Online Privacy Protection Act) related to information practices of this site regarding personal information and privacy of children. This page also provides background and impact information regarding COPPA and links to other articles and resources for COPPA.
OECD Privacy Statement
A long, long time ago, on 23.Sep.1980, the Organization for Economic Co-operation and Development, (OECD), issued Guidelines on the Protection of Privacy and Transborder Flows of Personal Data.
(Did you notice that date? 1980!! Privacy issues are not new.)
Recently OECD created the OECD Privacy Statement Generator to help organizations create privacy statements to post on websites.
All of the disclosures on the OECD Privacy-D page are functional duplicates of disclosures on my privacy page, but they have been "organized" according to the structure of the OECD Privacy Principles. This page also provides background and impact information regarding the OECD Privacy Guidelines links to other resources for the OECD Privacy Guidelines.
Disclosure: I participate in the Gammadyne affiliate program. Click here to link without crediting my referral account.
List Management Information
Best Practices of Email, Ezine and List Management: The organization known as MAPS (Mail Abuse Prevention System) once published a list it called "Basic Mailing List Management Principles for Preventing Abuse". I used this list as the starting point to create my own "Best Practices" which I follow in managing my lists. ««»»
List Email Headers: An explanation of the RFC standard headers which should be used on emails for lists and ezines. Also identifies the supplementary user-defined fields I use on my ezines, as well as RFC standard email addresses ezine publishers should implement. ««»»
History of Changes to Snippets: Describes the history of Snippets, with emphasis on the technical changes I've made since starting it, including moving to Gammadyne, adding double-opt-in and complying with CAN-SPAM. ««»»
TestZine, My "Test" ezine: To help "test" the changes to my Gammadyne Mailer system, I created TestZine. This ezine is fully functional. For example, you can subscribe, and unsubscribe. But there isn't really a "publication". If you subscribe and confirm your subscription, you will receive a sample issue. If you stay subscribed, you might get that issue again (as I retest features). If you unsubscribe, then resubscribe, you'll get that same issue. You can even try out some of the tests I perform, like subscribing twice in a row, or subscribing when you are already subscribed or unsubscribing when you are not subscribed, just to see how it handles these "special conditions". ««»»
This page created: